For MCP server maintainers
If your server has a page in the MCP servers directory, this page explains where its facts come from and what you can do about them. If it does not have a page yet, the reason is almost always one of the requirements below.
How a server gets a page
We find servers in the official MCP registry and on GitHub. There is no submission form and no payment. A server is listed when it has a public repository with a licence, an install config (from its registry entry or its README), a tool list in its README, and recent activity, as set out in How we verify. Meeting the requirements does not guarantee a page: we publish in small batches and check each one by hand.
The most useful thing you can do for your own listing is to make those facts easy to read: a licence file GitHub recognises, a README section headed “Tools” that lists every tool name, a config block for each client you support, and an entry in the official registry.
Correcting a page
Every fact on your page links to its source. If a value is wrong, fix the source (your README or registry entry) and tell us at feedback@saaslenz.com with the server and the field, or just write to us and we will check it. If you would rather not be listed, write to the same address.
A badge for your README
This is optional. The badge says your server is listed here and links to its page. It does not say anything about quality, because we do not rate servers.
Add this to your README, replacing <slug>with the last part of your page's URL (for a server at https://saaslenz.com/mcp/acme-my-server it is acme-my-server):
[](https://saaslenz.com/mcp/<slug>)Each server page also shows its own ready-to-copy snippet. Please only add the badge to a server that has a page.