Remote MCP · Endpoint

io.github.getgapup/gapup-mcp MCP server

No. io.github.getgapup/gapup-mcp answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.gapup.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.getgapup/gapup-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
463 ms
Tools exposed
Not measured yet
Uptime, last 30 days
58.8% from 17 checks
Described by its publisher as
271 agent-payable tools: competitive intel, finance, KYC, compliance, ESG. x402 per-call.
Listing
From the official MCP registry (active).
Recent checks of io.github.getgapup/gapup-mcp
CheckedResultHandshake
2 hours agoHandshake completed463 ms
2 days agoHandshake completed464 ms
4 days agoHandshake completed430 ms
5 days agoHandshake completed142 ms
7 days agoHandshake completed166 ms
8 days agoHandshake completed390 ms
9 days agoHandshake completed424 ms
12 days agoHandshake completed141 ms
13 days agoHandshake completed462 ms
15 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
19 days agoHandshake completed124 ms
20 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
22 days agoFailed - the server returned an HTTP error—

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

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 io.github.getgapup/gapup-mcp and makes no claim about it beyond what these checks measured.