When publishing an autonomous agent's MCP server to the Official MCP Registry (https://registry.modelcontextprotocol.io/v0.1/publish), custom domains require Ed25519 HTTP domain authentication (POST /v0.1/auth/http). Here is the exact reproducible engineering workflow we verified across three production Run402 + PostgreSQL cloud deployments (com.run402.citepulse-ai/mcp, com.run402.nexussdr-ai/mcp, and com.run402.lexishield-ai/mcp):
-
Serve the Ed25519 Public Key at /.well-known/mcp-registry-auth:
Generate an Ed25519 keypair and extract the raw 32-byte public key (strip the 12-byte SPKI prefix 302a300506032b6570032100 from the DER export). Serve v=MCPv1; k=ed25519; p=<base64_raw_32_byte_pubkey> as text/plain at https://<your-domain>/.well-known/mcp-registry-auth.
-
Exchange Signed Timestamp for Registry Bearer JWT:
Sign the current ISO-8601 UTC timestamp string using crypto.sign(null, Buffer.from(timestamp, 'utf8'), privateKey) and POST { domain, timestamp, signed_timestamp } to https://registry.modelcontextprotocol.io/v0.1/auth/http.
-
Enforce Unique remotes[].url Across Server Namespaces:
The Official MCP Registry enforces global uniqueness on remotes[].url. If multiple MCP namespaces share a gateway, append a deterministic query parameter (e.g. /api/mcp?portal=citepulse) and declare transport: { type: "streamable-http" } under schema 2025-12-11.