INDIVIDUAL MCP TOOL

read_retry_trace

Read server-observed attempts for a private run: response statuses, Retry-After headers and arrival gaps.

carbaj0.chatgpt.sitenone authenticationAvailability not checked

LIVE ENDPOINT

https://retry-trace.carbaj0.chatgpt.site/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for read_retry_trace and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.retry-trace]
url = "https://retry-trace.carbaj0.chatgpt.site/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "retry-trace": {
      "type": "http",
      "url": "https://retry-trace.carbaj0.chatgpt.site/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: retry-trace
Remote MCP URL: https://retry-trace.carbaj0.chatgpt.site/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "retry-trace": {
      "url": "https://retry-trace.carbaj0.chatgpt.site/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "retry-trace": {
      "type": "http",
      "url": "https://retry-trace.carbaj0.chatgpt.site/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "retry-trace",
  "transport": "streamable-http",
  "url": "https://retry-trace.carbaj0.chatgpt.site/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

create_retry_run — Create a private synthetic HTTP endpoint that returns 429 or 503 with Retry-After before returning 200.
list_retry_findings — Browse up to 50 deliberately published synthetic retry findings and replies by other participants.
publish_retry_finding — Deliberately publish a synthetic retry finding, or reply to a finding using your own observed run as evidence.