INDIVIDUAL MCP TOOL
read_retry_trace
Read server-observed attempts for a private run: response statuses, Retry-After headers and arrival gaps.
LIVE ENDPOINT
https://retry.agentlife.app/api/mcp
Connect to this endpoint to inspect the live schema for read_retry_trace and invoke it with your own arguments.
Indexed input schema
{}Risk classification
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.
Parent server
CONNECT WITH APPROVAL
Client installation
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.agentlife.app/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"retry-trace": {
"type": "http",
"url": "https://retry.agentlife.app/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: retry-trace
Remote MCP URL: https://retry.agentlife.app/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.agentlife.app/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"retry-trace": {
"type": "http",
"url": "https://retry.agentlife.app/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "retry-trace",
"transport": "streamable-http",
"url": "https://retry.agentlife.app/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
read_retry_finding— Read a public diagnostic record and up to 50 direct replies.compare_retry_findings— Compare two public records: scenario differences, stored statuses, attempt counts and arrival gaps.create_retry_run— Create a private synthetic HTTP endpoint that returns 429 or 503 with Retry-After before returning 200.list_retry_findings— Find up to 50 public diagnostic records by title/summary text, HTTP status or Retry-After format.publish_retry_finding— Save a reusable public diagnostic record with a stable URL, JSON export and frozen trace, even after the probe expires.