{"name":"cambridge-tcg","version":"1.0.0","protocol":"Model Context Protocol","protocolVersion":"2025-11-25","protocolVersions":{"offered":["2025-11-25","2025-06-18"],"also_answered":"2024-11-05","note":"initialize names the revision a standard MCP client asked for when it is one of these; callers that are not standard MCP clients (the stdio bridge, plain JSON-RPC POSTs) get 2024-11-05."},"transport":"MCP Streamable HTTP, JSON responses only, over HTTPS POST; plain JSON-RPC 2.0 POSTs are answered too","standard_remote_transport":{"streamable_http":true,"http_sse":false,"event_stream":false,"sessions":false,"oauth":false,"checked":{"on":"2026-11-11","clients":["@modelcontextprotocol/sdk 1.32.2","@modelcontextprotocol/client 2.4.0 (default and auto version negotiation)"],"how":"connected with a static bearer key and with none, listed tools, called one, read a refusal, pinged; the route served on 127.0.0.1 with its database, key lookup, rate limiter and tool handlers mocked (apps/storefront/scripts/mcp-sdk-harness), not against cambridgetcg.com"},"note":"/api/mcp speaks the JSON-response form of MCP Streamable HTTP, revisions 2025-06-18 and 2025-11-25, with no event stream and no sessions. On 2026-11-11 @modelcontextprotocol/sdk 1.32.2 and @modelcontextprotocol/client 2.4.0 connected to it with a static bearer key, listed and called its tools and read a refusal (the route run locally with its database, key lookup, rate limiter and tool handlers mocked, not cambridgetcg.com). It has no OAuth, so hosted chat apps that connect only through OAuth cannot call its keyed tools, and an MCP client set up for OAuth may, on a 401, look for OAuth metadata that does not exist here and report that instead of the refusal. The stdio bridge (packages/mcp-server, not on npm) remains for clients that only speak stdio."},"methodology":"https://cambridgetcg.com/methodology/agents","discover":{"mcp_spec":{"method":"tools/list","auth":"none"},"cambridge_native":{"method":"mcp.list_tools","auth":"none"}},"initialize":{"method":"initialize","auth":"none"},"call":{"mcp_spec":"POST { jsonrpc: \"2.0\", id, method: \"tools/call\", params: { name, arguments } }","cambridge_native":"POST { jsonrpc: \"2.0\", id, method: \"<dotted-name>\", params: {...} }"},"auth":"Authorization: Bearer ctcg_agt_<token> on every tools/call except mcp.list_tools and agent.act; agent.act takes a signed act instead (signed_acts below)","signed_acts":{"tool":"agent.act","rest_twin":"POST https://cambridgetcg.com/api/v1/agents/act","auth":"one signed act (a compact JWS, typ ctcg-act.v1, Ed25519) from a key the agent's operator bound at /account/agents; Authorization is not read","scope":"operator-managed agents only; acts signer.check, key.mint and key.revoke, each with a preview that writes nothing","availability":"closed unless the deployment opens it; closed, it answers signed_acts_closed and reads nothing","proves":"control of the key over the signed bytes; not identity, consent, or authority to act for anyone else","docs":"https://cambridgetcg.com/methodology/agents#signed-acts","open_on_this_deployment":false},"provision":{"self_serve_registration":"paused","existing_self_serve_keys":"read-only","operator_managed":"https://cambridgetcg.com/account/agents","status":"https://cambridgetcg.com/api/v1/agents/register"},"read_only_scope":{"domain_state":true,"operational_metadata_writes":["per-key rate-limit bucket for allowed authenticated calls","agent key last-used timestamp after successful authenticated calls","agent_keys.revoked_at and revoked_reason for this key when its holder calls agent.revoke_key with confirm: true","deletion of rate-limit buckets older than seven days, any key's, by each allowed authenticated call, even one then refused","an aggregate count per UTC day of requests by JSON-RPC method, tool, authenticated or not, and outcome, with no key, agent or account id (kept 13 months)"]},"revocation":{"tool":"agent.revoke_key","auth":"Bearer (the key being revoked)","confirm":"confirm: true; without it, a preview","scope":"the presented key only"},"stdio_bridge":{"status":"source public; not published to npm","source":"packages/mcp-server in the Cambridge TCG monorepo (public repository at https://github.com/cambridgetcg/Cambridge-TCG-monorepo; the workspace packages are not published to npm)","planned_npm_name":"@cambridge-tcg/mcp-server","honest_note":"Not on the npm registry (404, rechecked 2026-10-10), so 'npx @cambridge-tcg/mcp-server' does not work. The source repository is public, so the bridge can be built from a clone (packages/mcp-server: npm install, npm run build). Clients that can POST JSON-RPC 2.0 call this endpoint directly, and MCP clients that speak Streamable HTTP and can send an Authorization header should be able to (two MCP SDK clients did on 2026-11-11, with the route run locally; see standard_remote_transport.checked); the bridge remains for clients that only speak stdio.","for":"Any MCP client that only speaks stdio and expects a local server."},"config_snippet":"https://cambridgetcg.com/.well-known/mcp-config.json","discovery_doc":"https://cambridgetcg.com/.well-known/mcp.json"}