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 Supplier Watch Agent

REMOTE · WWW.GAIPAGENTS.COM

Now part of GAIP Check and GAIP Watch: compares supplier snapshots and watches for change.

0 this week 83 Trust /100

Last scanned (16 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

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 Usability87
  • 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 1518 tokens (~151/item across 10 items; 6 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
  • 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: this server exposes a tool marked destructive (gaip_watch_remove) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.

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
  • 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.

  • 11 Oct 26 0
    • Server version: 1.4.0 → 1.5.0 functional
  • 2 Oct 26 0
    • Server version: 1.3.0 → 1.4.0 functional
    • Server version: 1.2.0 → 1.3.0 functional
    • “gaip_watch_register” added an optional parameter “sla” cosmetic
    • “gaip_watch_register” reworded the description of “interval_hours” cosmetic
    • “gaip_watch_register” reworded the description of “kind” cosmetic
    • “gaip_watch_register” reworded the description of “terms_id” cosmetic
  • 1 Oct 26 0
    • “gaip_supplier_reliability” added an optional parameter “card” cosmetic
    • “gaip_supplier_reliability” added an optional parameter “transport” cosmetic
    • “gaip_supplier_reliability” reworded the description of “protocol” cosmetic

    3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

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/supplier-watch

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/supplier-watch Verified 200
http (plaintext) http://www.gaipagents.com/mcp/agents/supplier-watch HTTPS enforced 308 https://www.gaipagents.com/mcp/agents/supplier-watch
MCP tools · 6 exposed · ~1,269 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_compare_supplier_snapshots ~291

Use this when asked what changed between two versions of an agent card, MCP server description or OpenAPI document ("did this API break?"). Pass `prior` and `current`. Returns each change as BREAKING / NON_BREAKING / INFO with migration notes and a receipt. Free, no account; records a GAIP receipt only. Inputs must be public and non-personal.

NameTypeReqDescription
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.
currentobjectyesThe later version, same kind as `prior`.
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).
priorobjectyesThe earlier version: agent card, MCP server description, OpenAPI document or snapshot.
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.

{"counterparty_id":"example-weather-agent","current":{"capabilities":{"streaming":true},"name":"Weather Agent","protocolVersion":"0.3.0","security":[{"bearer":[]}],"securitySchemes":{"bearer":{"scheme":"bearer","type":"http"}},"skills":[{"id":"forecast","name":"Forecast"}],"url":"https://weather.example.com/v2/a2a","version":"2.0.0"},"prior":{"capabilities":{"streaming":true},"name":"Weather Agent","protocolVersion":"0.3.0","skills":[{"id":"forecast","name":"Forecast"},{"id":"alerts","name":"Severe weather alerts"}],"url":"https://weather.example.com/a2a","version":"1.4.0"}}
gaip_supplier_reliability ~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.

NameTypeReqDescription
cardobject–Optional supplier card / server description you integrated against.
counterparty_idstring–Optional: name of the supplier.
data_classificationstring–PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data.
failureobject–{code, detail?, http_status?} as for gaip_diagnose_integration_failure.
failure_started_atstring–Optional: RFC 3339 time the failures started.
failuresarray–Optional: several failures, each {code, detail}.
lookback_daysinteger–Optional: days of GAIP observations to look back over.
protocolstring–Omit to infer it from card, transport or the supplier URL path (else UNKNOWN).
supplier_urlstringyesPublic https URL of the supplier's agent card, MCP server or API.
task_classstring–Optional: short name of the task, e.g. weather_forecast.
transportstring–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"}
gaip_watch_events ~128

Use this when asked what changed on a watched agent or service. Pass your `continuity_handle` and optionally a `watch_id`. Returns recent change events: verdict before and after, a change summary, the receipt and webhook delivery status. Free, read-only, no account; inputs must be public and non-personal.

NameTypeReqDescription
continuity_handleobjectyesThe continuity_handle from an earlier GAIP result; proves you own these watches.
limitinteger–Optional: maximum events to return.
watch_idstring–The watch_id returned by gaip_watch_register.

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

Use this when asked which agents or services you are watching. Pass your `continuity_handle`. Returns each watch's kind, target, last verdict, last and next check and webhook endpoint (never the secret). Free, read-only, no account; inputs must be public and non-personal.

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 ~337

Use this when asked to keep an eye on an agent or MCP server ("tell me if it changes or goes down"). Pass the `continuity_handle` from any GAIP result, `kind` and `target_url`. GAIP re-checks every 24 hours (3 free watches), receipts each change and can call your webhook. Free, no account; records a GAIP receipt only. Inputs must be public and non-personal.

NameTypeReqDescription
continuity_handleobjectyesThe continuity_handle from an earlier GAIP result; proves you own these watches.
data_classificationstring–PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data.
interval_hoursinteger–Hours between checks: 24 minimum on the free tier; 1 for DELIVERY_SLA.
kindstringyesAGENT_READINESS (agent URL), SUPPLIER_CARD (published card), DELIVERY_TERMS (terms_id) or DELIVERY_SLA (terms_id plus sla terms).
slaobject–DELIVERY_SLA only: service-level terms checked on every observation, any of min_uptime_pct, max_latency_ms, required_fields (JSON key paths), freshness_field + max_age_seconds; optional uptime_window…
target_urlstring–Public https URL (AGENT_READINESS, SUPPLIER_CARD). No query string.
terms_idstring–DELIVERY_TERMS or DELIVERY_SLA: 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"}
gaip_watch_remove ~108

Use this when asked to stop watching an agent or service. Pass your `continuity_handle` and the `watch_id`. Its stored events are deleted; retained receipts stay verifiable. Free, no account; records a GAIP receipt only. Inputs must be public and non-personal.

NameTypeReqDescription
continuity_handleobjectyesThe continuity_handle from an earlier GAIP result; proves you own these watches.
watch_idstringyesThe watch_id returned by gaip_watch_register.

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"}
Install

How do I install the GAIP Supplier Watch Agent MCP server?

GAIP Supplier Watch Agent is a hosted endpoint at https://www.gaipagents.com/mcp/agents/supplier-watch, 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-supplier-watch 'https://www.gaipagents.com/mcp/agents/supplier-watch'
Common questions

What is the GAIP Supplier Watch Agent MCP server?

GAIP Supplier Watch Agent is an MCP server listed in the public MCP registry as io.github.tjcgraham-rgb/gaip-supplier-watch. Now part of GAIP Check and GAIP Watch: compares supplier snapshots and watches for change. This page covers its hosted endpoint (https://www.gaipagents.com/mcp/agents/supplier-watch).

Is the GAIP Supplier Watch Agent MCP server safe to use?

GAIP Supplier Watch Agent scores 83 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 Supplier Watch Agent MCP server expose?

GAIP Supplier Watch Agent exposes 6 tools: gaip_compare_supplier_snapshots, gaip_watch_register, gaip_watch_list, gaip_watch_remove, gaip_watch_events, gaip_supplier_reliability. Their descriptions and schemas cost roughly 1,269 tokens of context every time the server is loaded.

Does the GAIP Supplier Watch Agent MCP server require authentication?

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

Is the GAIP Supplier Watch Agent MCP server still maintained?

GAIP Supplier Watch 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 Supplier Watch Agent MCP server?

VerifyMCP ran 12 checks on GAIP Supplier Watch Agent, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about GAIP Supplier Watch Agent: Authorization. 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.