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 Outcome & Value Agent

REMOTE · WWW.GAIPAGENTS.COM · SCANNED SEP 28

Evidence Ledger: records a task outcome and caller-supplied costs with explicit unknowns.

68 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 Security80
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 368 tokens (~368/item across 1 items; 1 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
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 2 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 Outcome & Value Agent MCP server?

GAIP Outcome & Value Agent is a hosted endpoint at https://www.gaipagents.com/mcp/agents/outcome-value, 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-outcome-value 'https://www.gaipagents.com/mcp/agents/outcome-value'
// .cursor/mcp.json
{
  "mcpServers": {
    "tjcgraham-rgb-gaip-outcome-value": {
      "url": "https://www.gaipagents.com/mcp/agents/outcome-value"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "tjcgraham-rgb-gaip-outcome-value": {
      "type": "http",
      "url": "https://www.gaipagents.com/mcp/agents/outcome-value"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.tjcgraham-rgb-gaip-outcome-value]
url = "https://www.gaipagents.com/mcp/agents/outcome-value"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tjcgraham-rgb-gaip-outcome-value": {
      "type": "remote",
      "url": "https://www.gaipagents.com/mcp/agents/outcome-value",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tjcgraham-rgb-gaip-outcome-value --url 'https://www.gaipagents.com/mcp/agents/outcome-value' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  tjcgraham-rgb-gaip-outcome-value:
    url: "https://www.gaipagents.com/mcp/agents/outcome-value"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "tjcgraham-rgb-gaip-outcome-value": {
      "Transport": "http",
      "Url": "https://www.gaipagents.com/mcp/agents/outcome-value"
    }
  }
}
# add to Vellum
assistant mcp add tjcgraham-rgb-gaip-outcome-value -t streamable-http -u 'https://www.gaipagents.com/mcp/agents/outcome-value'
// mcp.json
{
  "mcpServers": {
    "tjcgraham-rgb-gaip-outcome-value": {
      "type": "http",
      "url": "https://www.gaipagents.com/mcp/agents/outcome-value"
    }
  }
}

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 +1
    • Schema quality: pass → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: fail → pass ▲ functional
    • Schema quality: fair → good 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/outcome-value

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

Independent outcome evidence for outcome-priced contracts: record what a task actually delivered and what the caller says it cost. Pass `counterparty_id`, `task_class`, `episode_id`, the `task` (acceptance_criteria), `delivery` (status) and `costs`; get a delivery, downstream-use and full-cost dossier with a receipt. Missing costs and unverified claims stay explicit; no ROI claim. Free, read-only, no account. Inputs must be public and non-personal; calling declares that (data_classification defaults to PUBLIC).

NameTypeReqDescription
baseline_cost_gbp–––
continuity_handleobject––
costsobjectyes–
counterparty_idstring––
data_classificationstring––
deliveryobjectyes–
downstream_useobject––
episode_idstringyes–
evidence_refsarray––
independent_operator_idstring––
syntheticboolean––
taskobjectyes–
task_classstring––

No output schema declared.

{"baseline_cost_gbp":"12.00","costs":{"agent_gbp":"0.40","compute_gbp":"0.12","human_review_gbp":"3.50","repair_gbp":"0"},"counterparty_id":"example-weather-agent","delivery":{"receipt_id":"example-receipt-1","status":"ACCEPTED"},"downstream_use":{"evidence_ref":"example-ticket-4411","status":"USED"},"episode_id":"example-episode-1","observed_at_utc":"2026-09-27T21:00:00Z","task":{"acceptance_criteria":"Forecast JSON for London returned within 5 seconds"},"task_class":"weather_forecast","unit_label":"forecast","units":7}
Common questions

What is the GAIP Outcome & Value Agent MCP server?

GAIP Outcome & Value Agent is an MCP server listed in the public MCP registry as io.github.tjcgraham-rgb/gaip-outcome-value. Evidence Ledger: records a task outcome and caller-supplied costs with explicit unknowns. This page covers its hosted endpoint (https://www.gaipagents.com/mcp/agents/outcome-value).

Is the GAIP Outcome & Value Agent MCP server safe to use?

GAIP Outcome & Value Agent scores 68 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 Outcome & Value Agent MCP server expose?

GAIP Outcome & Value Agent exposes 1 tool: gaip_measure_outcome_value. Their descriptions and schemas cost roughly 227 tokens of context every time the server is loaded.

Does the GAIP Outcome & Value Agent MCP server require authentication?

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

Is the GAIP Outcome & Value Agent MCP server still maintained?

GAIP Outcome & Value 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.