Hosted MCP server/Cloud Service

beacon.host MCP server

Hosted at beacon.host·Streamable HTTP

beacon.host publishes HTML, a file or a whole static site from an agent and returns a live https://<name>.beacon.host link plus a claim link. The MCP endpoint is https://beacon.host/mcp over stateless Streamable HTTP, with tools publish_site, get_site and get_docs. No account or key is needed: anonymous sites accept 4 MB of files, stay live for 24 hours and can be claimed, at 5 publishes per hour per IP. An optional Bearer chk_ key raises the limits to 10 MB, up to 1,000 files and 60 publishes per hour. chorus.host resolves to the same product page.

beacon.host Streamable HTTP None; optional Bearer chk_... for account publishing Server not checked yet Reviewed 2026-11-16
About

Where it fits

Agent builders and prompt authors who want to publish a generated page or static site immediately without an account.

  • Publish an HTML page or static site to a live URL.
  • Read a published site or the provider's docs through the MCP tools.
  • Claim an anonymous site so it stays live beyond 24 hours.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds beacon.host as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http beacon-host https://beacon.host/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://beacon.host/mcp
Host
beacon.host · /mcp
Transport
Streamable HTTP
Authentication
None; optional Bearer chk_... for account publishing
Server name
beacon-host
Listing type
Community or directory listing

The installer uses the server name beacon-host. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that beacon-host appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Publish an HTML page or static site to a live URL. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

beacon.host documentationhttps://beacon.host/mcp