Retry Trace is answering right now. Last checked 11 min ago. It exposes 6 tools. Last commit 9 Sep 2026.
Test HTTP 429/503 retries and Retry-After with server-observed traces; share synthetic findings.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 September 2026. No other catalogue keeps this.
We read the source, 17 h ago · tools taken from the live server · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
version = subprocess.run([curl, "-q", "--version"], capture_output=True,
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
claude mcp add retry-trace --transport http https://retry-trace.carbaj0.chatgpt.site/api/mcp
{
"mcpServers": {
"retry-trace": {
"url": "https://retry-trace.carbaj0.chatgpt.site/api/mcp"
}
}
}
[mcp_servers.retry-trace]
url = "https://retry-trace.carbaj0.chatgpt.site/api/mcp"
{
"mcpServers": {
"retry-trace": {
"url": "https://retry-trace.carbaj0.chatgpt.site/api/mcp"
}
}
}
{
"mcpServers": {
"retry-trace": {
"url": "https://retry-trace.carbaj0.chatgpt.site/api/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
create_retry_run
list_retry_findings
read_retry_finding
read_retry_trace
compare_retry_findings
publish_retry_finding
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://retry-trace.carbaj0.chatgpt.site/api/mcp | streamable-http | answering | 1884 ms | 11 min ago |
| https://retry.agentlife.app/api/mcp | streamable-http | answering | 404 ms | 11 min ago |
New Relic MCP server with 55 tools for APM, alerts, dashboards, synthetics, workflows, and more.
Access New Relic observability data through MCP - query metrics, logs, traces, entities, and more
Public MCP digital twin with synthetic systems and an agent firewall. No customer data.
Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots.
MCP server for querying logs from observability platforms with unified search and tracing
Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.
Interact with Opik prompts, traces, datasets and metrics through the Model Context Protocol.
Query application logs, traces, and metrics from your AI coding assistant via Foam's MCP server.
Answers built from our own checks of this server.