Get your plugin verified
Every verified plugin on ClaudeRegistry passes a seven-check security audit. Pass it, and your plugin carries the badge - proof for users, and for their AI agents, that your code does what it says.
Why authors do it
The badge means something
It is backed by a public methodology, machine-readable per-check results, and CI that revokes it the moment the code drifts. A badge that can’t go stale quietly is a badge users can trust.
Agents read it too
Verification status ships in the registry’s MCP server, llms.txt, and verified.json. When an AI agent picks a plugin to recommend, yours carries machine-readable audit evidence.
Homepage rotation
The clauderegistry.com homepage features verified plugins in a weekly rotation - every verified plugin gets its turn in front of visitors.
Distribution where developers work
Listed in the catalog, installable in two commands, searchable from inside Claude Code and any MCP client.
Pick your tier
Listed
Your repo, your pace- Plugin stays in your repository
- Structural validation plus human review
- Users install straight from your repo
- No badge - nothing pins what the code is
Verified at commit
Your repo, our audit- Plugin stays in your repository
- Full seven-check audit at a pinned commit
- Badge reads "verified @<short-sha>" - true forever
- Daily drift watchdog flags when your repo moves past the pin
Verified
Strongest tier- Plugin vendored into the registry repo
- Seven checks re-run by CI on every change
- Human review of hook and agent code
- Badge always describes exactly what users install
From repo to badge
- 1
Run the checker
Point the plugin checker at your repo. It runs the exact seven checks in your browser and names every failing file.
Open the checker → - 2
Fix what fails
Most failures take minutes: add frontmatter descriptions, scope your agent tools, flesh out the README. The methodology page explains what each check demands.
Read the methodology → - 3
Open a PR
Pick your tier, follow the contributing guide, and open a PR against the marketplace repo. CI re-runs the checks; a maintainer reviews your hook and agent code.
Contributing guide → - 4
Ship the badge
On merge your plugin is listed, verified, and the badge goes live at clauderegistry.com/badge/<your-plugin>.svg - embed it in your README.