Frequently Asked Questions ↗

mcp guide intermediate architecture models

Editorial Notes

This FAQ addresses the practical edge cases that the other registry guides do not cover in depth, including questions about naming conflicts, transfer of ownership, and delisting policies. Read this after you have gone through the main registry overview and authentication guides, since many answers assume familiarity with those workflows. The sections on troubleshooting publishing failures are particularly valuable if you encounter cryptic errors during your first submission attempt.

Original Documentation

Documentation Index#
Fetch the complete documentation index at: https://modelcontextprotocol.io/llms.txt Use this file to discover all available pages before exploring further.

The MCP Registry is currently in preview. Breaking changes or data resets may occur before general availability. If you encounter any issues, please report them on GitHub.

General#

What is the difference between “Official MCP Registry”, “MCP Registry”, “MCP registry”, “MCP Registry API”, etc?#

“MCP Registry API” — An API that implements the OpenAPI spec defined by the MCP Registry.
“Official MCP Registry API” — The REST API served at https://registry.modelcontextprotocol.io, which is a superset of the MCP Registry API. Its OpenAPI spec can be downloaded from https://registry.modelcontextprotocol.io/openapi.yaml.
“MCP registry” — A third-party service that provides an MCP Registry API.
“Official MCP Registry” (or “The MCP Registry”) — The service that lives at https://registry.modelcontextprotocol.io.

Can I delete/unpublish my server?#

Currently, no. At the time of writing, there is open discussion.

How do I update my server metadata?#

Submit a new server.json with a unique version string. Once published, version metadata is immutable (similar to npm).

Can I add custom metadata when publishing?#

Yes, custom metadata under _meta.io.modelcontextprotocol.registry/publisher-provided is preserved when publishing to the registry. This allows you to include custom metadata specific to your publishing process.

There is a 4KB size limit (4096 bytes of JSON). Publishing will fail if this limit is exceeded.

Reporting Issues#

What if I need to report a spam or malicious server?#

Report it as abuse to the underlying package registry (e.g. NPM, PyPi, DockerHub, etc.); and
Raise a GitHub issue on the registry repo with a title beginning Abuse report:

What if I need to report a security vulnerability in the registry itself?#

Follow the MCP community SECURITY.md.

Link last verified June 7, 2026. View original ↗

Source: MCP Docs

Link last verified: 2026-02-26