Remote MCP · Endpoint

io.github.gosadu/loophole-tape MCP server

No. io.github.gosadu/loophole-tape answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.loopholetape.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.gosadu/loophole-tape
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
223 ms
Tools exposed
34 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
pump.fun & Robinhood Chain launch data: radar, risk checks, delta feed, datasets, keys. x402 USDC
Listing
From the official MCP registry (active).
Recent checks of io.github.gosadu/loophole-tape
CheckedResultHandshake
1 hour agoHandshake completed223 ms
1 day agoHandshake completed208 ms
2 days agoHandshake completed203 ms
3 days agoFailed - the server returned an HTTP error—
4 days agoHandshake completed195 ms
5 days agoHandshake completed274 ms
6 days agoHandshake completed211 ms
9 days agoHandshake completed222 ms
11 days agoHandshake completed263 ms
14 days agoHandshake completed212 ms
16 days agoHandshake completed659 ms
18 days agoHandshake completed193 ms
20 days agoHandshake completed182 ms
22 days agoHandshake completed236 ms
24 days agoHandshake completed194 ms
26 days agoHandshake completed220 ms
27 days agoHandshake completed181 ms
29 days agoHandshake completed212 ms

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

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.gosadu/loophole-tape and makes no claim about it beyond what these checks measured.