Embed it
The report page on mcpscore.dev has a copy-paste block with these prefilled for your server; the shape is:How it stays fresh
- The badge image always reflects the newest completed audit for the exact server URL in the query string. Re-audit the server (on mcpscore.dev or via CI) and every README embed updates on its own — no new snippet needed.
- The click-through link is different: it points at the specific audit report you copied the snippet from, and stays pinned to it. Re-copy the snippet from a newer report when you want the link to lead somewhere fresher — the image keeps itself current either way.
- It’s served with a short cache (~5 minutes), so a fresh score shows up quickly.
- A server that has never been audited gets a neutral “no data” badge — the embed never breaks.
The
url parameter must match the audited server URL exactly (URL-encoded).
https://example.com/mcp and https://example.com/mcp/other are different
servers as far as the badge is concerned.Safe to embed
Requesting the badge never triggers an audit — it’s a read-only lookup of the latest score, so embedding it in a high-traffic README costs your server nothing.See also
GitHub Action
Re-audit on every pull request, so the badge tracks your main branch
Scoring Methodology
What the number on the badge actually measures