Publish to MoCoPo

1A drop-in for mcp-publisher

npm install -g mocopo

Already using the official mcp-publisher? The verbs match — your muscle memory just works.

2Scaffold, validate, submit

mocopo publish init      # scaffold server.json (detects your git remote)
mocopo publish           # validate ./server.json + submit the listing
mocopo publish status SLUG   # trust tier + the exact next step

No key yet? mocopo register --name "My Server" --username my-server mints a tsa_ key in one call — no password, no email.

The MOAT

Every listing starts unverified and climbs as you prove more. Higher tiers rank first and unlock the verified badge; unverified self-submissions are held back from default browse.

Tier	What it means	How to earn it
unverified	Self-submitted, no proof. Ranked below verified; hidden from default browse.	mocopo publish
namespace_ verified	The reverse-DNS namespace in your name was reconciled against a real GitHub project / DNS. A repo is compulsory.	mocopo server claim SLUG
human_ verified	…plus a verified human email anchors the publisher. One email → a capped set of namespaces.	mocopo publish verify-email   --email you@yourdomain.com

The name's namespace must match the proof: io.github.acme/x requires control of the acme GitHub account — owning some repo isn't enough. This is what stops squatting on io.github.microsoft/….

Resubmit a name that already exists (e.g. one already synced from the official registry) and MoCoPo routes you to the claim flow instead of minting a duplicate:

$ mocopo publish
✗ "io.github.acme/x" is already listed. Claim the existing listing instead of resubmitting.
  Existing   https://mocopo.ai/servers/io.github.acme--x
→ Claim it instead →  mocopo server claim io.github.acme--x

Add the auto-updating badge to your repo README — it shows your live quality score and links back to your listing:

[![MoCoPo](https://mocopo.ai/badge/YOUR-SLUG)](https://mocopo.ai/servers/YOUR-SLUG)

Check what to improve, point by point: mocopo server quality SLUG.