# Futility Breaker (remote · textforagents.com)

Evidence-bound stopping for agents: judgment ledger, binding futility verdicts, signed receipts.

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

## Components

- remote · `textforagents.com`: 58/100 (this document), [markdown](https://verifymcp.io/servers/com-textforagents-futility-breaker-evidence-bound-stopping/products-futility-breaker-evidence-bound-stopping-mcp.md), [page](https://verifymcp.io/servers/com-textforagents-futility-breaker-evidence-bound-stopping/products-futility-breaker-evidence-bound-stopping-mcp)

## Channel facts

- Endpoint: `https://textforagents.com/products/futility-breaker-evidence-bound-stopping/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 6 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**: 56/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 353 tokens (~58/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Futility Breaker MCP server?

Futility Breaker is a hosted endpoint at https://textforagents.com/products/futility-breaker-evidence-bound-stopping/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-futility-breaker-evidence-boun 'https://textforagents.com/products/futility-breaker-evidence-bound-stopping/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-textforagents-futility-breaker-evidence-boun": {
      "url": "https://textforagents.com/products/futility-breaker-evidence-bound-stopping/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-textforagents-futility-breaker-evidence-boun": {
      "type": "http",
      "url": "https://textforagents.com/products/futility-breaker-evidence-bound-stopping/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-textforagents-futility-breaker-evidence-boun]
url = "https://textforagents.com/products/futility-breaker-evidence-bound-stopping/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-textforagents-futility-breaker-evidence-boun": {
      "type": "remote",
      "url": "https://textforagents.com/products/futility-breaker-evidence-bound-stopping/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-textforagents-futility-breaker-evidence-boun --url 'https://textforagents.com/products/futility-breaker-evidence-bound-stopping/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-textforagents-futility-breaker-evidence-boun:
    url: "https://textforagents.com/products/futility-breaker-evidence-bound-stopping/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-textforagents-futility-breaker-evidence-boun": {
      "Transport": "http",
      "Url": "https://textforagents.com/products/futility-breaker-evidence-bound-stopping/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-textforagents-futility-breaker-evidence-boun -t streamable-http -u 'https://textforagents.com/products/futility-breaker-evidence-bound-stopping/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-textforagents-futility-breaker-evidence-boun": {
      "type": "http",
      "url": "https://textforagents.com/products/futility-breaker-evidence-bound-stopping/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 58, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 57)

First indexed and scored.

## MCP tools (6)

### `futility_register_run` (~55 tokens)

Register a run with its alternatives and operator-registered source identities (strings or {id, aliases}) before judging.

Input parameters:

- `alternatives` (array)
- `run_id` (string, required)
- `sources` (array)

### `futility_judge` (~115 tokens)

Record one usefulness judgment (useful / useless / partial) for a run/source/domain and return the binding verdict (CONTINUE / STOP-SOURCE / INTEGRATE-NOW / ABSTAIN). Billed as a verdict call: one-time trial, tier allowance, or x402 $0.002.

Input parameters:

- `domain` (string)
- `label` (string, required)
- `query` (string)
- `run_id` (string, required)
- `source` (string, required)
- `tokens` (integer)

### `futility_verdict` (~46 tokens)

Read the current verdict for a run/source/domain without recording a judgment.

Input parameters:

- `domain` (string)
- `run_id` (string, required)
- `source` (string, required)

### `futility_waste_report` (~39 tokens)

Waste report for a run: tokens spent after the verdict point, per source and per domain aggregate.

Input parameters:

- `run_id` (string, required)

### `futility_receipt` (~52 tokens)

Mint the HMAC-signed abstention receipt when the run/source/domain verdict is ABSTAIN.

Input parameters:

- `domain` (string)
- `run_id` (string, required)
- `source` (string, required)

### `futility_verify_receipt` (~46 tokens)

Verify a receipt payload {receipt, signature}; total rejection with a reason on malformed/forged input.

Input parameters:

- `receipt` (object, required)
- `signature` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-textforagents-futility-breaker-evidence-bound-stopping/products-futility-breaker-evidence-bound-stopping-mcp#diagnostics

## Score history

- 2026-10-23: 58
- 2026-10-22: 57

## Common questions

### What is the Futility Breaker MCP server?

Futility Breaker is an MCP server listed in the public MCP registry as com.textforagents/futility-breaker-evidence-bound-stopping. Evidence-bound stopping for agents: judgment ledger, binding futility verdicts, signed receipts. This page covers its hosted endpoint (https://textforagents.com/products/futility-breaker-evidence-bound-stopping/mcp).

### Is the Futility Breaker MCP server safe to use?

Futility Breaker scores 58 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 Futility Breaker MCP server expose?

Futility Breaker exposes 6 tools: futility_register_run, futility_judge, futility_verdict, futility_waste_report, futility_receipt, futility_verify_receipt. Their descriptions and schemas cost roughly 353 tokens of context every time the server is loaded.

### Does the Futility Breaker MCP server require authentication?

No. We connected to Futility Breaker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Futility Breaker MCP server still maintained?

Futility Breaker 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/futility-breaker-evidence-bound-stopping/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-textforagents-futility-breaker-evidence-bound-stopping/products-futility-breaker-evidence-bound-stopping-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-textforagents-futility-breaker-evidence-bound-stopping/products-futility-breaker-evidence-bound-stopping-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-textforagents-futility-breaker-evidence-bound-stopping/products-futility-breaker-evidence-bound-stopping-mcp