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.

GAIP Integration & Protocol Agent

REMOTE · WWW.GAIPAGENTS.COM · SCANNED SEP 28

Agent Observatory: checks A2A, MCP and OpenAPI declarations and logs published changes.

63 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1350 tokens (~192/item across 7 items; 7 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 Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 38% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 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
Install

How do I install the GAIP Integration & Protocol Agent MCP server?

GAIP Integration & Protocol Agent is a hosted endpoint at https://www.gaipagents.com/mcp/agents/integration-protocol, 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

# add to Claude Code
claude mcp add --transport http tjcgraham-rgb-gaip-integration-protocol 'https://www.gaipagents.com/mcp/agents/integration-protocol'
// .cursor/mcp.json
{
  "mcpServers": {
    "tjcgraham-rgb-gaip-integration-protocol": {
      "url": "https://www.gaipagents.com/mcp/agents/integration-protocol"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "tjcgraham-rgb-gaip-integration-protocol": {
      "type": "http",
      "url": "https://www.gaipagents.com/mcp/agents/integration-protocol"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.tjcgraham-rgb-gaip-integration-protocol]
url = "https://www.gaipagents.com/mcp/agents/integration-protocol"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tjcgraham-rgb-gaip-integration-protocol": {
      "type": "remote",
      "url": "https://www.gaipagents.com/mcp/agents/integration-protocol",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tjcgraham-rgb-gaip-integration-protocol --url 'https://www.gaipagents.com/mcp/agents/integration-protocol' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  tjcgraham-rgb-gaip-integration-protocol:
    url: "https://www.gaipagents.com/mcp/agents/integration-protocol"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "tjcgraham-rgb-gaip-integration-protocol": {
      "Transport": "http",
      "Url": "https://www.gaipagents.com/mcp/agents/integration-protocol"
    }
  }
}
# add to Vellum
assistant mcp add tjcgraham-rgb-gaip-integration-protocol -t streamable-http -u 'https://www.gaipagents.com/mcp/agents/integration-protocol'
// mcp.json
{
  "mcpServers": {
    "tjcgraham-rgb-gaip-integration-protocol": {
      "type": "http",
      "url": "https://www.gaipagents.com/mcp/agents/integration-protocol"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 Sept 26 −4
    • Authorization: partial → unverified ▼ security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 0% → 38% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: fail → pass ▲ functional
    • Schema quality: fair → good functional
    • Destructive annotations: pass → 100 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
  • 27 Sept 26 67

    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 28 Sept 2026 · Probed https://www.gaipagents.com/mcp/agents/integration-protocol

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-protocol Verified 200
http (plaintext) http://www.gaipagents.com/mcp/agents/integration-protocol HTTPS enforced 308 https://www.gaipagents.com/mcp/agents/integration-protocol
MCP tools · 7 exposed · ~1,210 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
check_agent_conformance ~350

Check any AI agent before you install or call it. Pass just its `url` (site, A2A agent card, MCP server card / server.json or OpenAPI link): GAIP fetches the card, validates it against the A2A, MCP or OpenAPI spec, tests that its endpoint answers and returns READY / FIXES_NEEDED / NO_AGENT_CARD / UNREACHABLE. Or pass the card itself as `metadata`. Every finding has a severity, JSON path, plain-English fix and spec link, plus a 0-100 score and a JSON Patch with placeholders; the receipt verifies with verify_gaip_receipt. Set mode=VERIFY_BEFORE_CALL with `target` to get task-specific evidence about a counterparty instead. Free, read-only, no account. Inputs must be public and non-personal; calling declares that (data_classification defaults to PUBLIC).

NameTypeReqDescription
data_classificationstring––
declared_identitystring––
expected_endpointstring–Optional: the endpoint you expect; a different primary endpoint is reported as ENDPOINT_DRIFT.
intended_taskstring––
metadataobject––
modestring––
protocolstring–Counterparty protocol. Inferred from metadata when omitted, otherwise MCP.
source_urlstring–Optional: where `metadata` was published, used only to resolve relative endpoints. Never fetched.
target–––
urlstring–Public https link to an agent, its A2A agent card, MCP server description or OpenAPI document. GAIP fetches, validates and reach-tests it. Use instead of metadata.

No output schema declared.

{"metadata":{"name":"GAIP Broker","protocolVersion":"2025-06-18","tools":[],"url":"https://www.gaipagents.com/mcp"}}
gaip_manifest_changes ~110

Read the Agent Observatory's hash-chained Manifest Transparency Log: which published manifests changed, before/after hashes, neutral change facts and receipts. Optional `target_id`, `since` (RFC 3339), `limit` (max 100). Free, read-only, no account. Inputs must be public and non-personal; calling declares that (data_classification defaults to PUBLIC).

NameTypeReqDescription
limitinteger––
sincestring––
target_idstring––

No output schema declared.

{"limit":20,"since":"2026-09-01T00:00:00Z"}
gaip_observatory_lookup ~149

What has an MCP server or A2A agent published over time? Pass a `url` or `name` to find its Observatory target_id, or a `target_id` for its dated facts: status history, manifest hash and bounded snapshot, conformance codes, metadata-signal rules (pattern present / not present) and the receipted change log. Facts observed at a time; not an assessment of safety or quality. Free, read-only, no account. Inputs must be public and non-personal; calling declares that (data_classification defaults to PUBLIC).

NameTypeReqDescription
namestring––
target_idstring––
urlstring––

No output schema declared.

{"url":"https://weather.example.com/mcp"}
gaip_watch_events ~113

Read recent change events for your watches (all, or one `watch_id`): verdict before and after, a compact change summary, the event receipt and whether the webhook delivery succeeded. Free, read-only, no account. Inputs must be public and non-personal; calling declares that (data_classification defaults to PUBLIC).

NameTypeReqDescription
continuity_handleobjectyesThe continuity_handle from an earlier GAIP result; proves you own these watches.
limitinteger––
watch_idstring––

No output schema declared.

{"continuity_handle":{"continuity_id":"\u003ccontinuity_handle.continuity_id returned by any GAIP tool\u003e","token":"\u003ccontinuity_handle.token returned by any GAIP tool\u003e"},"limit":10,"watch_id":"\u003cwatch_id from gaip_watch_register\u003e"}
gaip_watch_list ~92

See your watches: kind, target, last verdict, last and next check, and webhook endpoint (never the secret). Pass your `continuity_handle`. Free, read-only, no account. Inputs must be public and non-personal; calling declares that (data_classification defaults to PUBLIC).

NameTypeReqDescription
continuity_handleobjectyesThe continuity_handle from an earlier GAIP result; proves you own these watches.

No output schema declared.

{"continuity_handle":{"continuity_id":"\u003ccontinuity_handle.continuity_id returned by any GAIP tool\u003e","token":"\u003ccontinuity_handle.token returned by any GAIP tool\u003e"}}
gaip_watch_register ~298

Keep watching an agent you depend on, for free. kind=AGENT_READINESS re-checks an agent URL's readiness, SUPPLIER_CARD re-fetches its published card and flags BREAKING / NON_BREAKING changes, DELIVERY_TERMS replays witness terms (terms_id from witness_register_terms) and flags NOT_MET. Pass the `continuity_handle` an earlier GAIP result gave you (it proves the watches are yours) and optionally your own public https `webhook_url`: changes are POSTed there signed with X-GAIP-Signature (HMAC-SHA256; the `webhook_secret` is shown once). FREE: 3 watches, each checked at most every 24 hours; every change gets a receipt. Free, read-only, no account. Inputs must be public and non-personal; calling declares that (data_classification defaults to PUBLIC).

NameTypeReqDescription
continuity_handleobjectyesThe continuity_handle from an earlier GAIP result; proves you own these watches.
data_classificationstring––
interval_hoursinteger––
kindstringyes–
target_urlstring–Public https URL (AGENT_READINESS, SUPPLIER_CARD). No query string.
terms_idstring–DELIVERY_TERMS: terms_id from witness_register_terms.
webhook_urlstring–Optional: your own public https endpoint for signed change events.

No output schema declared.

{"continuity_handle":{"continuity_id":"\u003ccontinuity_handle.continuity_id returned by any GAIP tool\u003e","token":"\u003ccontinuity_handle.token returned by any GAIP tool\u003e"},"interval_hours":24,"kind":"SUPPLIER_CARD","target_url":"https://weather.example.com/.well-known/agent-card.json","webhook_url":"https://hooks.example.com/gaip-watch"}
gaip_watch_remove ~98

Stop a watch: pass your `continuity_handle` and the `watch_id`. Its stored events are deleted; retained receipts stay verifiable. Free, read-only, no account. Inputs must be public and non-personal; calling declares that (data_classification defaults to PUBLIC).

NameTypeReqDescription
continuity_handleobjectyesThe continuity_handle from an earlier GAIP result; proves you own these watches.
watch_idstringyes–

No output schema declared.

{"continuity_handle":{"continuity_id":"\u003ccontinuity_handle.continuity_id returned by any GAIP tool\u003e","token":"\u003ccontinuity_handle.token returned by any GAIP tool\u003e"},"watch_id":"\u003cwatch_id from gaip_watch_register\u003e"}
Common questions

What is the GAIP Integration & Protocol Agent MCP server?

GAIP Integration & Protocol Agent is an MCP server listed in the public MCP registry as io.github.tjcgraham-rgb/gaip-integration-protocol. Agent Observatory: checks A2A, MCP and OpenAPI declarations and logs published changes. This page covers its hosted endpoint (https://www.gaipagents.com/mcp/agents/integration-protocol).

Is the GAIP Integration & Protocol Agent MCP server safe to use?

GAIP Integration & Protocol Agent scores 63 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 & Protocol Agent MCP server expose?

GAIP Integration & Protocol Agent exposes 7 tools: check_agent_conformance, gaip_watch_register, gaip_watch_list, gaip_watch_remove, gaip_watch_events, and 2 more. Their descriptions and schemas cost roughly 1,210 tokens of context every time the server is loaded.

Does the GAIP Integration & Protocol Agent MCP server require authentication?

No. We connected to GAIP Integration & Protocol Agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the GAIP Integration & Protocol Agent MCP server still maintained?

GAIP Integration & Protocol 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.