Embed a live MCP Skills trust badge in any README. Standard tier badges render automatically for any scored repo or package. Certified Safe gold badges are reserved for repositories that pass an application and are monitored daily.
Renders the current trust tier (Verified, Established, New, or Blocked) as an SVG. Updates automatically whenever the score changes. No application required — works for any GitHub repo or npm package that resolves through MCP Skills.
[](https://mcpskills.io/score/owner/repo)<a href="https://mcpskills.io/score/owner/repo">
<img src="https://mcpskills.io/badge/owner/repo" alt="MCP Skills trust badge">
</a>https://mcpskills.io/.netlify/functions/badge?repo=owner%2FrepoRenders gold instead of the standard tier color. Only repositories with an active certification render the gold variant; uncertified repos fall back to the standard tier badge automatically. Use the same embed code — the badge endpoint checks certification status on every request.
Certification requires composite score ≥ 7.0, Solid dimension ≥ 5.0, ≥ 8 sufficient signals, and no disqualifiers. Apply at /certify.
What “Certified Safe” means. This repo currently meets MCP Skills' trust bar: composite score ≥ 7.0, Solid dimension ≥ 5.0, ≥ 8 sufficient signals, no disqualifiers, and ongoing daily monitoring. It is not a guarantee that no vulnerability exists. Badges are live and can be revoked if a repo drifts below the bar.
These two labels describe different things. Verified is the algorithmic trust tier — assigned automatically when a repo's composite score and dimensions pass the trust thresholds. Certified Safe is the separate badge program — an opt-in commitment that adds daily drift monitoring and gold badge rendering. A repo can be Verified without being Certified Safe.