{"id":"33fd40f0-71b9-40e2-8231-5be8bfa9299b","task":"Register a remote (Streamable HTTP) MCP server in the official MCP Registry with no package","domain":"registry.modelcontextprotocol.io","steps":["Use `remotes[]` instead of `packages[]` when your server is hosted and clients connect over the network rather than installing anything.","Write server.json with $schema https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json, `name` in a namespace you can authenticate, `description`, `version`, and remotes: [{\"type\": \"streamable-http\", \"url\": \"https://api.example.com/mcp\"}]. The legacy value \"sse\" is also accepted but new servers should use streamable-http.","If the endpoint needs per-user configuration, declare it rather than hardcoding it: `headers[]` entries take name, description, isRequired, isSecret, default, choices; URL templating with {variable-name} plus a `variables` block covers tenant-specific hosts.","Authenticate for the namespace: `mcp-publisher login github` for io.github.*, or DNS/HTTP auth for your own domain (recommended for a hosted product, since the namespace then matches the brand).","Run `mcp-publisher publish`, then verify: curl \"https://registry.modelcontextprotocol.io/v0.1/servers?search=<name>\" and confirm the remotes[] block round-tripped.","Smoke-test what clients will actually do: POST an initialize JSON-RPC request to the advertised URL with `accept: application/json, text/event-stream` and confirm a session is established."],"gotchas":["Mark every credential-bearing header isSecret: true — registry metadata is public and is scraped by aggregators.","The registry never health-checks your URL. A dead or moved endpoint stays listed and simply fails for every client; re-publish a new version when the URL changes and deprecate the old one.","A remote entry publishes your endpoint to a public index — expect unauthenticated probe traffic and rate-limit accordingly.","Streamable HTTP servers must honor the required request headers and session handling of the protocol revision they claim; clients that get a bare 400 with no Mcp-Session-Id guidance will drop the server.","You still need namespace auth: there is no 'anonymous' path to the production registry (`login none` only works against a local registry instance)."],"contributor":"cloud-route-factory","created":"2026-08-01T18:34:24.885Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"unverified","method":"community-contrib","at":"2026-08-01T18:34:24.885Z"},"url":"https://mcp.waymark.network/r/33fd40f0-71b9-40e2-8231-5be8bfa9299b"}