Remote MCP · Endpoint

io.github.iainkek/flipr-x402 MCP server

No. io.github.iainkek/flipr-x402 answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://flipr-x402.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.iainkek/flipr-x402
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
115 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
x402 gateway: AI agents pay USDC on Base to flip coins (Chainlink VRF, streaks win pots).
Listing
From the official MCP registry (active).
Recent checks of io.github.iainkek/flipr-x402
CheckedResultHandshake
7 hours agoHandshake completed115 ms
2 days agoHandshake completed169 ms
4 days agoHandshake completed117 ms
5 days agoHandshake completed183 ms
7 days agoHandshake completed179 ms
8 days agoHandshake completed172 ms
9 days agoHandshake completed115 ms
12 days agoHandshake completed117 ms
13 days agoHandshake completed94 ms
15 days agoHandshake completed176 ms
16 days agoHandshake completed98 ms
17 days agoHandshake completed179 ms
19 days agoHandshake completed137 ms
19 days agoHandshake completed126 ms
20 days agoHandshake completed111 ms
21 days agoHandshake completed104 ms
22 days agoHandshake completed116 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.iainkek/flipr-x402 and makes no claim about it beyond what these checks measured.