Listing Policy
Edition 1.1, in force from .
This policy is part of the Terms of Service.
1. Where listings come from
We list the servers published to the Official MCP Registry (registry.modelcontextprotocol.io), except those deleted there, and servers we find in public package registries and catalogues (npm, PyPI, crates.io, Go modules, NuGet, Maven Central, Packagist, RubyGems, Open VSX, Docker Hub, Docker's and GitHub's MCP catalogues and Hugging Face Spaces) when the package depends on an MCP software development kit, declares itself an MCP server, or lists its MCP tools. Other directories are used only to find a server's name or address; we do not copy their descriptions, scores or lists.
2. What a listing shows
A listing shows what the publisher wrote (name, title, description, version, packages and remote endpoints), install snippets we write from it, and facts read from public sources: the licence, the website and repository, the sources that list the server, its tools, download counts its package registry publishes, and advisories known for its packages. It is placed in categories and ordered as How we rank describes. Once we run them, it also shows our own dated check results. What the publisher wrote is shown as they wrote it. What we write ourselves is marked as ours.
3. Claiming a listing
Claiming is not open yet. When it is, a publisher who shows they control the server's repository will be able to add a description, logo and links, reply to our findings and ask for a new check. Claiming never changes a check result or a score.
4. What you send us
Text and logos a publisher sends us are covered by the licence in section 5 of the Terms. A claimant can see and export what they sent us and the data we hold about their listing.
5. Checks and corrections
When we check servers, we publish how. A check only connects to a server to see whether it starts and what it offers; it never calls a tool, never uses credentials and never sends heavy traffic. A publisher may reply to any finding and ask for a new check; if the finding does not repeat, we withdraw it. A mistake we confirm is corrected within 5 business days. A publisher may ask us to stop checking their server.
6. Removal
A server deleted from the registry, or no longer found in the source that listed it, disappears from the site at our next update. A publisher may ask us to remove a listing through the report form or at [email protected].
7. Paid placement
Nothing on the site is paid for today. If we ever sell placement, payment will change placement only and be labelled; it will never change a check result, a score or what we say about a server, and we will never sell a "verified", "trusted" or "secure" mark.
8. What we do not list
We do not list, or we remove, a server that contains malware, impersonates another project or publisher, or uses a name that infringes someone else's rights. When we act on a listing, we give our reasons and a way to dispute them, as section 12 of the Terms describes.
9. Disputes between claimants
If two people claim the same listing, we ask both for proof of control of the repository and the registry namespace, and decide on that proof. Either may dispute our decision as the Terms describe.