GAIP Trust & Assurance Agent
REMOTE · WWW.GAIPAGENTS.COM
Now part of GAIP Witness: verifies GAIP receipts; evidence packs and incident bundles.
Available components
Last scanned (17 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1404 tokens (~140/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
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.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
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 →
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 +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.
- 8 Nov 26 −1
- Stability: pass → 0.93 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 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
- 4 Oct 26 0
- “gaip_incident_bundle” reworded the description of “ai_system_ref” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
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/trust-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/trust-assurance | Verified | 200 | |
| http (plaintext) | http://www.gaipagents.com/mcp/agents/trust-assurance | HTTPS enforced | 308 | https://www.gaipagents.com/mcp/agents/trust-assurance |
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_check_sar_receipt Check an x402 SAR receipt ~160
Use this when handed an x402 SAR-shaped receipt (draft proposal shape; may change). Pass `sar_receipt`, optionally the issuer's `public_key`. Returns missing fields, whether receipt_id matches the core and whether the signature checks out against that key. Free, read-only, no account; inputs must be public and non-personal.
| Name | Type | Req | Description |
|---|---|---|---|
| public_key | – | – | Optional: the issuer's Ed25519 public key, raw 32 bytes base64url or a JWK {kty: OKP, crv: Ed25519, x}. Omit to use GAIP's published keys. |
| sar_receipt | object | yes | The SAR receipt object (or a whole gaip_receipt_export x402 result). |
No output schema declared.
{"public_key":"Y8BpzlWPH3EPRQziEPRBeLS1lJBF4xEo9WaxTNbzNp0","sar_receipt":{"confidence":1,"reason_code":"SPEC_MATCH","receipt_id":"sha256:17146cdeb5aba1c269130348cdc7d3d96ae55f6e048b81d3baa59d4e3f3b188b","receipt_version":"0.1","sig":"ogilW-bjlCbYkwwUAIrg_zm_Wuoc6EiRgeErs0RL7llP7FWyX43-LgozZFyCjCXgsViK-A4_aroOo16Q4uvTCg","sig_alg":"Ed25519","task_id_hash":"sha256:c8b36982316351a28e040a6520df2092c2c87a4ea611c123d04993074b2b6f1d","ts":"2026-10-01T09:00:00Z","verdict":"PASS","verifier_kid":"ef654fc8b615b51c"}} gaip_evidence_pack Build an evidence pack ~148
Use this when an insurer, auditor or buyer asks what evidence exists about an agent or supplier. Pass its `subject` (public id or https URL). Returns conformance, watch, witness, repair and incident records with Merkle proofs, plus gaps. A compilation, not certification or advice. Free, read-only, no account; inputs must be public and non-personal.
| Name | Type | Req | Description |
|---|---|---|---|
| requester | object | – | Optional: {purpose, continuity_handle} to include your own receipts. |
| scope | object | – | Optional: {receipt_ids, since, until, categories, max_items}. |
| subject | – | yes | The agent or supplier: its public id or https URL. Never a person. |
No output schema declared.
{"requester":{"purpose":"INSURER"},"scope":{"max_items":50,"since":"2026-09-01"},"subject":{"counterparty_id":"example-weather-agent"}} gaip_incident_bundle Build an incident evidence bundle ~197
Use this when something went wrong with an agent and you need the facts in order. Pass the `receipt_ids` you hold and attributed `observations`. Returns a verified, source-attributed timeline with an EU AI Act Art. 73 reference aid. No fault, cause or liability finding. Free, read-only, no account; inputs must be public and non-personal.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_system_ref | string | – | Optional: public id or URL of the AI system involved; given alone, GAIP starts the timeline from its own public records of that system. |
| data_classification | string | – | PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data. |
| observations | array | – | Attributed observations, each {source, statement, observed_at_utc}. |
| receipt_ids | array | – | GAIP receipt ids you hold about the incident. |
| title | string | – | Optional: short incident title. |
No output schema declared.
{"ai_system_ref":"example-weather-agent","observations":[{"observed_at_utc":"2026-09-27T10:00:00Z","source":"our uptime monitor","source_type":"AUTOMATED_MONITOR","statement":"HTTP 503 from the forecast endpoint for 12 minutes"}],"receipt_ids":["\u003creceipt_id returned by any GAIP tool\u003e"],"title":"Forecast endpoint returned errors"} gaip_receipt_export Export a GAIP receipt ~162
Use this when you need a GAIP receipt in another format. Pass `receipt_id` and `format`: x402 (attestation style), erc8004 (validation-response shape) or vc (W3C-VC-like JSON-LD). Ed25519-signed when the runtime key is available; hash chain and Merkle proof; no on-chain write. Free, read-only, no account; inputs must be public and non-personal.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | x402, erc8004 or vc. |
| receipt_id | string | yes | The receipt_id exactly as an earlier GAIP result returned it. Have none? Call with any id: the refusal lists example_receipt_ids from GAIP's own public records. |
No output schema declared.
{"format":"x402","receipt_id":"\u003creceipt_id returned by any GAIP tool\u003e"} inspect_counterparty_evidence What evidence exists about this agent? ~286
Use this when asked what evidence exists about an agent before delegating to it. Pass its `counterparty_id` and any `observations`. Returns task-specific evidence coverage, conflicts, gaps and GAIP's own earlier checks of it, with a receipt. Never a trust score or recommendation. Free, read-only, no account; inputs must be public and non-personal.
| Name | Type | Req | Description |
|---|---|---|---|
| continuity_handle | object | – | Optional: the continuity_handle from an earlier GAIP result; links this call to your earlier ones. |
| counterparty_id | string | – | Name or URL of the agent or service. |
| data_classification | string | – | PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data. |
| episode_id | string | – | Optional: your own id to group related calls. |
| independent_operator_id | string | – | Optional: your operator id (recorded as a claim, not verified). |
| max_age_days | integer | – | Optional freshness window (default 30): GAIP history records older than this are STALE and do not count toward evidence_sufficiency. |
| observations | array | – | Optional: observations about it, each {source, observed_at, evidence_digest, lifecycle_state, claim}. |
| synthetic | boolean | – | Optional: true marks a test call. |
| task_class | string | – | Task you want evidence for. Optional. |
No output schema declared.
{"counterparty_id":"example-weather-agent","observations":[{"claim":"Publishes a public weather_forecast skill","evidence_digest":"3f0a9c1e5b7d2468ace013579bdf2468ace013579bdf2468ace013579bdf2468","lifecycle_state":"observed","observed_at":"2026-09-27T12:00:00Z","source":"https://forecast.example.com/.well-known/agent-card.json"},{"claim":"Returned a London forecast in 1.2 s","lifecycle_state":"OBSERVED","observed_at":"2026-09-27T12:05:00Z","source":"caller_task_log"}],"task_class":"weather_forecast"} verify_gaip_receipt Verify a GAIP receipt ~197
Use this when you hold a GAIP receipt_id and want to confirm it ("is this receipt genuine?"). Returns the retained record, hash chain and Merkle inclusion proof. Integrity only: it does not make the underlying claim true. Free, read-only, no account; inputs must be public and non-personal.
| Name | Type | Req | Description |
|---|---|---|---|
| continuity_handle | object | – | Optional: the continuity_handle from an earlier GAIP result; links this call to your earlier ones. |
| data_classification | string | – | PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data. |
| episode_id | string | – | Optional: your own id to group related calls. |
| independent_operator_id | string | – | Optional: your operator id (recorded as a claim, not verified). |
| receipt_id | string | yes | A receipt_id returned by an earlier GAIP call. |
| synthetic | boolean | – | Optional: true marks a test call. |
No output schema declared.
{"receipt_id":"\u003creceipt_id returned by any GAIP tool\u003e"} How do I install the GAIP Trust & Assurance Agent MCP server?
GAIP Trust & Assurance Agent is a hosted endpoint at https://www.gaipagents.com/mcp/agents/trust-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
claude mcp add --transport http tjcgraham-rgb-gaip-trust-assurance 'https://www.gaipagents.com/mcp/agents/trust-assurance'
What is the GAIP Trust & Assurance Agent MCP server?
GAIP Trust & Assurance Agent is an MCP server listed in the public MCP registry as io.github.tjcgraham-rgb/gaip-trust-assurance. Now part of GAIP Witness: verifies GAIP receipts; evidence packs and incident bundles. This page covers its hosted endpoint (https://www.gaipagents.com/mcp/agents/trust-assurance).
Is the GAIP Trust & Assurance Agent MCP server safe to use?
GAIP Trust & Assurance 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 Trust & Assurance Agent MCP server expose?
GAIP Trust & Assurance Agent exposes 6 tools: inspect_counterparty_evidence, gaip_receipt_export, verify_gaip_receipt, gaip_evidence_pack, gaip_incident_bundle, gaip_check_sar_receipt. Their descriptions and schemas cost roughly 1,150 tokens of context every time the server is loaded.
Does the GAIP Trust & Assurance Agent MCP server require authentication?
No. We connected to GAIP Trust & Assurance Agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GAIP Trust & Assurance Agent MCP server still maintained?
GAIP Trust & 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 Trust & Assurance Agent MCP server?
VerifyMCP ran 13 checks on GAIP Trust & 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.