# Tool-Confusability Recovery Loop (remote · textforagents.com)

Recovery loop for agent tool catalogs: measured confusion, ranked fixes, signed recovery receipts.

- Trust score: 61/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `textforagents.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/com-textforagents-tool-confusability-regression-gate/products-tool-confusability-regression-gate-mcp.md), [page](https://verifymcp.io/servers/com-textforagents-tool-confusability-regression-gate/products-tool-confusability-regression-gate-mcp)

## Channel facts

- Endpoint: `https://textforagents.com/products/tool-confusability-regression-gate/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.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-11-05.

- **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**: 51/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 234 tokens (~39/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 Tool-Confusability Recovery Loop MCP server?

Tool-Confusability Recovery Loop is a hosted endpoint at https://textforagents.com/products/tool-confusability-regression-gate/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-tool-confusability-regression- 'https://textforagents.com/products/tool-confusability-regression-gate/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-textforagents-tool-confusability-regression-": {
      "url": "https://textforagents.com/products/tool-confusability-regression-gate/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-textforagents-tool-confusability-regression-": {
      "type": "http",
      "url": "https://textforagents.com/products/tool-confusability-regression-gate/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-textforagents-tool-confusability-regression-]
url = "https://textforagents.com/products/tool-confusability-regression-gate/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-textforagents-tool-confusability-regression-": {
      "type": "remote",
      "url": "https://textforagents.com/products/tool-confusability-regression-gate/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-textforagents-tool-confusability-regression- --url 'https://textforagents.com/products/tool-confusability-regression-gate/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-textforagents-tool-confusability-regression-:
    url: "https://textforagents.com/products/tool-confusability-regression-gate/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-textforagents-tool-confusability-regression-": {
      "Transport": "http",
      "Url": "https://textforagents.com/products/tool-confusability-regression-gate/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-textforagents-tool-confusability-regression- -t streamable-http -u 'https://textforagents.com/products/tool-confusability-regression-gate/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-textforagents-tool-confusability-regression-": {
      "type": "http",
      "url": "https://textforagents.com/products/tool-confusability-regression-gate/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-11-05 (score 61, +1)

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

### 2026-11-03 (score 60, +1)

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

### 2026-11-01 (score 59, +1)

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

### 2026-10-29 (score 58, +1)

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

### 2026-10-28 (score 57, 0)

- [functional regression] Schema quality: 187 → 234
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “server_author_verdict”

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

First indexed and scored.

## MCP tools (6)

### `register_catalog` (~37 tokens)

Register a tool catalog + probe suite; stores the green state. Free.

Input parameters:

- `catalog` (array, required)
- `probes` (array, required)

### `start_loop` (~52 tokens)

Start a recovery loop run against the current live catalog ($0.05 / plan / first run free).

Input parameters:

- `catalog` (array, required)
- `catalog_id` (string, required)
- `selector_class` (string)

### `apply_fix` (~39 tokens)

Serve the revised catalog for a chosen worklist item of an open loop run.

Input parameters:

- `item` (integer, required)
- `loop_id` (string, required)

### `verify_recovery` (~34 tokens)

Re-probe a loop run whose fix was served and return the signed recovery receipt.

Input parameters:

- `loop_id` (string, required)

### `server_author_verdict` (~47 tokens)

Server-author pre-publish verdict: measure one submitted tool against the curated reference stacks; every verdict names its stack.

Input parameters:

- `stack` (string)
- `tool` (object, required)

### `loop_status` (~25 tokens)

Fetch a loop run's status and receipt.

Input parameters:

- `loop_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-textforagents-tool-confusability-regression-gate/products-tool-confusability-regression-gate-mcp#diagnostics

## Score history

- 2026-11-05: 61
- 2026-11-04: 60
- 2026-11-03: 60
- 2026-11-02: 59
- 2026-11-01: 59
- 2026-10-31: 58
- 2026-10-30: 58
- 2026-10-29: 58
- 2026-10-28: 57
- 2026-10-27: 57

## Common questions

### What is the Tool-Confusability Recovery Loop MCP server?

Tool-Confusability Recovery Loop is an MCP server listed in the public MCP registry as com.textforagents/tool-confusability-regression-gate. Recovery loop for agent tool catalogs: measured confusion, ranked fixes, signed recovery receipts. This page covers its hosted endpoint (https://textforagents.com/products/tool-confusability-regression-gate/mcp).

### Is the Tool-Confusability Recovery Loop MCP server safe to use?

Tool-Confusability Recovery Loop scores 61 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 Tool-Confusability Recovery Loop MCP server expose?

Tool-Confusability Recovery Loop exposes 6 tools: register_catalog, start_loop, apply_fix, verify_recovery, server_author_verdict, loop_status. Their descriptions and schemas cost roughly 234 tokens of context every time the server is loaded.

### Does the Tool-Confusability Recovery Loop MCP server require authentication?

No. We connected to Tool-Confusability Recovery Loop without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Tool-Confusability Recovery Loop MCP server still maintained?

Tool-Confusability Recovery Loop is still listed as active in the MCP registry. We last reached this channel on 5 November 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/tool-confusability-regression-gate/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-textforagents-tool-confusability-regression-gate/products-tool-confusability-regression-gate-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-textforagents-tool-confusability-regression-gate/products-tool-confusability-regression-gate-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-textforagents-tool-confusability-regression-gate/products-tool-confusability-regression-gate-mcp