isocast-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVM_PRIVATE_KEY | No | 0x-prefixed wallet key with USDC on Base Mainnet. Enables the paid/keyed tools. Free tools work without it. | |
| ISOCAST_API_URL | No | Override the API base URL (default https://api.isocast.dev). | https://api.isocast.dev |
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 |
|---|---|
| get_healthA | Check Isocast API health: liveness ( |
| get_citiesA | List every active Isocast city — slug, display name, country, temperature unit, bucket width, timezone, resolution source, station, and the latest public signal sequence number. Use this to discover which weather markets have signals. Free, no wallet or API key required. |
| get_cityA | Get one Isocast city by slug, including its current target market day and the Polymarket market URL. Free, no wallet or API key required. |
| get_sample_signalA | Get a FREE sample Isocast signal for a city — the fixed seq-1 signal (never the latest), or, when that city has no servable sample yet, a REAL past signal from another city labeled via a |
| get_signal_metaA | Get Isocast pricing and payment metadata — per-signal unit price, minimum spend, currency, network, payTo address, and the volume tier table (Min/Starter/Standard/Pro/Whale). Pass a city to also get its latestSeq. NEVER returns any signal rows. Free, no wallet or API key required. |
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 5 tools
Each tool has a clearly distinct purpose: health check, list cities, get a single city, get a sample signal, and get pricing metadata. No two tools overlap in functionality, so an agent can unambiguously select the right one.
All tool names follow the same verb_noun pattern: get_health, get_cities, get_city, get_sample_signal, get_signal_meta. This is highly predictable and consistent.
With 5 tools, the server is well-scoped for a read-only API providing public data and metadata. Each tool earns its place without redundancy or bloat.
The description explicitly references buy_signals and poll_signals as the way to get live entitled signals, but these tools are missing from the server. This leaves a significant gap in the core workflow of actually obtaining signals, making the tool surface incomplete for the apparent domain.