Real T3 Code web thread transcript (synthetic fixture only).
Thread identifiers and provider/model metadata omitted.

USER
Discover the MCP servers repro and switchable. Call their proof_ping tools through MCP and report each exact result. Do not use a shell, file tools, or change any files or configuration. If unavailable, report that; do not repair anything.

ASSISTANT
I'll discover the `repro` and `switchable` MCP tools, then call each `proof_ping`.

ASSISTANT
Both MCP servers are unavailable.

**repro** — `namespaceStatus: error`  
Error: `This MCP server failed during live tool discovery. Its tools are unavailable until the connection is fixed.`  
`proof_ping` was not callable (only `mcp_auth` appeared; server not usable in error state).

**switchable** — `namespaceStatus: error`  
Error: `This MCP server failed during live tool discovery. Its tools are unavailable until the connection is fixed.`  
`proof_ping` was not callable (same situation).

No calls were made and nothing was repaired, per your instructions.

USER
The switchable MCP server is now disabled in Cursor project state. Discover the tools again and call repro proof_ping. Also attempt switchable proof_ping if it is still advertised. Report actual results or unavailability for both. Do not use shell or file tools and do not edit or repair anything.

ASSISTANT
Rediscovering both MCP namespaces, then calling `proof_ping` where available.

ASSISTANT
**repro** — unavailable  
`namespaceStatus: error` — `This MCP server failed during live tool discovery. Its tools are unavailable until the connection is fixed.`  
Only `mcp_auth` is listed; `proof_ping` is not callable. No call attempted.

**switchable** — unavailable  
Namespace not found (no longer advertised). Available namespaces: `cursor`, `plugin-gmail-gmail`, `plugin-google-calendar-google-calendar`, `plugin-slack-slack`, `repro`, `t3-code`.  
No `proof_ping` attempt.