MCP OAuth client-interop conformance: prove real clients can connect

{
  "name": "MCP OAuth client-interop conformance: prove real clients can connect",
  "type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",
  "active": true,
  "services": [
    {
      "name": "web",
      "endpoint": "https://textforagents.com/products/mcp-oauth-client-interop-conformance/"
    },
    {
      "name": "A2A",
      "version": "1.0",
      "endpoint": "https://textforagents.com/agent-cards/mcp-oauth-client-interop-conformance.json"
    },
    {
      "name": "MCP",
      "version": "2024-11-05",
      "endpoint": "https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp"
    }
  ],
  "description": "Run five scripted client profiles encoding documented real-client OAuth behaviours (MCP Inspector, Claude Desktop, Cursor, Claude Code, VS Code) over real HTTP against an authorization-server fixture built to the server shape you describe, and get a perishable per-cell verdict — PASS, or FAIL with the exact failing step and a step-exact shim prescription. It reproduces the three documented breaks: Cursor x Cognito-like DCR, Claude Code x Cognito-like DCR-despite-client_id (#38102), VS Code x strict-loopback redirect port. Fixture shapes, not live tenants. Per-check $0.01 · Solo $9/mo per server · Fleet $29/mo (not self-serve).",
  "x402Support": true,
  "registrations": [
    {
      "agentId": 340001,
      "agentRegistry": "eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432"
    }
  ],
  "supportedTrust": [
    "reputation"
  ]
}