Remote MCP · Endpoint

GAIP Witness Agent MCP server

No. GAIP Witness Agent answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://www.gaipagents.com/mcp/agents/witness

The last check completed an MCP handshake.

Registry name
io.github.tjcgraham-rgb/gaip-witness
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
404 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Witness: agreed terms, delivery checks, signed receipts, dispute bundles and evidence packs.
Listing
From the official MCP registry (active).
Recent checks of GAIP Witness Agent
CheckedResultHandshake
3 hours agoHandshake completed404 ms
9 days agoHandshake completed449 ms
10 days agoHandshake completed572 ms
11 days agoHandshake completed501 ms
12 days agoHandshake completed399 ms
14 days agoHandshake completed420 ms
14 days agoHandshake completed518 ms
15 days agoHandshake completed602 ms
17 days agoHandshake completed503 ms
19 days agoHandshake completed476 ms
21 days agoHandshake completed452 ms
24 days agoHandshake completed557 ms
26 days agoHandshake completed2.67 s
28 days agoHandshake completed1.86 s

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 26.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with GAIP Witness Agent and makes no claim about it beyond what these checks measured.