GAIP Integration Repair Agent
REMOTE · WWW.GAIPAGENTS.COM
Now part of GAIP Diagnose: diagnoses failed agent or API calls (gaip_diagnose).
Available components
Last scanned (15 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Monitoring and Observability
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 853 tokens (~142/item across 6 items; 2 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 10 Nov 26 +1
- Stability: 0.97 → pass security
- 9 Nov 26 −1
- Stability: pass → 0.97 functional
- 8 Nov 26 +1
- Stability: 0.97 → pass security
- 7 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- “gaip_diagnose_integration_failure” reworded the description of “failure” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
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://www.gaipagents.com/mcp/agents/integration-repair
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.gaipagents.com | CN=YR1,O=Let's Encrypt,C=US | 20 Nov 2026 | 18 Feb 2027 | RSA 2048 | SHA256-RSA | 629394bb10f8e4e1d662f4be4ac796c3b6f |
| SANs: *.gaipagents.com, gaipagents.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.gaipagents.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| gaipagents.com. | 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 |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.gaipagents.com/mcp/agents/integration-repair | Verified | 200 | |
| http (plaintext) | http://www.gaipagents.com/mcp/agents/integration-repair | HTTPS enforced | 308 | https://www.gaipagents.com/mcp/agents/integration-repair |
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 →
gaip_diagnose_integration_failure Why did my agent call fail? ~309
Use this when an agent, MCP or API call failed ("why did my call fail?", "what does this 429 mean?"). Pass the `failure` ({code, detail}) or the raw error text. Returns the likely cause, when and how to retry, fix steps and a receipt. GAIP touches no other system. Free, no account; records a GAIP receipt only. Inputs must be public and non-personal.
| Name | Type | Req | Description |
|---|---|---|---|
| continuity_handle | object | – | Optional: the continuity_handle from an earlier GAIP result; links this call to your earlier ones. |
| counterparty_id | string | – | Name or URL of the agent/service. Optional. |
| data_classification | string | – | PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data. |
| episode_id | string | – | Optional: your own id to group related calls. |
| failure | object | yes | The failure: {code, detail?, http_status?}, e.g. {"code": 429, "detail": "Too Many Requests; Retry-After: 20"}. |
| independent_operator_id | string | – | Optional: your operator id (recorded as a claim, not verified). |
| protocol | string | – | Counterparty protocol. Inferred from metadata when omitted, otherwise MCP. |
| synthetic | boolean | – | Optional: true marks a test call. |
| task_class | string | – | Optional: short name of the task, e.g. weather_forecast. |
No output schema declared.
{"counterparty_id":"example-weather-agent","failure":{"code":429,"detail":"HTTP 429 Too Many Requests; Retry-After: 20"}} gaip_supplier_reliability Why is my supplier failing? ~313
Use this when a supplier agent or API you depend on started failing ("did something change on their side?"). Pass its `supplier_url` and the `failure`. Returns the diagnosis plus changes GAIP observed around then (correlated in time, not causation), with receipts. Free, read-only, no account; inputs must be public and non-personal.
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | – | Optional supplier card / server description you integrated against. |
| counterparty_id | string | – | Optional: name of the supplier. |
| data_classification | string | – | PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data. |
| failure | object | – | {code, detail?, http_status?} as for gaip_diagnose_integration_failure. |
| failure_started_at | string | – | Optional: RFC 3339 time the failures started. |
| failures | array | – | Optional: several failures, each {code, detail}. |
| lookback_days | integer | – | Optional: days of GAIP observations to look back over. |
| protocol | string | – | Omit to infer it from card, transport or the supplier URL path (else UNKNOWN). |
| supplier_url | string | yes | Public https URL of the supplier's agent card, MCP server or API. |
| task_class | string | – | Optional: short name of the task, e.g. weather_forecast. |
| transport | string | – | Optional transport you used (e.g. streamable-http, sse, GRPC). |
No output schema declared.
{"failure":{"code":404,"detail":"Not Found"},"failure_started_at":"2026-09-27T12:00:00Z","supplier_url":"https://weather.example.com/.well-known/agent-card.json"} How do I install the GAIP Integration Repair Agent MCP server?
GAIP Integration Repair Agent is a hosted endpoint at https://www.gaipagents.com/mcp/agents/integration-repair, 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 · www.gaipagents.com
claude mcp add --transport http tjcgraham-rgb-gaip-integration-repair 'https://www.gaipagents.com/mcp/agents/integration-repair'
What is the GAIP Integration Repair Agent MCP server?
GAIP Integration Repair Agent is an MCP server listed in the public MCP registry as io.github.tjcgraham-rgb/gaip-integration-repair. Now part of GAIP Diagnose: diagnoses failed agent or API calls (gaip_diagnose). This page covers its hosted endpoint (https://www.gaipagents.com/mcp/agents/integration-repair).
Is the GAIP Integration Repair Agent MCP server safe to use?
GAIP Integration Repair Agent scores 90 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 GAIP Integration Repair Agent MCP server expose?
GAIP Integration Repair Agent exposes 2 tools: gaip_diagnose_integration_failure, gaip_supplier_reliability. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.
Does the GAIP Integration Repair Agent MCP server require authentication?
No. We connected to GAIP Integration Repair Agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GAIP Integration Repair Agent MCP server still maintained?
GAIP Integration Repair Agent 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 GAIP Integration Repair Agent MCP server?
VerifyMCP ran 13 checks on GAIP Integration Repair Agent, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.