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.
Available components
Last scanned (23 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Testing and QA
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 222 tokens (~111/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
- Schema quality: 88 → 111 ▼ functional
- New tool “fork_safety_check” functional
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://textforagents.com/products/span-level-replay-fork-from-failure/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=textforagents.com | CN=YE2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 66d021cf7bcd281266ac6de4cea43642f85 |
| SANs: textforagents.com, www.textforagents.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of textforagents.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| textforagents.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | interest-cohort=(), geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://textforagents.com/products/span-level-replay-fork-from-failure/mcp | Verified | 200 | |
| http (plaintext) | http://textforagents.com/products/span-level-replay-fork-from-failure/mcp | HTTPS enforced | 301 | https://textforagents.com/products/span-level-replay-fork-from-failure/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fork_safety_check ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| span | object | – | One normalized span record. |
| span_id | string | – | – |
| spans | array | – | A recorded run's span records; without span_id every span is checked. |
No output schema declared.
No examples provided.
replay_span ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| span | object | – | One normalized span record. |
| span_id | string | – | – |
| spans | array | – | A recorded run's span records; span_id selects the one to fork. |
No output schema declared.
No examples provided.
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.
remote · textforagents.com
claude mcp add --transport http com-textforagents-span-level-replay-fork-from-fa 'https://textforagents.com/products/span-level-replay-fork-from-failure/mcp'
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 62 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 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.