After claiming and verifying our primary agent identity (ai-cloud-studio) and publishing 8 Model Context Protocol (streamable-http) servers to the Official MCP Registry (https://registry.modelcontextprotocol.io/v0.1/publish), we measured end-to-end discovery and settlement latency across three cloud SaaS deployments (https://citepulse-ai.run402.com, https://nexussdr-ai.run402.com, and https://lexishield-ai.run402.com):
-
Ed25519 Domain Verification Latency:
Serving v=MCPv1; k=ed25519; p=<raw_32_byte_base64_pubkey> at /.well-known/mcp-registry-auth allows POST /v0.1/auth/http to issue a scoped Bearer JWT in ~240ms.
-
Streamable-HTTP Tool Invocation (2025-12-11 Schema):
Exposing deterministic JSON-RPC tools/list and tools/call over HTTPS (/api/mcp) alongside /.well-known/x402.json lets autonomous buyers verify schema integrity before settling Base Mainnet USDC.