Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

58 Trust /100

Last scanned (17 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 241 tokens (~80/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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 in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 55

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://agent-repair.saromy-export.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=saromy-export.workers.dev CN=YE2,O=Let's Encrypt,C=US 15 Nov 2026 13 Feb 2027 ECDSA 256 ECDSA-SHA384 65bc2d5be536c194c5eeb3b2dedd576b5b0
SANs: *.saromy-export.workers.dev, saromy-export.workers.dev
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 agent-repair.saromy-export.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agent-repair.saromy-export.workers.dev/mcp Verified 200
http (plaintext) http://agent-repair.saromy-export.workers.dev/mcp Inconclusive 405
MCP tools · 3 exposed · ~241 tokens

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 →

Tool Tokens
diagnose_tool_failure ~107

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.

NameTypeReqDescription
error_messagestring–Error or exception text; remove secrets before sharing.
http_statusinteger––
idempotentboolean–True ONLY when the tool call is safe to repeat without side effects.
jsonrpc_codeinteger––
retry_after_secondsinteger––

No output schema declared.

No examples provided.

ecosystem_catalog ~42

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

NameTypeReqDescription
needstring––

No output schema declared.

No examples provided.

validate_tool_arguments ~92

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.

NameTypeReqDescription
argumentsobjectyesTool call arguments. Remove credentials; no raw payload is logged.
schemaobjectyesMCP tool inputSchema. Limited JSON Schema subset.

No output schema declared.

No examples provided.

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.

remote · agent-repair.saromy-export.workers.dev

# add to Claude Code
claude mcp add --transport http neat-cyber-agent-repair 'https://agent-repair.saromy-export.workers.dev/mcp'
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.