← Back to search
MISSING FROM VERIFY?

Submit GitHub repo

Add an MCP server repository to the discovery review queue. Verify will create a pending profile, include it in discovery checks, and let maintainers claim ownership for evidence, badges, monitoring, and revalidation.

Search • Sprawl Radar • TrustOps • Gateway • Ledger • Mandates • Hosting • Docs Compiler • Demo • Trust Index • Discovery Sources • Submit Repo • GitHub Action • Plans • Intelligence API • Verified Profiles • Shortlists • Rankings • Compare • Badges • ChatGPT compatible • Claude compatible • Healthcare • Digests • RSS • RSS XML • Backfill • MCP API
What happens after submission
Verify normalizes the repo URL, creates or updates a pending profile, includes it in discovery checks, and exposes a claim path after the first scan.
Review states
submitted → discovery_review → pending_validation → claim_after_scan → verified_profile
Accepted URL formats
https://github.com/org/repo
github.com/org/repo
org/repo
Publisher path
Verified Server Profile adds verified identity, evidence packs, monitoring, badge analytics, and richer metadata. Discovery Sources explains what Verify crawls.
WHAT HAPPENS NEXT
  1. We create a pending profile.
  2. We scan repo metadata and MCP signatures.
  3. We attempt validation/introspection.
  4. You can claim ownership.
  5. Claimed owners can revalidate, add evidence, and publish badges.
No submission yet.