retry-trace

Name: retry-trace
Author: carbaj03

MCP serverMCP

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

by carbaj03repository ↗homepage ↗v1.1.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"retry-trace","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability218/218 checks ok

Endpoints

https://retry.agentlife.app/api/mcpmcp streamable http · checked on a schedule
https://retry-trace.carbaj0.chatgpt.site/api/mcpmcp streamable http · checked on a schedule

Registry facts

Not distributed through a package registry we index.

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	199 ms	server retry-trace 1.1.1 · protocol 2025-06-18 · 7 tools
2 h ago	mcp initialize	ok	200	176 ms	server retry-trace 1.1.1 · protocol 2025-06-18 · 7 tools
8 h ago	mcp initialize	ok	200	203 ms	server retry-trace 1.1.1 · protocol 2025-06-18 · 7 tools
8 h ago	mcp initialize	ok	200	297 ms	server retry-trace 1.1.1 · protocol 2025-06-18 · 7 tools
14 h ago	mcp initialize	ok	200	304 ms	server retry-trace 1.1.1 · protocol 2025-06-18 · 7 tools
16 h ago	mcp initialize	ok	200	242 ms	server retry-trace 1.1.1 · protocol 2025-06-18 · 7 tools
21 h ago	mcp initialize	ok	200	131 ms	server retry-trace 1.1.1 · protocol 2025-06-18 · 7 tools
23 h ago	mcp initialize	ok	200	106 ms	server retry-trace 1.1.1 · protocol 2025-06-18 · 7 tools
29 h ago	mcp initialize	ok	200	186 ms	server retry-trace 1.1.1 · protocol 2025-06-18 · 7 tools
29 h ago	mcp initialize	ok	200	143 ms	server retry-trace 1.1.1 · protocol 2025-06-18 · 7 tools

Tools observed via MCP handshake

get_curl_retry_diagnostic — Get a downloadable localhost diagnostic for installed curl: compare default behavior with --retry 1 against HTTP 429/503 and Retry-After seconds/date headers. R
read_retry_finding — Read a public diagnostic record and up to 50 direct replies. Returns frozen evidence and exact settings to create your own private reproduction. Reading never a
compare_retry_findings — Compare two public records: scenario differences, stored statuses, attempt counts and arrival gaps. No correctness verdict or proof of independent reproduction.
create_retry_run — Create a private synthetic HTTP endpoint that returns 429 or 503 with Retry-After before returning 200. Use your own HTTP client to GET the returned probe_url,
read_retry_trace — Read server-observed attempts for a private run: response statuses, Retry-After headers and arrival gaps. Arrival gaps include network/server effects; they do n
list_retry_findings — Find up to 50 public diagnostic records by title/summary text, HTTP status or Retry-After format. Each record includes a reusable scenario and permanent pilot U
publish_retry_finding — Save a reusable public diagnostic record with a stable URL, JSON export and frozen trace, even after the probe expires. Use it as a reference for your own work

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.carbaj03/retry-trace

first seen 1 mo ago · fetched 3 d agoopen ↗

Field history (12 recent events)

6 d ago · declared · version → "1.1.1"
6 d ago · declared · description → "Inspect external HTTPS 429/503 retries with server-recorded attempts, Retry-After and arrival times."
6 d ago · declared · summary → "Inspect external HTTPS 429/503 retries with server-recorded attempts, Retry-After and arrival times."
11 d ago · declared · summary → "Test curl retries locally or inspect remote 429/503 Retry-After traces; optionally share findings."
11 d ago · declared · version → "1.1.0"
11 d ago · declared · description → "Test curl retries locally or inspect remote 429/503 Retry-After traces; optionally share findings."
1 mo ago · declared · homepageUrl → "https://retry.agentlife.app"
1 mo ago · declared · version → "1.0.2"
1 mo ago · declared · description → "Test HTTP 429/503 retries and Retry-After with server-observed traces; share synthetic findings."
1 mo ago · declared · protocols → ["mcp"]
1 mo ago · declared · version → "1.0.1"
1 mo ago · declared · repoUrl → "https://github.com/carbaj03/retry-trace"

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from