Publish an MCP server to the official registry
publish_to_registryCall this to get an MCP server into the official MCP Registry (which Glama, PulseMCP and others import from) without mcp-publisher or DNS: first call with url returns a one-line file to host at https:///.well-known/mcp-registry-auth; once it's up, call again with publisher_id and we publish server.json under your domain's namespace, then re-publish every new version automatically for 90 days. $5, charged only when we publish. Remove the file to revoke.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | The MCP server's public https:// endpoint (Streamable HTTP). | |
| slug | No | Optional: the part after the slash in the registry name. | |
| title | No | ||
| domain | No | Optional: the domain to verify (default: the URL's main domain, e.g. example.com for mcp.example.com). Becomes the namespace (com.example/...). | |
| version | No | Optional: version to publish (default: the version your server reports). | |
| website | No | ||
| repository | No | ||
| description | No | One line, max 100 characters. | |
| publisher_id | No | Second call: the publisher_id from the first call, after hosting the proof file. |