MCP transport ownership | BEFORE | dfd2187ccb0f7d16b0ff6d13f79eb5236ca9c46f Environment: Linux; real Node server; loopback HTTP; fresh isolated database Protocol: 2025-06-18 | secrets and session IDs omitted Owner A: separate MCP OAuth credential issued via registration + pairing + PKCE (HTTP 200) Other B: separate MCP OAuth credential issued via registration + pairing + PKCE (HTTP 200) Session 1 A initialize -> HTTP 200; Mcp-Session-Id received Session 1 A notifications/initialized -> HTTP 202 A POST tools/list before attack -> HTTP 200; 71 tools returned B POST tools/list with A session -> HTTP 200; 71 tools returned B GET with A session -> HTTP 405 B DELETE with A session -> HTTP 204 A POST tools/list after B DELETE -> HTTP 404 A DELETE own session -> HTTP 404 Control session A initialize -> HTTP 200; Mcp-Session-Id received Control session A notifications/initialized -> HTTP 202 Control A POST tools/list -> HTTP 200; 71 tools returned Control A DELETE -> HTTP 204 No credential POST -> HTTP 401; {"error":"invalid_mcp_credential","message":"A valid T3 Code MCP credential is required."} Junk credential POST -> HTTP 401; {"error":"invalid_mcp_credential","message":"A valid T3 Code MCP credential is required."} Revoked B credential POST -> HTTP 401; {"error":"invalid_mcp_credential","message":"A valid T3 Code MCP credential is required."} END: same request sequence completed; HTTP responses above are from the real server