Search • Governance: TrustOps / Gateway / Compare • Publishers: Claim / Badges / Profiles • Research: Trust Index / Rankings • Docs: Methodology / Security / MCP API • Pricing • Sign in
More: About • Changelog • Status • Shortlists • Digests • RSS • RSS XML • Discovery sources • Scan my server • Submit repo • GitHub Action • Docs Compiler • Agent commerce
PUBLISHER FUNNEL
Scan my MCP server
Use this entry point to find your current Verify profile, submit a missing server, claim ownership, publish badges, and set up monitoring. This does not change the objective score; it improves evidence quality and freshness.
Next step for this server
Verify can use the public index first, then route maintainers into claim and publisher evidence workflows.
1. Check current profile
If the server is already indexed, open the profile and review score, freshness, risk drivers, and policy export.
2. Claim publisher evidence
Use GitHub, DNS, HTTP, MCP metadata, or domain email proof to verify ownership.
3. Submit missing source
If the server is missing, submit the GitHub repo or public URL so it can enter discovery.
Publisher readiness checklist
Fresh validation
Keep validation evidence inside the freshness window before promoting the badge.
Healthy endpoint
Remote MCP endpoint should initialize and list tools reliably.
Metadata complete
Add description, homepage/docs/support URLs, version metadata, and public server-card data.
Ownership verified
Prove publisher control through GitHub, DNS, HTTP, MCP metadata, or domain email.
Risk reviewed
Address OAuth, write-action, destructive-tool, and protocol findings before production claims.
Badge published
Embed score and freshness badges in the README, docs, package pages, and marketplace listings.
Commercial path
Free search and badges stay public. Paid publisher profiles add verified evidence, monitoring, badge analytics, authenticated validation, and richer trust metadata without buying a better score.