Remote MCP · Endpoint

Span-level replay: fork from the failure MCP server

No. Span-level replay: fork from the failure answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://textforagents.com/products/span-level-replay-fork-from-failure/mcp

The last check completed an MCP handshake.

Registry name
com.textforagents/span-level-replay-fork-from-failure
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
46 ms
Tools exposed
2 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Fork-replay one recorded span from a failed agent run and get an attribution verdict.
Website
https://textforagents.com/products/span-level-replay-fork-from-failure/
Listing
From the official MCP registry (active).
Recent checks of Span-level replay: fork from the failure
CheckedResultHandshake
34 minutes agoHandshake completed46 ms
9 days agoHandshake completed58 ms
10 days agoHandshake completed70 ms
11 days agoHandshake completed42 ms
12 days agoHandshake completed45 ms
14 days agoHandshake completed57 ms
14 days agoHandshake completed50 ms
15 days agoHandshake completed53 ms
17 days agoHandshake completed56 ms
19 days agoHandshake completed20 ms
21 days agoHandshake completed15 ms
24 days agoHandshake completed18 ms
26 days agoFailed - the server returned an HTTP error—

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Span-level replay: fork from the failure and makes no claim about it beyond what these checks measured.