MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

Span-level replay: fork from the failure

By textforagents.com Verified namespace

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

WebsiteAI models & agents
Connect to Span-level replay: fork from the failure
Checks passed
10 / 22

4 failed · 8 not measured

Median response
341 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
2

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
410
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
220
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 341 ms.

  • Pass
    Valid handshake

    protocolVersion 2024-11-05, serverInfo.name span-level-replay-fork-from-failure.

  • Pass
    Lists tools

    tools/list returned 2 tools.

  • Fail
    Current protocol

    Negotiated 2024-11-05. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 341 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 341 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    4 of 6 parameters have a description (67%). The bar is 80%.

  • Fail
    Safety hints

    2 tools set neither readOnlyHint nor destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-10-20T01:57:40.771016Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using Span-level replay: fork from the failure

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http span-level-replay-fork-from-the-failure https://textforagents.com/products/span-level-replay-fork-from-failure/mcp

Capabilities

Tools 2

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.

Discovered
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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected341 ms2

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Explore alternatives to Span-level replay: fork from the failure