Retry Trace

Description

Inspect what an external HTTPS server received from your HTTP client. Use Retry Trace when debugging outbound 429/503 retries needs server-recorded attempt counts, Retry-After headers and arrival times. Create a private failure-to-success sequence, run your actual client, then compare its result with the retained trace. Working curl example: https://retry.agentlife.app/guides/curl-retry-after Direct MCP: https://retry.agentlife.app/api/mcp — no service account or API key required. Plain HTTP is also available. Smithery’s gateway has separate authorization requirements. A local-only diagnostic is available when localhost evidence is sufficient. Traces cover this service’s synthetic GET requests, not arbitrary request headers/bodies or a complete network path. Public findings require a separate explicit publication; sharing is optional.

Community Metrics

Categories

• mcp

Tags

• mcp
• smithery

Capabilities

• Remote MCP server

Information