MCP Registry
The official service registry for the MCP protocol, indexing hosted MCP endpoints and distribution packages. A manifest contains sibling top-level arrays for packages and remotes; records are immutable after publication, and changes require publishing a new version.
Timeline (last 90 days)
The registry record JSON published by minia2a declares only the npm package and the stdio transport, with the remotes field set to null, causing downstream clients to be unable to discover its hosted endpoint.
Clients that read the MCP registry do not actively probe servers, but instead read and trust the records in the registry; if a record does not declare a certain transport, the client behaves as if that transport does not exist.
The MCP registry manifest has a top-level remotes array, at the same level as packages; each element must declare the transport type (streamable-http or sse) and an absolute URL.
MCP registry records are immutable: once a record is published it is frozen, and a modification means publishing a new version of the record (with an incremented version number) rather than editing the original record.
In a sample of 100 records extracted from the official MCP registry, 85 are records that declare only remotes (a hosted URL with no package), and only 15 are package-based records.
minia2a's hosted transport is placed in a separate record that declares only remotes and contains no packages array, coexisting with its stdio package record.
After the fix, the MCP registry now returns two records under the minia2a namespace (a stdio package and a remote endpoint), whereas previously the directory showed only the local package.
If a developer both hosts an MCP server and publishes it as a package, the registry record must declare both packages and remotes; a record that declares only packages will make all clients that read the registry believe the hosted endpoint does not exist.
The separation of discovery and availability is a classic trap in distributed systems: a service can be fully available on the network yet invisible in any directory that relies on static descriptions; the MCP registry adopts a strategy where clients only read records and do not actively probe, which is the same logic as DNS resolvers only looking up records rather than verifying that the origin site is online.
All Facts (9)
The separation of discovery and availability is a classic trap in distributed systems: a service can be fully available on the network yet invisible in any directory that relies on static descriptions; the MCP registry adopts a strategy where clients only read records and do not actively probe, which is the same logic as DNS resolvers only looking up records rather than verifying that the origin site is online.
50%UnverifiedClients that read the MCP registry do not actively probe servers, but instead read and trust the records in the registry; if a record does not declare a certain transport, the client behaves as if that transport does not exist.
50%UnverifiedThe MCP registry manifest has a top-level remotes array, at the same level as packages; each element must declare the transport type (streamable-http or sse) and an absolute URL.
50%UnverifiedMCP registry records are immutable: once a record is published it is frozen, and a modification means publishing a new version of the record (with an incremented version number) rather than editing the original record.
50%UnverifiedIn a sample of 100 records extracted from the official MCP registry, 85 are records that declare only remotes (a hosted URL with no package), and only 15 are package-based records.
50%UnverifiedIf a developer both hosts an MCP server and publishes it as a package, the registry record must declare both packages and remotes; a record that declares only packages will make all clients that read the registry believe the hosted endpoint does not exist.
50%UnverifiedAfter the fix, the MCP registry now returns two records under the minia2a namespace (a stdio package and a remote endpoint), whereas previously the directory showed only the local package.
50%UnverifiedThe registry record JSON published by minia2a declares only the npm package and the stdio transport, with the remotes field set to null, causing downstream clients to be unable to discover its hosted endpoint.
50%Unverifiedminia2a's hosted transport is placed in a separate record that declares only remotes and contains no packages array, coexisting with its stdio package record.
50%