Foresea MCP server

• Registry nameink.foresea/forecastingverified in the MCP registry

The registry name sits under foresea.ink. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools28
• Server calls itselfForesea
• Server version1.30.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 82 ms.

• Its tools do every use case we checked: compare AI forecast odds with prediction market prices; review scored track record before trusting a forecast.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer121 ms
• Space in an agent's context≈ 5,526 tokensthe definitions of all its tools (28), which an agent carries on every turn
• Tool definitionsC · 68 of 100
• Typed results28 of 28 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 25 of 28
• Not saying whether it only reads or can destroy: 28 of 28

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• foresea_forecast

  Call this whenever the user asks about probability, likelihood, or whether something will happen. Good triggers: "Will X happen?", "What are the chances of Y?", "How likely is Z?", "What's the probability that…", "Do you think X will…"…

• foresea_analyze_market

  Call this when the user mentions a specific prediction market by URL, slug, or ticker — or asks whether a particular market is over/underpriced. Good triggers: "Is this Polymarket fair?", "What's the edge on kalshi:XXXXX?", "Should I…

• foresea_scan_markets

  Call this when the user wants to find mispriced or interesting markets, not evaluate a specific one. Good triggers: "What should I bet on?", "Find me trading opportunities", "Which markets are mispriced right now?", "What's Foresea's best…

• foresea_batch_quotes

  Call this when the user wants current price/volume for several markets at once -- a watchlist, a portfolio, "check on these 5 markets" -- instead of calling foresea_analyze_market once per market. Each ref is "platform:ident", e.g…

• foresea_check_run

  Call this after foresea_analyze_market timed out or errored with a message naming a client_run_key -- the research it started may still be running server-side. Returns {"status": "running", ...} if it's not done yet (call again in a bit)…

• foresea_track_record

  Call this when the user asks how reliable or accurate Foresea is, or wants to know whether to trust a forecast. Good triggers: "How good is Foresea?", "What's the track record?", "Has it been right before?", "Is it calibrated?", "What's…

• foresea_edge_board

  Call this when the user wants the current top trading opportunities with explicit trade directions and historical backing. Good triggers: "What are the best bets right now?", "Show me the edge board", "Which model is winning the…

• foresea_venue_data

  Read public historical markets/candles/trades, batch books/midpoints/spreads, fees, holders, open interest, event volume, milestones and weather. Omit operation to discover operation names and schemas. No account or write access.

• foresea_exchange_status

  Call this to check Kalshi exchange operational status (trading active flag) and operational hours/schedule.

• foresea_orderbook

  Call this to fetch the live bids and asks orderbook depth for a Kalshi market ticker (e.g. 'KXFED-25JUN-H') or Polymarket YES-token ID.

• foresea_market_tags

  Call this to sample Polymarket's category vocabulary. Each entry is a label and the slug that identifies it. This is one page of at most 100 tags, not the full taxonomy: Polymarket has tens of thousands, and the endpoint returns a fixed…

• foresea_price_history

  Call this to retrieve historical price series or OHLC candlesticks for a market (e.g. Kalshi ticker or Polymarket token/slug).

• foresea_live_data

  Call this to fetch real-time sports game statistics, play-by-play data, and live event feeds from Kalshi. Provide event_ticker for event charts, or milestone_id with data_type="game_stats" for play-by-play.

• foresea_polymarket_meta

  Call this to fetch Polymarket metadata: event series listings, community discussion comments for a market, or sports league metadata (target: 'series', 'comments', 'sports', 'teams'). 'series' lists the series and how many events each…

• foresea_recent_trades

  Call this to fetch recent public executed trades / trade tape (prices, sizes, timestamps) on Kalshi or Polymarket.

• foresea_market_leaderboard

  Call this to fetch the top profitable prediction market trader leaderboard and rankings from Polymarket.

• foresea_debate_market

  Conduct an adversarial multi-agent debate (Bull vs. Bear vs. Chief Risk Judge) to cross-examine evidence and isolate blind spots on a forecasting question.

• foresea_optimize_portfolio

  Calculate optimal mathematical Fractional Kelly capital allocations and position sizes across live Grade A/B prediction market opportunities.

• foresea_feed_latest

  Fetch the real-time unified Foresea Alpha & Agent Feed, combining live prediction market edge signals, autonomous agent trades & theses, and leaderboard standings.

• foresea_weather_radar

  Scan live temperature and weather prediction markets (Kalshi KXHIGHNY, KXHIGHCHI, KXHIGHMIA, KXHIGHAUS, KXHIGHDEN, KXHIGHPHIL, etc.) against neural weather models (Google DeepMind WeatherNext 3 / MetNet) and high-resolution multi-model…

• foresea_weather_forecast

  Retrieve neural model weather forecasts (Google Maps Weather API / WeatherNext 3 / MetNet, ECMWF, GFS, GraphCast) with empirical station bias correction (e.g. KNYC Central Park, KMDW Chicago Midway, KDEN Denver) and strike bracket…

• foresea_batch_forecast

  Submit up to 25 forecasting questions concurrently and receive structured predictions with confidence probabilities, bull/bear factor decomposition, key catalysts, and evidence citations for each question.

• foresea_crypto_edge

  Scan real-time Kalshi cryptocurrency prediction markets (KXBTCD threshold contracts) scored against Black-Scholes zero-drift diffusion models and spot volatility. Returns tradeable market mispricings, implied odds, calibration…

• foresea_webhook_subscribe

  Subscribe an external agent HTTP callback webhook to receive real-time dispatches for new forecasts and market edge opportunities. The response contains an HMAC secret (X-Foresea-Signature) for validating incoming payloads.

• foresea_trade_account_status

  Check real prediction-market trading readiness, max order notional limits, and venue configuration statuses for Kalshi and Polymarket.

• foresea_preview_order

  Validate, normalize, and simulate guardrail checks for a real Kalshi or Polymarket order without submitting it to the exchange.

• foresea_place_order

  Submit a guarded real order to Kalshi or Polymarket. Live execution requires confirmation='PLACE REAL ORDER' and execute=True, and is protected by server notional ceilings and exchange guardrails.

• foresea_cancel_order

  Cancel an active open order on Kalshi or Polymarket using its venue order ID.