← Back to search
BADGE EMBED KIT

Verified by MCP Verify badges for server authors

Give maintainers a durable backlink and buyers a fast trust signal. Claimed publishers can embed live score, freshness, OAuth, write-safe, enterprise-ready, OpenAI-compatible, Claude-compatible, and supply-chain trust badges in READMEs, docs, marketplaces, and launch posts.

Live score badge

Verified by MCP Verify badge

[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/io.sentinelsignal/scoring.svg)](https://verify.sentinelsignal.io/servers/io.sentinelsignal/scoring)
Freshness badge

Freshly validated by MCP Verify badge

[![Freshly validated by MCP Verify](https://verify.sentinelsignal.io/badge/io.sentinelsignal/scoring.svg?variant=freshness)](https://verify.sentinelsignal.io/servers/io.sentinelsignal/scoring)
HTML embed
<a href="https://verify.sentinelsignal.io/servers/io.sentinelsignal/scoring"><img src="https://verify.sentinelsignal.io/badge/io.sentinelsignal/scoring.svg" alt="Verified by MCP Verify"></a>

Badge API

Badge metadata
Returns score, checked date, public badge URL, Markdown embed, and trust badge variants.
Trust badges
Returns freshness, OAuth, write-safe, OpenAI-compatible, Claude-compatible, enterprise-ready, and supply-chain badge states.
SVG route
Use ?variant=freshness, ?variant=oauth, ?variant=write_safe, or another trust badge key.

Free badge and paid badge path

Free badge
Live score, risk level, last checked date, and link to the public profile.
Paid badge
Verified owner proof, signed badge URL, custom style, SLA/security metadata, incident status, evidence-pack link, and analytics.
Conversion funnel
Badge traffic lands on the server profile where publishers can claim, verify ownership, add evidence, monitor drift, and upgrade.
Score neutrality
Paid badge features disclose better evidence and ownership, but never buy a better Verify score.

Claim this badge

Claim this badge to verify ownership and add evidence. Claimed profiles can customize badge metadata, monitor score changes, and show verified publisher proof without changing the objective score.

Claim another server

Publisher launch checklist

1. Claim
Use the server page owner funnel to prove GitHub, DNS, or HTTP control.
2. Revalidate
Run priority validation and keep the trust snapshot fresh before embedding.
3. Publish
Add Markdown to README, docs, package pages, marketplace listings, and release notes.
4. Monitor
Subscribe to drift alerts for score, freshness, auth, schema, and write-surface changes.