Maintainer access

Verify as a maintainer

Verifying ownership of a server's namespace unlocks two things: disputing a grade with priority review, and triggering an on-demand re-scan after you've shipped a fix — instead of waiting for the next nightly sync.

How verification works

We confirm you control the GitHub account or organization tied to your server's registry namespace — the same verification the MCP registry itself already requires to publish under that namespace.

Rate-limited, on purpose

Re-scan triggers are limited per server even after verification — this protects the scanning pipeline from abuse, not just from unverified requests.

Free on every tier

Verification and re-scan triggers are not a paid feature. Gating maintainer remediation behind a paywall would conflict with the entire premise of this product.

Maintainer verification isn't live yet — this page describes how it will work. Check back after launch, or see the dispute process for how to reach us in the meantime.