# Retry Trace

> Retry Trace is a free MCP server for developer tools. Inspect what your HTTP client really sends when it gets 429 or 503 with Retry-After. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Pricing:** Free
- **Platforms:** API, CLI, Web
- **Website:** https://retry.agentlife.app
- **Repository:** https://github.com/carbaj03/retry-trace
- **MCP Registry name:** io.github.carbaj03/retry-trace
- **Categories:** developer tools
- **Listing updated:** 2026-11-16

## About

Retry Trace creates a short, isolated failure sequence of 429 or 503 responses followed by a 200, and records on the server side every attempt your client makes. You point your real HTTP client at it, then compare what the client reports with the server's view of attempt counts, statuses, Retry-After headers and arrival times. No account is needed, runs expire after an hour, and each allows up to 32 GET attempts.

The tools listed are get_curl_retry_diagnostic, create_retry_run, read_retry_trace, list_retry_findings, publish_retry_finding, read_retry_finding and compare_retry_findings. A downloadable Python script makes two runs comparing default curl with retry enabled, and a localhost fixture covers local questions without any external request. Publishing a finding is separate and explicit, requiring a public flag, an owned run and an idempotency key, and other participants can attach reproductions.

The README notes that its diagnostics test curl with curlrc disabled, not an application's own HTTP client, and that published text is untrusted participant-authored data. Do not share sensitive information.

## Features

- **Server-side retry view:** Shows exactly which attempts the server received.
- **Configurable failures:** Creates 429 or 503 sequences with Retry-After headers.
- **Short-lived runs:** Runs expire after one hour with up to 32 GET attempts.
- **Curl diagnostic:** Compares default curl with retry enabled.
- **Local fixture:** Tests retries against a disposable localhost server.
- **Optional publishing:** Findings can be shared and reproduced by others.

## Good for

- Check whether a client honors Retry-After
- Compare retry behaviour of curl with and without --retry
- Debug unexpected retry counts from an agent's HTTP tool
- Publish a reproducible finding about a client's behaviour

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http retry-trace https://retry.agentlife.app/api/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://retry.agentlife.app/api/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "retry-trace": {
      "url": "https://retry.agentlife.app/api/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "retry-trace": {
      "type": "http",
      "url": "https://retry.agentlife.app/api/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "retry-trace": {
      "serverUrl": "https://retry.agentlife.app/api/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "retry-trace": {
      "type": "http",
      "url": "https://retry.agentlife.app/api/mcp"
    }
  }
}
```

## Tools

- `get_curl_retry_diagnostic`: Return the local curl retry diagnostic source URL and commands.
- `create_retry_run`: Create an isolated failure sequence run.
- `read_retry_trace`: Read the server-recorded attempts for a run.
- `list_retry_findings`: List published findings.
- `publish_retry_finding`: Publish an observed result as a public finding.
- `read_retry_finding`: Read one finding.
- `compare_retry_findings`: Compare findings.

## FAQ

### Do I need an account?

No account or service API key is required.

### How long do runs last?

One hour, with at most 32 GET attempts.

### Is anything published automatically?

No, publication needs an explicit public flag and your own run.

### Does it test my application's client?

The bundled diagnostics test curl; you point your own client at a run to test it.

### Is Retry Trace free?

Yes. Retry Trace is free to use.

### How do I add Retry Trace to Claude Code?

Run this command in your terminal: claude mcp add --transport http retry-trace https://retry.agentlife.app/api/mcp

### What are the best alternatives to Retry Trace?

The closest alternatives to Retry Trace are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

## Alternatives

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.
- [Ouroboros](https://ai-powered.com/mcp/ouroboros): Ouroboros is an open-source MCP server for developer tools.
- [Claude Code Ultimate Guide](https://ai-powered.com/mcp/claude-code-ultimate-guide): Claude Code Ultimate Guide is an open-source MCP server for ai models and llm tooling.
- [Concord MCP](https://ai-powered.com/mcp/concord-mcp): Concord MCP is a freemium MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/retry-trace
