Step 2 — Official MCP Registry

Discovery plumbing (secondary). This page makes the service findable by someone already searching; it does not replace pipeline work (page 00). Do it once; no paid tier, listing or upgrade (hard rule 6).

Prerequisite: Step 1 complete (PyPI package live).

What this is: registry.modelcontextprotocol.io is the upstream, metadata-only registry that downstream directories (Glama, mcp.so, PulseMCP) read from. One good entry here propagates.

Do this

1. Install the publisher CLI on the build machine (see github.com/modelcontextprotocol/registry for the current install command — it is the mcp-publisher tool).
2. The manifest already exists in the repository: integrations/mcp/listing/server.json (namespace com.apertureapi/, registryType pypi, package apertureapi-mcp 0.1.0). Do not rewrite it — if the CLI reports a schema mismatch, report back rather than improvising.
3. Authenticate. Namespace com.apertureapi/* is claimed by proving control of the apertureapi.com domain (DNS or HTTP challenge — the CLI walks you through it; the operator must add the DNS TXT record if asked). GitHub-based auth is the alternative if the server is published under a GitHub namespace — for our custom domain namespace, use the DNS route.
4. mcp-publisher publish from integrations/mcp/listing/.
5. Verify: curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=apertureapi" returns the entry.

Artifact

• The registry API URL above returning our entry (save the JSON).
• Tracking line with date + account/domain-proof method used.

Buyer pages to pair with this page: workflow fit. Pipeline stages and KPIs: page 00.