README badge

Wear the receipt.

Once your namespace is verified, drop this badge in your README. It links straight to your server’s signed history on RCX-Registry — a trust signal for your users and a backlink to the proof.

/badge/verified.svg

Copy & paste

Two snippets, one placeholder

Swap <your-namespace> for your server’s canonical name (for example com.example/my-mcp-server). The link resolves to that server’s signed-history page on the registry.

Markdown

[![Verified on RCX-Registry](https://rcxprotocol.org/badge/verified.svg)](https://registry.rcxprotocol.org/servers/<your-namespace>)

HTML

<a href="https://registry.rcxprotocol.org/servers/<your-namespace>">
  <img src="https://rcxprotocol.org/badge/verified.svg" alt="Verified on RCX-Registry" height="20">
</a>

Why it’s worth it

A badge that actually means something

It’s earned

The badge only makes sense after you’ve proven namespace control by DNS or GitHub. It isn’t a decoration — it’s backed by a rights-verification receipt.

It links to proof

Clicking through lands on your server’s signed history — snapshots, declarations, verifications — that anyone can replay. Not a logo that links to a marketing page.

It compounds

Every badge is a backlink and a trust signal. Users see it, other publishers see it, and answer engines index it. Verification becomes visible where developers already look.

Not verified yet?

Claim your namespace first — DNS TXT or GitHub OAuth, minutes either way — and the badge is yours.

Claim your namespace How verification works