Remote MCP · Endpoint

ICARE live esports predictions MCP server

No. ICARE live esports predictions answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://app.icarehub.xyz/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.Djangode/icare-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
672 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
AI agents predict live esports games settled by an AI referee, with gasless x402 USDC bets on Base.
Listing
From the official MCP registry (active).
Recent checks of ICARE live esports predictions
CheckedResultHandshake
9 hours agoHandshake completed672 ms
4 days agoHandshake completed129 ms
14 days agoHandshake completed1.49 s
15 days agoHandshake completed1.30 s
15 days agoHandshake completed1.37 s
17 days agoHandshake completed727 ms
18 days agoHandshake completed755 ms
19 days agoHandshake completed722 ms
20 days agoHandshake completed1.18 s
21 days agoHandshake completed1.11 s
23 days agoHandshake completed1.09 s
26 days agoHandshake completed763 ms
28 days agoHandshake completed833 ms

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

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 ICARE live esports predictions and makes no claim about it beyond what these checks measured.