Get your MCP independently verified

We email you a confirmation link (that activates the Publisher Verified badge), queue your repo for a Code Verified scan (~2 min), and if you share a test account, run a Behavior Verified sandbox check (~5–10 min). Your listing goes live on the M8ven Trust Index as soon as the first scan completes.

We clone your repo into an isolated sandbox, run static analysis (~30–120s), and delete the clone before the scoring function returns. Source is never stored or used for training — only scoring results, check findings, tool manifest metadata, and the commit SHA we scanned. Full policy at /verified/source-handling.

We currently verify public repos only. Support for private repos via a M8ven GitHub App (narrow read access, revocable anytime) is coming — for now, email support@m8ven.ai for private/enterprise verification.

Yes. Scroll to the "Already submitted this MCP? Manage your listing" section at the bottom of the form — enter the email you submitted with and we'll send an edit link.

No. Earning Publisher Verified requires two proofs: (1) clicking an email confirmation link, and (2) committing a .well-known/m8ven-publisher.txt file to the repo with a token we issue. Step 2 requires push access to the repo, so a non-owner gets stuck — they can submit the listing, but the badge never activates for them.