GAIP Integration Repair Agent
REMOTE · WWW.GAIPAGENTS.COM · SCANNED SEP 28
Supplier Reliability: diagnoses failed agent or API calls and returns a bounded repair plan.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 571 tokens (~285/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% 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 2 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
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'
{
"mcpServers": {
"tjcgraham-rgb-gaip-integration-repair": {
"url": "https://www.gaipagents.com/mcp/agents/integration-repair"
}
}
} {
"servers": {
"tjcgraham-rgb-gaip-integration-repair": {
"type": "http",
"url": "https://www.gaipagents.com/mcp/agents/integration-repair"
}
}
} [mcp_servers.tjcgraham-rgb-gaip-integration-repair] url = "https://www.gaipagents.com/mcp/agents/integration-repair"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tjcgraham-rgb-gaip-integration-repair": {
"type": "remote",
"url": "https://www.gaipagents.com/mcp/agents/integration-repair",
"enabled": true
}
}
} openclaw mcp add tjcgraham-rgb-gaip-integration-repair --url 'https://www.gaipagents.com/mcp/agents/integration-repair' --transport streamable-http
mcp_servers:
tjcgraham-rgb-gaip-integration-repair:
url: "https://www.gaipagents.com/mcp/agents/integration-repair" {
"McpServers": {
"tjcgraham-rgb-gaip-integration-repair": {
"Transport": "http",
"Url": "https://www.gaipagents.com/mcp/agents/integration-repair"
}
}
} assistant mcp add tjcgraham-rgb-gaip-integration-repair -t streamable-http -u 'https://www.gaipagents.com/mcp/agents/integration-repair'
{
"mcpServers": {
"tjcgraham-rgb-gaip-integration-repair": {
"type": "http",
"url": "https://www.gaipagents.com/mcp/agents/integration-repair"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 17% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fail → pass ▲ functional
- Schema quality: fair → good functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “gaip_supplier_reliability” functional
- 27 Sept 26 67
First indexed and scored.
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 28 Sept 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=YR2,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | RSA 2048 | SHA256-RSA | 6a0d0472cd704c560e84fb22d65b86934fc |
| SANs: *.gaipagents.com, gaipagents.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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. | present | 19718 | 13 | Verified |
| gaipagents.com. | absent | 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 Diagnose integration failure ~243
An agent-to-agent call failed? Pass the `failure` ({code, detail}): an HTTP status (400-504), a JSON-RPC, A2A or MCP error code, or the raw error text (TLS, DNS, connection refused, timeout, schema mismatch). Returns a specific diagnosis, severity, whether and how to retry (attempts, backoff, Retry-After), ordered fix steps, the likely owner, evidence to capture and a receipt. Proposal only; GAIP does not touch the other system. Free, read-only, no account. Inputs must be public and non-personal; calling declares that (data_classification defaults to PUBLIC).
| Name | Type | Req | Description |
|---|---|---|---|
| continuity_handle | object | – | – |
| counterparty_id | string | – | Name or URL of the agent/service. Optional. |
| data_classification | string | – | – |
| episode_id | string | – | – |
| failure | object | yes | – |
| independent_operator_id | string | – | – |
| protocol | string | – | Counterparty protocol. Inferred from metadata when omitted, otherwise MCP. |
| synthetic | boolean | – | – |
| task_class | string | – | – |
No output schema declared.
{"counterparty_id":"example-weather-agent","failure":{"code":429,"detail":"HTTP 429 Too Many Requests; Retry-After: 20"}}gaip_supplier_reliability Diagnose a supplier failure with recent changes ~208
A supplier agent or API started failing? Pass the `failure` ({code, detail}), the supplier's public `supplier_url` and optionally `failure_started_at`. Returns the Integration Repair diagnosis plus the supplier card and readiness changes GAIP observed around that time, each with a receipt and labelled correlated in time (not causation), next steps and an offer to watch the supplier. Free, read-only, no account. Inputs must be public and non-personal; calling declares that (data_classification defaults to PUBLIC).
| Name | Type | Req | Description |
|---|---|---|---|
| counterparty_id | string | – | – |
| data_classification | string | – | – |
| failure | object | – | {code, detail?, http_status?} as for gaip_diagnose_integration_failure. |
| failure_started_at | string | – | – |
| failures | array | – | – |
| lookback_days | integer | – | – |
| protocol | string | – | – |
| supplier_url | string | yes | – |
| task_class | string | – | – |
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"}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. Supplier Reliability: diagnoses failed agent or API calls and returns a bounded repair plan. 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 69 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 451 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 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.