host.chorus/mcp

Est-ce que host.chorus/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « host.chorus/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 3 outils

• get_docs≈ 163 tokens

  Return the full chorus.host documentation as Markdown (the same text as https://chorus.host/skill.md): the REST API, the beacon CLI, accounts and API keys, claiming sites, password protection, and Workers, which run server-side JavaScript at <slug>.worker.chorus.host for APIs and webhooks. Read it before building a backend, when the user asks about accounts or limits, or when a task needs something publish_site can't do.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_docs", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_site≈ 536 tokens

  Check a chorus.host site: whether it is live, its URL, whether it has a password, and when it expires. With the site's claim_token (or an API key that owns the site) it also returns the file list, total size, live version and claim link. Use it to confirm a publish worked, to see when an anonymous site expires, or to see what is published at a slug.

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    The site's slug, i.e. the subdomain in <slug>.chorus.host. A full URL also works.
  • claim_token · string · optionnel
    Optional claim_token (ctk_...) of the site. Unlocks the file list and other details.

  Exemple d'appel

  {"name": "get_site", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "slug": "texte", "files": [], "title": "texte", "status": "texte", "claimed": true, "summary": "texte", "claim_url": "texte", "can_manage": true, "created_at": "texte", "expires_at": "texte", "file_count": 1}}

• publish_site≈ 978 tokens

  Publish HTML/CSS/JS or any static files to a live public HTTPS URL at <slug>.chorus.host in one call. No account or API key needed. Use it when the user asks to publish, host, deploy or share a page, website, landing page, report, dashboard, portfolio, game or demo, or wants a link to something you made. Send every file with its path (index.html is served at the root) and its content: plain text for HTML, CSS, JS, SVG, JSON and Markdown, or base64 with encoding='base64' for images, fonts and other binary files. Each call publishes the complete site: files you leave out are removed. Limits: 4 MB of file content per call without an API key, 10 MB with one, and 1,000 files. Anonymous sites stay live for 24 hours; the result has a claim_url to give the user so they can keep the site for free, and a claim_token to save. To update a site, call again with the same slug and its claim_token.

  Paramètres, retour & exemple (4)

  Paramètres

  • slug · string · optionnel
    Optional. Subdomain to publish to (3-63 lowercase letters, digits and hyphens). Leave empty for a random one. To update an existing site, pass its slug together with its claim_token.
  • files · array · requis
    Every file of the site. Each call replaces all files of the site.
  • title · string · optionnel
    Optional human-readable title saved with the site.
  • claim_token · string · optionnel
    The claim_token (ctk_...) returned when the site was first published. Required to update an anonymous site.

  Exemple d'appel

  {"name": "publish_site", "arguments": {"files": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "slug": "texte", "updated": true, "page_url": "texte", "warnings": [], "anonymous": true, "claim_url": "texte", "expires_at": "texte", "file_count": 1, "next_steps": "texte", "version_id": "texte", "claim_token": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://chorus.host/mcp