# Agent Repair — MCP Tool Failure Diagnostics (remote · agent-repair.saromy-export.workers.dev)

Free MCP tool error diagnosis, argument checks, and related agent-tool discovery.

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

## Components

- remote · `agent-repair.saromy-export.workers.dev`: 58/100 (this document), [markdown](https://verifymcp.io/servers/neat-cyber-agent-repair/agent-repair.md), [page](https://verifymcp.io/servers/neat-cyber-agent-repair/agent-repair)

## Channel facts

- Endpoint: `https://agent-repair.saromy-export.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-21.

- **Endpoint Security**: 46/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 3 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 241 tokens (~80/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Agent Repair — MCP Tool Failure Diagnostics server?

Agent Repair — MCP Tool Failure Diagnostics is a hosted endpoint at https://agent-repair.saromy-export.workers.dev/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 neat-cyber-agent-repair 'https://agent-repair.saromy-export.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "neat-cyber-agent-repair": {
      "url": "https://agent-repair.saromy-export.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "neat-cyber-agent-repair": {
      "type": "http",
      "url": "https://agent-repair.saromy-export.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.neat-cyber-agent-repair]
url = "https://agent-repair.saromy-export.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "neat-cyber-agent-repair": {
      "type": "remote",
      "url": "https://agent-repair.saromy-export.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add neat-cyber-agent-repair --url 'https://agent-repair.saromy-export.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  neat-cyber-agent-repair:
    url: "https://agent-repair.saromy-export.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "neat-cyber-agent-repair": {
      "Transport": "http",
      "Url": "https://agent-repair.saromy-export.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add neat-cyber-agent-repair -t streamable-http -u 'https://agent-repair.saromy-export.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "neat-cyber-agent-repair": {
      "type": "http",
      "url": "https://agent-repair.saromy-export.workers.dev/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-20 (score 58, +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-11-18 (score 57, +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-11-16 (score 56, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 55)

First indexed and scored.

## MCP tools (3)

### `diagnose_tool_failure` (~107 tokens)

Classify a failed MCP/API tool call and recommend bounded next actions. Offline deterministic analysis. Does NOT retry, contact a service, or store the supplied error text.

Input parameters:

- `error_message` (string): Error or exception text; remove secrets before sharing.
- `http_status` (integer)
- `idempotent` (boolean): True ONLY when the tool call is safe to repeat without side effects.
- `jsonrpc_code` (integer)
- `retry_after_seconds` (integer)

### `validate_tool_arguments` (~92 tokens)

Check supplied tool arguments against a constrained subset of JSON Schema (type, required, properties, additionalProperties, enum, const, numeric/string bounds, arrays). Returns paths and errors, no network access or storage. NOT full JSON Schema validation.

Input parameters:

- `arguments` (object, required): Tool call arguments. Remove credentials; no raw payload is logged.
- `schema` (object, required): MCP tool inputSchema. Limited JSON Schema subset.

### `ecosystem_catalog` (~42 tokens)

Discover useful independent agent-native tools from this same project and their MCP connection URLs. No request to another service, referrals only when relevant.

Input parameters:

- `need` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/neat-cyber-agent-repair/agent-repair#diagnostics

## Score history

- 2026-11-21: 58
- 2026-11-20: 58
- 2026-11-19: 57
- 2026-11-18: 57
- 2026-11-17: 56
- 2026-11-16: 56
- 2026-11-15: 55

## Common questions

### What is the Agent Repair — MCP Tool Failure Diagnostics server?

Agent Repair — MCP Tool Failure Diagnostics is listed in the public MCP registry as io.github.neat-cyber/agent-repair. Free MCP tool error diagnosis, argument checks, and related agent-tool discovery. This page covers its hosted endpoint (https://agent-repair.saromy-export.workers.dev/mcp).

### Is the Agent Repair — MCP Tool Failure Diagnostics server safe to use?

Agent Repair — MCP Tool Failure Diagnostics 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 Agent Repair — MCP Tool Failure Diagnostics server expose?

Agent Repair — MCP Tool Failure Diagnostics exposes 3 tools: diagnose_tool_failure, validate_tool_arguments, ecosystem_catalog. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.

### Does the Agent Repair — MCP Tool Failure Diagnostics server require authentication?

No. We connected to Agent Repair — MCP Tool Failure Diagnostics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Agent Repair — MCP Tool Failure Diagnostics server still maintained?

Agent Repair — MCP Tool Failure Diagnostics is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Agent Repair — MCP Tool Failure Diagnostics server?

VerifyMCP ran 11 checks on Agent Repair — MCP Tool Failure Diagnostics, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Agent Repair — MCP Tool Failure Diagnostics: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://agent-repair.saromy-export.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/neat-cyber-agent-repair/agent-repair.xml
- Changelog JSON feed: https://verifymcp.io/servers/neat-cyber-agent-repair/agent-repair/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/neat-cyber-agent-repair/agent-repair.json
- HTML version of this page: https://verifymcp.io/servers/neat-cyber-agent-repair/agent-repair
