Documentation
The verified badge
Stars measure popularity. Grades measure code signals. The verified badge measures the thing users actually care about: does this server work right now. Verification means we tested the server ourselves, not that the author says it works.
Only claimed servers can be verified, because verification requires cooperation from the maintainer for servers that need credentials or configuration.
What we test
It responds
We start the server or connect to its endpoint and complete an MCP handshake. Dead servers do not get badges.
Tools answer
We list the server's declared tools and confirm the interface matches what the listing claims.
It stays alive
Verification is re-run on a schedule. A server that stops working loses the badge until it passes again, so the badge always reflects the current state.
What the badge unlocks
- +The green VERIFIED badge on your listing and in directory browsing
- +A do-follow link to your project site or repository
- +Priority placement within your category
- +A verification timestamp shown on the listing, so users know it was tested recently
Verification is a paid tier for maintainers who want the trust signal. Payment buys the testing work and the placement, never the result: a server that fails verification does not get the badge, paid or not.