retry-trace

Inspect external HTTPS 429/503 retries with server-recorded attempts, Retry-After and arrival times.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
70%
Naming quality
97%
Poisoning risk
100%
Permission match
90%
Protocol compliance
100%

Findings (1)

  • LOWTool 'get_curl_retry_diagnostic' suggests web access but openWorldHint=falsein get_curl_retry_diagnostic

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,935Tokens (tool definitions)
~1.4 KBTypical response size
Moderate attention impact (1.51% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://retry-trace.carbaj0.chatgpt.site/mcpstreamable-http
https://retry-trace.carbaj0.chatgpt.site/api/mcpstreamable-http
https://retry.agentlife.app/api/mcpstreamable-http

What it can do

Tool inventory

No publishable tool enumeration has been recorded.

Community

Rate this Server

Evidence

Recent observations

failed observationversion not recorded—
verifiedversion not recorded7 tools
verifiedversion not recorded7 tools
failed observationversion not recorded—
verifiedversion not recorded7 tools
verifiedversion not recorded7 tools
failed observationversion not recorded—
verifiedversion not recorded7 tools
verifiedversion not recorded7 tools
failed observationversion not recorded—