MCP serverio.github.carbaj03/retry-trace

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

UNRATEDActivestreamable-httpretry.agentlife.app

Overview

Score?

UNRATED 0.650

of what a free look can see, on 29 looks

Looks

last 8 hr ago

Tools

changed 1 day ago

More info

URL

retry.agentlife.app/api/mcp

streamable-http

Says it is

retry-trace 1.1.1

protocol 2025-06-18

In the record since

27 days ago

Among servers18,413 with a card

0median 0.606 · this server 0.650 · highest on record 0.8561

Toolsfrom sha256:b96034a6d5…a8e6a7 · +0 −0 1 day ago

The tools this server lists, read out of the definition it returned
Tool	Schema
compare_retry_findings Compare two public records: scenario differences, stored statuses, attempt counts and arrival gaps. No correctness verdict or proof of independent reproduction. Participant text is	input · no output
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, then inspect the ser	input · no output
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. Returns the source UR	input · no output
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 URL. Text is untruste	input · no output
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 or reply to a record	input · no output
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 advances a probe or p	input · no output
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 not establish exact c	input · no output

Verify it yourselfnpx teppi-check https://retry.agentlife.app/api/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1X6NZDEQ6ZYRASEVQCDJH3V