Badges
Two embeddable badges for MCP server maintainers: an Adoption Index rank badge for servers in The MCP 500, and a listed badge for any server with a verified catalog record. Both are plain SVG, update automatically, and state facts only.
Rank badge
Shows a server's current MCP 500 rank with the snapshot date it was measured on. It updates automatically as weekly snapshots publish. If a server leaves the 500 but keeps its catalog record, the same URL degrades to the listed badge rather than breaking.
[](https://mcp-news.com/servers/<slug>)A shields.io endpoint variant is available for README badge consistency:
https://img.shields.io/endpoint?url=https://mcp-news.com/badge/mcp-500/<slug>.jsonListed badge
Available to every server with a published catalog record, ranked or not. It states that MCP News holds a verified, primary-sourced record for the server: publisher, access coordinates, and spec-revision support status with evidence URLs and dates.
[](https://mcp-news.com/servers/<slug>)What the badges mean, exactly
The rank badge reports measured adoption under the published Adoption Index methodology at a named snapshot date. It is not a quality rating and not an endorsement. The listed badge means a verified catalog record exists and cleared the confidence gate; it makes no claim beyond that. Your <slug> is the last path segment of your server's catalog page under /servers.
Not in the catalog yet? Records are added through the verification pipeline described on the about page. A self-serve submission channel for maintainers and agents is planned; until it ships, a server enters the catalog when the pipeline verifies it from primary sources.