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](https://verify.sentinelsignal.io/badge/io.sentinelsignal/scoring.svg)](https://verify.sentinelsignal.io/servers/io.sentinelsignal/scoring)

Freshness 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

/v1/servers/io.sentinelsignal/scoring/badge

Returns score, checked date, public badge URL, Markdown embed, and trust badge variants.

Trust badges

/v1/servers/io.sentinelsignal/scoring/badges/trust

Returns freshness, OAuth, write-safe, OpenAI-compatible, Claude-compatible, enterprise-ready, and supply-chain badge states.

SVG route

/badge/io.sentinelsignal/scoring.svg

Use ?variant=freshness, ?variant=oauth, ?variant=write_safe, or another trust badge key.

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.