Skip to content

Agent Repair — MCP Tool Failure Diagnostics

io.github.neat-cyber/agent-repairneat-cyberstreamable-httpv0.2.0Scanned

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

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Agent Repair — MCP Tool Failure Diagnostics can do

The Agent Repair — MCP Tool Failure Diagnostics is published by the GitHub account neat-cyber. It has 3 tools. It can create or change data (2 tools: diagnose_tool_failure and ecosystem_catalog), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • diagnose_tool_failureClassify a failed MCP/API tool call and recommend bounded next actions.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • ecosystem_catalogDiscover useful independent agent-native tools from this same project and their MCP connection URLs.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Discover useful independent agent-native tools from this same project and their MCP connection URLs. No request to another service, referrals only when relevant.
Only reads 1Show 1 read-only tool
  • validate_tool_argumentsCheck supplied tool arguments against a constrained subset of JSON Schema (type, required, properties, additionalProperties, enum, const, numeric/string bounds, arrays).1 finding

    Why it is in this group

    • The name "validate_tool_arguments" says "validate": a word for reading.

    Findings

    • Info

      The input schema at properties.arguments.description mentions "credentials".

      Matched text

      inputSchema.properties.arguments.description: "Tool call arguments. Remove credentials; no raw payload is logged."

      What this check looks for
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:23 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://agent-repair.saromy-export.workers.dev/mcp: tools/list returned 3 tools to an anonymous client, including diagnose_tool_failure (write), ecosystem_catalog (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The input schema at properties.arguments.description mentions "credentials".

    Matched text

    inputSchema.properties.arguments.description: "Tool call arguments. Remove credentials; no raw payload is logged."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-repair https://agent-repair.saromy-export.workers.dev/mcp
claude mcp add --transport http agent-repair https://agent-repair.saromy-export.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agent-repair__validate_tool_arguments"
    ],
    "ask": [
      "mcp__agent-repair__diagnose_tool_failure",
      "mcp__agent-repair__ecosystem_catalog"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-repair. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.neat-cyber/agent-repair/verify?hash=bc9e25e2ca50527b5d3c040313cc26cd8f2b5f446b8259f26fbbdc57085c1c3b" | jq -e '.changed == false'

Pinned hash bc9e25e2ca50, from Nov 15, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.neat-cyber/agent-repair/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.neat-cyber/agent-repair
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.neat-cyber/agent-repair.svg)](https://radar.anlyon.com/servers/io.github.neat-cyber/agent-repair)

Source: MCP Registry. Synced Nov 15, 2026, 13:17 UTC.

Agent Repair — MCP Tool Failure Diagnostics: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Agent Repair — MCP Tool Failure Diagnostics safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Agent Repair — MCP Tool Failure Diagnostics delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Agent Repair — MCP Tool Failure Diagnostics do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Agent Repair — MCP Tool Failure Diagnostics have?

3 tools: 2 write, 1 read. diagnose_tool_failure, ecosystem_catalog and validate_tool_arguments.

Does the Agent Repair — MCP Tool Failure Diagnostics need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Agent Repair — MCP Tool Failure Diagnostics send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Agent Repair — MCP Tool Failure Diagnostics changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.