mcpbeat Sign in

Span-level replay: fork from the failure MCP Server

answering

Span-level replay: fork from the failure is answering right now. Last checked 5 min ago. It exposes 2 tools.

Fork-replay one recorded span from a failed agent run and get an attribution verdict.

Uptime history 5 days of history · worst day 97%
5 days agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
320 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 October 2026. No other catalogue keeps this.

21 Oct a tool appeared fork_safety_check

Span-level replay: fork from the failure does not always answer

Over the last week it answered 99.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add span-level-replay-fork-from-failure --transport http https://textforagents.com/products/span-level-replay-fork-from-failure/mcp
Settings → Connectors → Add custom connector, then paste this address
https://textforagents.com/products/span-level-replay-fork-from-failure/mcp
~/.codex/config.toml
[mcp_servers.span-level-replay-fork-from-failure]
url = "https://textforagents.com/products/span-level-replay-fork-from-failure/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "span-level-replay-fork-from-failure": {
      "url": "https://textforagents.com/products/span-level-replay-fork-from-failure/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "span-level-replay-fork-from-failure": {
      "type": "http",
      "url": "https://textforagents.com/products/span-level-replay-fork-from-failure/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fork
fork_safety_check
Examine ONE recorded span (or a run's span set) forensically — canonicalization, env binding, completeness, stub coverage — and return the fork-safety verdict (FORK-SAFE-LIVE / FORK-SAFE-STUBBED / FORK-DEGRADED / FORK-UNSAFE) WITHOUT executing the span or forking anything. $0.01 per span checked on the hosted surface.
replay
replay_span
Fork-replay ONE recorded span from a failed agent run and return an attribution verdict (determinism vs tool drift vs env drift vs world-state vs model decision), without re-running the whole run.

Endpoints

URLTransportStateLatencyChecked
https://textforagents.com/products/span-level-replay-fork-from-failure/mcp streamable-http answering 319 ms 5 min ago

Alternatives to Span-level replay: fork from the failure

same job, measured the same way
Orcareplay
by continuum-ai-corp

Read, replay and fork recorded coding-agent runs.

67 installs/wk local only
Agent Replay
by mdfifty50-boop

Record and replay AI agent execution for debugging

16 installs/wk local only
Kira
by aibenyclaude-coder

Skills and Scars for AI agents - your agent records its failures and never repeats them.

30 installs/wk local only
Postcept
by postcept

Verify agent actions against the system of record and get signed completion receipts.

18 installs/wk local only
RECOVER — Decide Safely After a Failed Machine Action
by gsterlingpress

Choose the safest next action after an API, MCP, or agent failure before retrying.

1 tools answering
handoff — agent swarm coordination
by 34r7h

Agent swarm coordination: find funded work, form teams, run tasks, message E2E, get paid on verify.

169 tools answering
MintwareDevelopers
by mintwaredevelopers

Look up on-chain Attribution reputation scores for wallets and AI agents on Base.

9 installs/wk local only
Rssa
by getvda

Read and verify signed RSS-A agent feeds; post, reply and react on the RSS-A Agent Network board.

10 tools answering

Span-level replay: fork from the failure — questions

Answers built from our own checks of this server.

What can Span-level replay: fork from the failure do?
It exposes 2 tools, read directly from the server on our last check. Among them: fork_safety_check, replay_span. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Span-level replay: fork from the failure working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 320 ms. The bar chart above shows every period we have measured.
How do I connect Span-level replay: fork from the failure?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Span-level replay: fork from the failure need an API key?
No. Span-level replay: fork from the failure completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Span-level replay: fork from the failure?
It answers our handshake in 320 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.