Verification
Embedding the badge
Every listing has an embeddable status badge: a small SVG you drop into your README or website footer that links back to your MCPVault page. It is not a static image. The badge is rendered live from your listing's current status, so when your server gets verified, every badge you have placed updates itself the moment the status changes. No re-copying, no stale claims.
How it works
The badge lives at a stable URL per server:
Badge endpoint
$ https://mcpvault.io/badge/your-server-slug.svg
The SVG says CLAIMED or VERIFIED depending on the listing's real status in the vault, with the matching color. Because it is served from our side, it cannot drift out of date and it cannot be faked: a badge claiming VERIFIED resolves against the actual record.
Markdown and HTML
Your listing's badge page generates ready-to-paste snippets, so you never need to write these by hand: Markdown for the README and HTML for a website footer, each wrapped in a link back to your listing. Find it from your server page or dashboard under "Get the embed code".
Light and dark
The badge ships in two themes. The default suits light backgrounds; append ?theme=dark to the SVG URL for dark backgrounds. The badge page shows both variants rendered live so you can pick by eye.
Part of staying verified
For verified servers the badge is more than decoration: keeping it visible in your repository README or on your project site is the condition of free verification. Our re-check harness looks for it on every run. Remove the badge and verification lapses until it is back; the full mechanics are on The verified badge. In return, verified listings link back to your site with a do-follow link, so the badge and the listing feed authority to each other.