Remote MCP · Endpoint

GAIP Buyer Assurance Agent MCP server

No. GAIP Buyer Assurance Agent answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://www.gaipagents.com/mcp/agents/buyer-assurance

The last check completed an MCP handshake.

Registry name
io.github.tjcgraham-rgb/gaip-buyer-assurance
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.05 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Now part of GAIP Witness: records a buyer's request and checks what was delivered.
Listing
From the official MCP registry (active).
Recent checks of GAIP Buyer Assurance Agent
CheckedResultHandshake
2 days agoHandshake completed1.05 s
4 days agoHandshake completed1.46 s
6 days agoHandshake completed882 ms
8 days agoHandshake completed922 ms
10 days agoHandshake completed885 ms
11 days agoHandshake completed429 ms
13 days agoHandshake completed952 ms
14 days agoHandshake completed1.04 s
15 days agoHandshake completed1.29 s
18 days agoHandshake completed355 ms
19 days agoHandshake completed372 ms
21 days agoHandshake completed1.17 s
22 days agoHandshake completed900 ms
24 days agoHandshake completed734 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 Buyer Assurance Agent and makes no claim about it beyond what these checks measured.