Remote MCP · Endpoint

GAIP Witness Agent MCP server

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

UpLast checked 4 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
2.67 s
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
4 hours agoHandshake completed2.67 s
2 days agoHandshake completed1.86 s
4 days agoHandshake completed2.30 s
6 days agoHandshake completed1.76 s
8 days agoHandshake completed3.30 s
10 days agoHandshake completed3.13 s
11 days agoHandshake completed2.29 s
12 days agoHandshake completed2.62 s
14 days agoHandshake completed2.90 s
16 days agoHandshake completed872 ms
18 days agoHandshake completed407 ms
20 days agoHandshake completed1.07 s
21 days agoHandshake completed889 ms
22 days agoHandshake completed409 ms

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

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.