Remote MCP · Endpoint

GAIP Listing Observer MCP server

No. GAIP Listing Observer answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.gaipagents.com/mcp/agents/listing-observer

The last check completed an MCP handshake.

Registry name
io.github.tjcgraham-rgb/gaip-listing-observer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
492 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Behind Second Look (preview): a shop's product page as clean data, source checks, price history.
Listing
From the official MCP registry (active).
Recent checks of GAIP Listing Observer
CheckedResultHandshake
1 hour agoHandshake completed492 ms
2 days agoHandshake completed463 ms
4 days agoHandshake completed2.73 s
6 days agoHandshake completed2.68 s
8 days agoHandshake completed1.71 s
10 days agoHandshake completed1.71 s
12 days agoHandshake completed3.62 s
14 days agoHandshake completed2.22 s
15 days agoHandshake completed2.31 s
16 days agoHandshake completed2.23 s
18 days agoHandshake completed2.29 s
20 days agoHandshake completed929 ms
22 days agoHandshake completed982 ms
24 days agoHandshake completed1.07 s

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 Listing Observer and makes no claim about it beyond what these checks measured.