Claim and evidence
Publish metadata about your public MCP server in the official registry so clients and marketplaces can discover and install it.
No dated example yet. Treat this tactic as a hypothesis.
Vendor claim
A tool vendor reports numbers about its own customers or product. Useful, but not independent.
Working · 2026-11 Registry documented as in preview; breaking changes or data resets may occur.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
The registry feeds downstream marketplaces and clients, so one verified listing can propagate to many places. Namespace verification builds trust.
How to run it
- Build a publicly accessible MCP server
- Write server.json metadata
- Verify namespace via GitHub or DNS
- Publish to the registry
- Track installs through downstream aggregators
Ways to run it
Design options to test, not promised results.
- Option AGitHub-verified namespace
Prove ownership through GitHub and publish under that namespace.
- Option BDomain-verified namespace
Verify through DNS so the listing carries your company domain.
- Option CTrack downstream installs
Watch which aggregators pick up the entry and where installs come from.
Dated examples
No dated example yet. Treat this tactic as a hypothesis.
Does it still work?
Registry documented as in preview; breaking changes or data resets may occur. source
Risks
- Preview status
- Private servers are not supported
- Installs depend on downstream aggregators
Sources
- modelcontextprotocol.io
“The MCP Registry is the official centralized metadata repository for publicly accessible MCP servers”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (acq-paid)