ICARE live esports predictions MCP server
io.github.Djangode/icare-mcpDjangodestreamable-httpv0.2.0Scanned
AI agents predict live esports games settled by an AI referee, with gasless x402 USDC bets on Base.
6 tools: 3 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 6
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ICARE live esports predictions MCP server can do
The ICARE live esports predictions MCP server is published by the GitHub account Djangode. It has 6 tools. It can create or change data (3 tools: icare_live_matches, icare_bet_link and icare_season), but cannot delete data. 3 tools only read.
6 tools bring in text other people can write (icare_live_matches, icare_match, icare_bet_link and 3 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 3Claude Code: ask
icare_bet_linkLink 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.Reads text others write1 finding
Why it is in this group
- The name "icare_bet_link" says "link": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "icare_bet_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "icare_bet_link" says "link": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
icare_live_matchesFollowed live matches with Win/Lose prices, pot, closing time, stream and match page; optionally recent results with their referee proof.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Followed live matches with Win/Lose prices, pot, closing time, stream and match page; optionally recent results with their referee proof.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
icare_seasonSeason 0 standings: points, rank and qualification of the top wallets.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Season 0 standings: points, rank and qualification of the top wallets.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 3Show 3 read-only tools
fetchFull record of one ICARE match by id (from search).Reads text others writeNo findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Full record of one ICARE match by id (from search).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
icare_matchStatus, Win/Lose prices, pot, result and referee proof of one match.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "status": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Status, Win/Lose prices, pot, result and referee proof of one match.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
searchSearch followed ICARE matches by streamer or game; returns ids for fetch.Reads text others writeNo findings
Why it is in this group
- The name "search" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search followed ICARE matches by streamer or game; returns ids for fetch.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:57 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://app.icarehub.xyz/api/mcp: tools/list returned 6 tools to an anonymous client, including icare_live_matches (write), icare_bet_link (write), icare_season (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnicare_bet_link
The server marks "icare_bet_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "icare_bet_link" says "link": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http icare https://app.icarehub.xyz/api/mcpclaude mcp add --transport http icare https://app.icarehub.xyz/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__icare__icare_match",
"mcp__icare__search",
"mcp__icare__fetch"
],
"ask": [
"mcp__icare__icare_live_matches",
"mcp__icare__icare_bet_link",
"mcp__icare__icare_season"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as icare. Review it before you use it.
Capability tags behind 6 rules
- mcp__icare__icare_live_matches untrusted-input
- mcp__icare__icare_match untrusted-input
- mcp__icare__icare_bet_link untrusted-input
- mcp__icare__icare_season untrusted-input
- mcp__icare__search untrusted-input
- mcp__icare__fetch untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Djangode/icare-mcp/verify?hash=700f20de0b5de4baa92df1a1abc59c3d8e9a0b60b12f283b114063ddfaf34a04" | jq -e '.changed == false'Pinned hash 700f20de0b5d, from Nov 15, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Djangode/icare-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Djangode/icare-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:15 UTC.
ICARE live esports predictions MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ICARE live esports predictions MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ICARE live esports predictions MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ICARE live esports predictions MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ICARE live esports predictions MCP server have?
- 6 tools: 3 write, 3 read. icare_live_matches, icare_bet_link, icare_season, icare_match, search and fetch.
Does the ICARE live esports predictions MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ICARE live esports predictions MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ICARE live esports predictions MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.