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 Procurement Evidence Agent

REMOTE · WWW.GAIPAGENTS.COM

Now part of GAIP Witness: tests supplier claims and compares them with published metadata.

0 this week 90 Trust /100

Last scanned (19 hours ago)

Scores higher than 97% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

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
  • Tool/resource definitions use about 554 tokens (~110/item across 5 items; 1 tools + 4 resources), lean.Pass
  • 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 1 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 0
    • Stability: 0.97 → pass security
  • 9 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Stability: 0.97 → pass security
  • 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 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Oct 26 0
    • Server version: 1.4.0 → 1.5.0 functional
  • 2 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “gaip_verify_supplier_claims” rewrote its description, which is the text the model reads security
    • Server version: 1.3.0 → 1.4.0 functional
    • Server version: 1.2.0 → 1.3.0 functional
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/procurement-verify

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/procurement-verify Verified 200
http (plaintext) http://www.gaipagents.com/mcp/agents/procurement-verify HTTPS enforced 308 https://www.gaipagents.com/mcp/agents/procurement-verify
MCP tools · 1 exposed · ~321 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
gaip_verify_supplier_claims ~321

Use this to check what an agent, API or supplier claims. Pass `claims` (each with an `id`; add `check_url` and GAIP tests it now), your `observations` and `metadata`. Returns per claim what GAIP saw, what you reported and whether they agree. Free, no account; records a GAIP receipt only. Inputs must be public and non-personal.

NameTypeReqDescription
claimsarrayyesClaims to check, each {id, text}.
continuity_handleobject–Optional: the continuity_handle from an earlier GAIP result; links this call to your earlier ones.
counterparty_idstring–Name or URL of the agent/service. Optional.
data_classificationstring–PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data.
episode_idstring–Optional: your own id to group related calls.
independent_operator_idstring–Optional: your operator id (recorded as a claim, not verified).
metadataobjectyesThe published agent card, MCP server description or OpenAPI document (as JSON).
observationsarray–Optional: what you saw, each {claim_id, result: PASS|FAIL, detail}.
protocolstring–Counterparty protocol. Inferred from metadata when omitted, otherwise MCP.
syntheticboolean–Optional: true marks a test call.
task_classstring–Optional: short name of the task, e.g. weather_forecast.

No output schema declared.

{"claims":[{"id":"c1","text":"Returns JSON forecasts over MCP"},{"id":"c2","text":"Responds within 2 seconds"}],"counterparty_id":"example-weather-agent","metadata":{"protocolVersion":"2025-06-18","url":"https://weather.example.com/mcp"},"observations":[{"claim_id":"c1","detail":"tools/call returned valid JSON","result":"PASS"},{"claim_id":"c2","detail":"p95 latency 4.8 s over 20 calls","result":"FAIL"}]}
Install

How do I install the GAIP Procurement Evidence Agent MCP server?

GAIP Procurement Evidence Agent is a hosted endpoint at https://www.gaipagents.com/mcp/agents/procurement-verify, 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-procurement-verify 'https://www.gaipagents.com/mcp/agents/procurement-verify'
Common questions

What is the GAIP Procurement Evidence Agent MCP server?

GAIP Procurement Evidence Agent is an MCP server listed in the public MCP registry as io.github.tjcgraham-rgb/gaip-procurement-verify. Now part of GAIP Witness: tests supplier claims and compares them with published metadata. This page covers its hosted endpoint (https://www.gaipagents.com/mcp/agents/procurement-verify).

Is the GAIP Procurement Evidence Agent MCP server safe to use?

GAIP Procurement Evidence 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 Procurement Evidence Agent MCP server expose?

GAIP Procurement Evidence Agent exposes 1 tool: gaip_verify_supplier_claims. Their descriptions and schemas cost roughly 321 tokens of context every time the server is loaded.

Does the GAIP Procurement Evidence Agent MCP server require authentication?

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

Is the GAIP Procurement Evidence Agent MCP server still maintained?

GAIP Procurement Evidence 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 Procurement Evidence Agent MCP server?

VerifyMCP ran 13 checks on GAIP Procurement Evidence 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.