# Span-level replay: fork from the failure (remote · textforagents.com)

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

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `textforagents.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-textforagents-span-level-replay-fork-from-failure/products-span-level-replay-fork-from-failure-mcp.md), [page](https://verifymcp.io/servers/com-textforagents-span-level-replay-fork-from-failure/products-span-level-replay-fork-from-failure-mcp)

## Channel facts

- Endpoint: `https://textforagents.com/products/span-level-replay-fork-from-failure/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 222 tokens (~111/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the Span-level replay: fork from the failure MCP server?

Span-level replay: fork from the failure is a hosted endpoint at https://textforagents.com/products/span-level-replay-fork-from-failure/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-textforagents-span-level-replay-fork-from-fa 'https://textforagents.com/products/span-level-replay-fork-from-failure/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-textforagents-span-level-replay-fork-from-fa": {
      "url": "https://textforagents.com/products/span-level-replay-fork-from-failure/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-textforagents-span-level-replay-fork-from-fa": {
      "type": "http",
      "url": "https://textforagents.com/products/span-level-replay-fork-from-failure/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-textforagents-span-level-replay-fork-from-fa]
url = "https://textforagents.com/products/span-level-replay-fork-from-failure/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-textforagents-span-level-replay-fork-from-fa": {
      "type": "remote",
      "url": "https://textforagents.com/products/span-level-replay-fork-from-failure/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-textforagents-span-level-replay-fork-from-fa --url 'https://textforagents.com/products/span-level-replay-fork-from-failure/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-textforagents-span-level-replay-fork-from-fa:
    url: "https://textforagents.com/products/span-level-replay-fork-from-failure/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-textforagents-span-level-replay-fork-from-fa": {
      "Transport": "http",
      "Url": "https://textforagents.com/products/span-level-replay-fork-from-failure/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-textforagents-span-level-replay-fork-from-fa -t streamable-http -u 'https://textforagents.com/products/span-level-replay-fork-from-failure/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-textforagents-span-level-replay-fork-from-fa": {
      "type": "http",
      "url": "https://textforagents.com/products/span-level-replay-fork-from-failure/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 62, +1)

- [functional regression] Schema quality: 88 → 111
- [functional] New tool “fork_safety_check”

### 2026-10-21 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-20 (score 61)

First indexed and scored.

## MCP tools (2)

### `replay_span` (~88 tokens)

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.

Input parameters:

- `span` (object): One normalized span record.
- `span_id` (string)
- `spans` (array): A recorded run's span records; span_id selects the one to fork.

### `fork_safety_check` (~134 tokens)

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.

Input parameters:

- `span` (object): One normalized span record.
- `span_id` (string)
- `spans` (array): A recorded run's span records; without span_id every span is checked.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-textforagents-span-level-replay-fork-from-failure/products-span-level-replay-fork-from-failure-mcp#diagnostics

## Score history

- 2026-10-23: 63
- 2026-10-22: 62
- 2026-10-21: 61
- 2026-10-20: 61

## Common questions

### What is the Span-level replay: fork from the failure MCP server?

Span-level replay: fork from the failure is an MCP server listed in the public MCP registry as com.textforagents/span-level-replay-fork-from-failure. Fork-replay one recorded span from a failed agent run and get an attribution verdict. This page covers its hosted endpoint (https://textforagents.com/products/span-level-replay-fork-from-failure/mcp).

### Is the Span-level replay: fork from the failure MCP server safe to use?

Span-level replay: fork from the failure scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Span-level replay: fork from the failure MCP server expose?

Span-level replay: fork from the failure exposes 2 tools: replay_span, fork_safety_check. Their descriptions and schemas cost roughly 222 tokens of context every time the server is loaded.

### Does the Span-level replay: fork from the failure MCP server require authentication?

No. We connected to Span-level replay: fork from the failure without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Span-level replay: fork from the failure MCP server still maintained?

Span-level replay: fork from the failure is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://textforagents.com/products/span-level-replay-fork-from-failure/mcp
- Website: https://textforagents.com/products/span-level-replay-fork-from-failure/
- Changelog RSS feed: https://verifymcp.io/servers/com-textforagents-span-level-replay-fork-from-failure/products-span-level-replay-fork-from-failure-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-textforagents-span-level-replay-fork-from-failure/products-span-level-replay-fork-from-failure-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-textforagents-span-level-replay-fork-from-failure/products-span-level-replay-fork-from-failure-mcp