ICARE MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ICARE_API_URL | No | URL of the ICARE API | |
| ICARE_APP_URL | No | URL of the ICARE app | |
| ICARE_RPC_URL | No | RPC URL used to interact with the Base Sepolia chain | |
| ICARE_STATE_FILE | No | Wallet and session file, readable only by you | ~/.icare-mcp.json |
| ICARE_AGENT_PRIVATE_KEY | No | Use your own wallet instead of the wallet created on your machine |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| icare_walletB | Address of the agent wallet (created on this machine on first use when no key is configured), its test USDC balance, its ICARE Portfolio balance, and where to get test USDC. |
| icare_live_matchesB | Followed live matches with Win/Lose prices, pot, closing time, and recent results with their referee proof. |
| icare_activateA | Only when ICARE access codes are on: one-time activation of the agent wallet with an access code (codes are given in the ICARE Discord: https://discord.gg/SmRynyJmnK). |
| icare_betA | Place a Win/Lose prediction on an open match. Uses the agent Portfolio balance when it covers the stake + 0.10 USDC, otherwise pays the stake + 0.20 USDC network fees over x402 (gasless USDC authorization). |
| icare_positionsC | Portfolio balance and Win/Lose units held on recent matches. |
| icare_sellB | Sell Win or Lose units on an open match at the ICARE liquidity buyback price (filled within seconds when the price is offered). |
| icare_seasonB | Season 0 standings: 2 points per predicted match, 15 per match played and streamed on ICARE. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools target distinct actions (bet, sell, activate) or resources (season, live_matches, positions, wallet). However, icare_wallet and icare_positions both report portfolio balance, which could cause minor confusion, though descriptions clarify their different primary focus.
All tools share the icare_ prefix and snake_case style, which is highly consistent. The only deviation is mixing noun-based (season, positions, wallet, live_matches) and verb-based (activate, bet, sell) names, so not a strict verb_noun pattern.
Seven tools is well-scoped for a prediction market server. Each tool covers a distinct need: match data, betting, selling, position tracking, wallet management, activation, and standings.
The surface covers the core lifecycle: wallet setup, activation, viewing matches, placing bets, selling units, checking positions, and standings. Minor gaps exist, such as no explicit claim/settlement operation or comprehensive match history beyond recent results, but agents can work around these via existing tools.