chorus.host is a remote MCP server that gives an AI agent 3 tools, among them get_docs, get_site, publish_site. It answers at https://chorus.host/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 1 October 2026; the last check, on 16 November 2026, succeeded.
Publish websites from any AI agent. Live URL at <slug>.chorus.host in one call, no account needed.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_docs | Return the full beacon.host documentation as Markdown (the same text as https://beacon.host/skill.md): the REST API, the beacon CLI, accounts and API keys, claiming sites, password protection, and Workers, which run server-side JavaScript a |
get_site | Check a beacon.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. Us Inputs: slug, claim_token |
publish_site | Publish a website or any file (PDF, image, HTML, CSS/JS) to a live public HTTPS URL at <slug>.beacon.host in one call. Files keep their content type, so PDFs and images open in the browser. No account or API key needed. Use it when the user Inputs: files, slug, claim_token, title, expires_at, password |
Every block below points at https://chorus.host/mcp. Pick your client and copy.
claude mcp add --transport http chorus-host https://chorus.host/mcp
{
"mcpServers": {
"chorus-host": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://chorus.host/mcp"]
}
}
}{
"mcpServers": {
"chorus-host": {
"url": "https://chorus.host/mcp"
}
}
}{
"servers": {
"chorus-host": {
"type": "http",
"url": "https://chorus.host/mcp"
}
}
}{
"context_servers": {
"chorus-host": {
"url": "https://chorus.host/mcp"
}
}
}{
"mcpServers": {
"chorus-host": {
"serverUrl": "https://chorus.host/mcp"
}
}
}{
"mcpServers": {
"chorus-host": {
"url": "https://chorus.host/mcp"
}
}
}name: chorus.host
version: 0.0.1
schema: v1
mcpServers:
- name: chorus.host
type: streamable-http
url: https://chorus.host/mcp{
"mcpServers": {
"chorus-host": {
"httpUrl": "https://chorus.host/mcp"
}
}
}{
"mcpServers": {
"chorus-host": {
"type": "http",
"url": "https://chorus.host/mcp"
}
}
}{
"mcpServers": {
"chorus-host": {
"url": "https://chorus.host/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fchorus.host%2Fmcp&type=streamable_http&id=chorus-host&name=chorus.host
It answered our last check on 16 November 2026 in 498 ms. Over 4 checks since 1 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by chorus.host and served from chorus.host, the vendor's own domain: https://chorus.host/mcp.
3, as returned by the server's own tools/list on 19 November 2026: get_docs, get_site, publish_site.
It answered our last check on 16 November 2026 in 498 ms. Over 4 checks since 1 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://chorus.host/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: host.chorus. Endpoint host: chorus.host. ARD identifier: urn:air:host.chorus:mcp:mcp.
First indexed 1 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.