How we verify MCP servers
The MCP servers directory lists fewer servers than other directories on purpose. A server gets a page only when the facts on it can be traced to a source you can open. This page says where those facts come from, what we check, and what we do not.
Where the facts come from
- The official MCP registry: name, description, version, package and required settings, as the publisher submitted them.
- The project's GitHub repository, through GitHub's API: maintainer, licence, stars, open issues and the date of the last commit.
- The project's own README: the list of tools the server exposes, the clients it documents setup for and, for servers that are not in the registry, the install config, copied as written. The “About”, “What can you do” and “Requirements” sections, and the one-line description of each tool, are the README's own sentences, copied as written and labelled as such with a link; a section is left out when the README has no clear one. The questions and answers on a page are built only from the checked facts above.
Nothing is written from memory or taken from other directories. The description at the top of a server page is the publisher's own and is labelled that way.
What a server must have to be listed
- A public repository with a recognised licence.
- An install config taken from the registry entry or the README.
- A tool list in its README.
- A commit in the last six months, unless the server is published by the vendor of the tool it connects to.
- At least 10 GitHub stars, with the same exception.
Before a server is published we also check that its repository still answers, that the package named in the install config exists on npm or PyPI, and that the config does not depend on a copy of the server you would first have to clone or build. A server that fails any of this is not listed at all; we do not publish partial pages.
What a person reviews
Tool lists are read out of README files by a program, which can mistake a parameter or a group name for a tool. Before a server is published, its tool list is compared with the README and corrected or rejected. Servers are released in small batches, and the site owner approves each batch.
What we do not do
- We do not install or run the servers. An install config is what the publisher documents, not something we have tested. A tool list is what the README says, which can be behind the code.
- We do not assess security. Read a server's code and permissions before you give it access to your data.
- We do not rate servers, accept payment for listing, or use affiliate links.
- “Setup documented for” means the README describes setup for that client. It does not mean we confirmed it works.
Dates and sources on each page
Every fact on a server page shows a source link and the date we last checked it. Stars, open issues and the last commit date change constantly, so read them with their date. Where a page says “no source link”, treat that value as unverified.
Corrections
If a page is wrong or out of date, write to feedback@saaslenz.com. Maintainers are welcome to send corrections for their own server. For how guides are written, see the editorial policy.