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 Buyer Assurance Agent

REMOTE · WWW.GAIPAGENTS.COM

Now part of GAIP Witness: records a buyer's request and checks what was delivered.

0 this week 89 Trust /100

Last scanned (13 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Testing and QA

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 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
Schema Quality & AI Usability91
  • 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 881 tokens (~125/item across 7 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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 (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 →

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.

  • 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
  • 1 Nov 26 +51
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
  • 31 Oct 26 −51
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
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://www.gaipagents.com/mcp/agents/buyer-assurance

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/buyer-assurance Verified 200
http (plaintext) http://www.gaipagents.com/mcp/agents/buyer-assurance HTTPS enforced 308 https://www.gaipagents.com/mcp/agents/buyer-assurance
MCP tools · 3 exposed · ~661 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
assurance_complete ~232

Use this when finishing a Buyer Assurance check. Pass the `terms_id` from assurance_prepare and mode PUBLIC_REPLAY (GAIP replays the service) or BUYER_SUBMITTED. Returns PASS / FAIL / UNKNOWN per check and a delivery receipt. Free, no account; records a GAIP receipt only. Inputs must be public and non-personal.

NameTypeReqDescription
bodystring–BUYER_SUBMITTED: the response body you received (max 32 KiB).
body_sha256string–BUYER_SUBMITTED: SHA-256 of the body, instead of the body.
content_typestring–BUYER_SUBMITTED: the Content-Type you received.
data_classificationstring–PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data.
http_statusinteger–BUYER_SUBMITTED: the HTTP status you received.
mode–yesPUBLIC_REPLAY: GAIP fetches the public URL itself. BUYER_SUBMITTED: check a response you pass in.
terms_idstringyesThe terms_id returned when the terms were registered.

No output schema declared.

{"mode":"PUBLIC_REPLAY","terms_id":"\u003cterms_id from assurance_prepare\u003e"}
assurance_prepare ~354

Use this when you, the buyer, chose a public service and want its delivery checked end to end. Pass `service_url`, `checks` and explicit_read_only_consent=true. GAIP preflights it and records your checks; returns a `terms_id` for assurance_complete. Free, no account; records a GAIP receipt only. Inputs must be public and non-personal.

NameTypeReqDescription
checksarrayyes1-8 checks, each {"id": "http_status_in", "allowed": [200]}, {"id": "content_type_is", "value": "application/json"}, {"id": "non_empty"}, {"id": "json_parses"}, {"id": "json_required_keys", "keys": […
counterparty_idstring–Name or URL of the agent or service.
data_classificationstring–PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data.
episode_idstring–Optional: your own id to group related calls.
explicit_read_only_consent–yesMust be true: you consent to a public, read-only check.
service_urlstringyesPublic https URL of the service.
task_classstring–Optional: short name of the task, e.g. weather_forecast.

No output schema declared.

{"checks":[{"allowed":[200],"id":"http_status_in"},{"id":"json_parses"}],"counterparty_id":"example-weather-agent","explicit_read_only_consent":true,"service_url":"https://weather.example.com/forecast.json","task_class":"weather_forecast"}
assurance_verify ~75

Use this when you hold a Buyer Assurance terms or delivery receipt_id and want to confirm it. Returns the retained record and its integrity proof (integrity only). Free, read-only, no account; inputs must be public and non-personal.

NameTypeReqDescription
receipt_idstringyesA receipt_id returned by an earlier GAIP call.

No output schema declared.

{"receipt_id":"\u003creceipt_id from assurance_prepare or assurance_complete\u003e"}
Install

How do I install the GAIP Buyer Assurance Agent MCP server?

GAIP Buyer Assurance Agent is a hosted endpoint at https://www.gaipagents.com/mcp/agents/buyer-assurance, 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-buyer-assurance 'https://www.gaipagents.com/mcp/agents/buyer-assurance'
Common questions

What is the GAIP Buyer Assurance Agent MCP server?

GAIP Buyer Assurance Agent is an MCP server listed in the public MCP registry as io.github.tjcgraham-rgb/gaip-buyer-assurance. Now part of GAIP Witness: records a buyer's request and checks what was delivered. This page covers its hosted endpoint (https://www.gaipagents.com/mcp/agents/buyer-assurance).

Is the GAIP Buyer Assurance Agent MCP server safe to use?

GAIP Buyer Assurance Agent scores 89 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 Buyer Assurance Agent MCP server expose?

GAIP Buyer Assurance Agent exposes 3 tools: assurance_prepare, assurance_complete, assurance_verify. Their descriptions and schemas cost roughly 661 tokens of context every time the server is loaded.

Does the GAIP Buyer Assurance Agent MCP server require authentication?

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

Is the GAIP Buyer Assurance Agent MCP server still maintained?

GAIP Buyer Assurance 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 Buyer Assurance Agent MCP server?

VerifyMCP ran 13 checks on GAIP Buyer Assurance 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.