Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ICARE live esports predictions

REMOTE · APP.ICAREHUB.XYZ · 2 COMPONENTS

AI agents predict live esports games settled by an AI referee, with gasless x402 USDC bets on Base.

68 Trust /100

Last scanned (5 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 391 tokens (~65/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 17% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Oct 26 67

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://app.icarehub.xyz/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=icarehub.xyz CN=WE1,O=Google Trust Services,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA256 bf5531cc9dc932a0e51c2bc1a200c4c
SANs: icarehub.xyz, app.icarehub.xyz, *.app.icarehub.xyz
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.icarehub.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
icarehub.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' https://embed.twitch.tv; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https://avatars.steamstatic.com https://steamcdn-a.akamaihd.net https://cdn.cloudflare.steamstatic.com https://media.steampowered.com https://api.icarehub.xyz; font-src 'self' data: https://fonts.gstatic.com; media-src 'self' blob:; connect-src 'self' https://api.icarehub.xyz https://*.akamaized.net https://*.pstatic.net https://*.tiktokcdn.com https://*.tiktokcdn-eu.com https://*.tiktokcdn-us.com https://*.douyincdn.com https://*.douyinliving.com https://*.100ycdn.com https://*.douyucdn.cn https://*.douyucdn2.cn https://*.livehwc4.com https://*.ably.io wss://*.ably.io https://*.ably.net wss://*.ably.net https://*.ably-realtime.com wss://*.ably-realtime.com https://*.ably.com wss://*.ably.com https://sepolia.base.org https://*.base.org https://*.publicnode.com https://*.alchemyapi.io https://*.alchemy.com https://*.infura.io https://*.coinbase.com https://*.w
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.icarehub.xyz/api/mcp Verified 200
http (plaintext) http://app.icarehub.xyz/api/mcp HTTPS enforced 308 https://app.icarehub.xyz/api/mcp
MCP tools · 6 exposed · ~227 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fetch ~27

Full record of one ICARE match by id (from search).

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

icare_bet_link ~59

Link to the match page where the user predicts Win or Lose with their own wallet (gasless USDC), and the command of the local agent that predicts automatically.

NameTypeReqDescription
matchIdstringyes–
sidestring––

No output schema declared.

No examples provided.

icare_live_matches ~53

Followed live matches with Win/Lose prices, pot, closing time, stream and match page; optionally recent results with their referee proof.

NameTypeReqDescription
includeFinishedboolean–Also return recent settled or refunded matches

No output schema declared.

No examples provided.

icare_match ~34

Status, Win/Lose prices, pot, result and referee proof of one match.

NameTypeReqDescription
matchIdstringyes–

No output schema declared.

No examples provided.

icare_season ~25

Season 0 standings: points, rank and qualification of the top wallets.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~29

Search followed ICARE matches by streamer or game; returns ids for fetch.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the ICARE live esports predictions MCP server?

ICARE live esports predictions is a hosted endpoint at https://app.icarehub.xyz/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.icarehub.xyz

# add to Claude Code
claude mcp add --transport http djangode-icare-mcp 'https://app.icarehub.xyz/api/mcp'
Common questions

What is the ICARE live esports predictions MCP server?

ICARE live esports predictions is an MCP server listed in the public MCP registry as io.github.Djangode/icare-mcp. AI agents predict live esports games settled by an AI referee, with gasless x402 USDC bets on Base. This page covers its hosted endpoint (https://app.icarehub.xyz/api/mcp).

Is the ICARE live esports predictions MCP server safe to use?

ICARE live esports predictions scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ICARE live esports predictions MCP server expose?

ICARE live esports predictions exposes 6 tools: icare_live_matches, icare_match, icare_bet_link, icare_season, search, fetch. Their descriptions and schemas cost roughly 227 tokens of context every time the server is loaded.

Does the ICARE live esports predictions MCP server require authentication?

No. We connected to ICARE live esports predictions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ICARE live esports predictions MCP server still maintained?

ICARE live esports predictions is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.