Destination type
Official registry
MCP Registry
Longtail ecosystem•Path checked
Official MCP Registry
The MCP project's vendor-neutral registry publishes server metadata for downstream clients and aggregators. It is a registry, not a client-specific app store.
The brand reference above links to an official platform source. EveryMCP is an independent directory and is not endorsed by this platform.
Eligibility and connection boundary
The quickstart covers package ownership verification, an npm or other supported artifact, registry authentication, and a server.json entry. Remote-server support is documented as a separate path.
Review or publication path
The registry is in preview and uses validation, status, and community moderation. The official project warns that breaking changes or data resets may occur before general availability.
Cost and terms
No registry fee is stated in the checked docs. Package hosting, npm, GitHub, and account costs remain separate from the registry metadata entry.
Preparation checklist
- 1.Choose the package or remote-server path and read its current ownership-verification requirements.
- 2.Publish the underlying artifact where required, then validate server.json with the official publisher tool.
- 3.Authenticate with the intended namespace, publish a version, and retain the registry response as a receipt.
- 4.Monitor status and schema changes because the registry is explicitly in preview.
Open questions
- • Preview behavior, data durability, and schema changes before general availability.
- • Whether a given hosted endpoint should use the remote-server path or a package entry.
Sources checked
2026-09-22Receipt boundary: A connection, a submitted PR, or a registry record does not prove marketplace approval. Keep the platform response, version, review state, and rollback plan with the release evidence.