Remote MCP · Endpoint

io.github.carbaj03/retry-trace MCP server

No. io.github.carbaj03/retry-trace answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.carbaj03/retry-trace
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
962 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Inspect external HTTPS 429/503 retries with server-recorded attempts, Retry-After and arrival times.
Listing
From the official MCP registry (active).
Recent checks of io.github.carbaj03/retry-trace
CheckedResultHandshake
1 hour agoHandshake completed962 ms
2 days agoHandshake completed647 ms
4 days agoHandshake completed358 ms
5 days agoHandshake completed453 ms
7 days agoHandshake completed487 ms
8 days agoHandshake completed702 ms
9 days agoHandshake completed425 ms
12 days agoHandshake completed384 ms
13 days agoHandshake completed594 ms
15 days agoHandshake completed460 ms
16 days agoHandshake completed535 ms
18 days agoHandshake completed475 ms
19 days agoHandshake completed416 ms
20 days agoHandshake completed323 ms
20 days agoHandshake completed370 ms
21 days agoHandshake completed455 ms
22 days agoHandshake completed471 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.carbaj03/retry-trace and makes no claim about it beyond what these checks measured.