Foresea Forecasting MCP server

• foresea_analyze_marketFree

  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 buy/sell this market?", user pastes a Polymarket or Kalshi URL. Fetches the live price, gathers evidence, forecasts, computes model-vs-market edge, and returns a recommendation. Use foresea_forecast instead when there is no specific live market — just a general probability question. Example: platform="polymarket", slug="fed-rate-cut-march-2026" → {model_probability, market_probability, edge, stance, recommendation, thesis}.

• foresea_batch_quotesFree

  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. "kalshi:KXFED-25JUN-H" or "polymarket:some-market-slug". Every quote carries fetched_at and age_seconds so you can judge freshness yourself -- both venues rate-limit hard, so don't assume a quote is live without checking age_seconds. One bad ref returns an error on that entry only; the rest of the batch still succeeds. Up to 50 refs per call. Example: refs=["kalshi:KXFED-25JUN-H", "polymarket:fed-cut-2026"] → {quotes: [{platform, ident, probability, volume, fetched_at, age_seconds, error}], count, truncated}.

• foresea_check_runwrite actionFree

  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), or the full report once it is. Do not call this speculatively; only use the client_run_key a prior foresea_analyze_market call actually gave you. Example: client_run_key="a1b2c3..." → {status:"running", id:"agent_run_..."} or the full report once complete.

• foresea_debate_marketFree

  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_edge_boardFree

  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 paper-trading competition?", "What's the strongest edge today?", "Are these edges statistically significant?". Returns open markets ranked by model-vs-market disagreement, each with Buy YES/NO direction, implied odds, whether the edge is historically significant, and a multi-model comparison.

• foresea_exchange_statusFree

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

• foresea_feed_latestFree

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

• foresea_forecastFree

  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…", "Should I bet on…". Returns a calibrated YES/NO probability (or numeric/date range) with written rationale and supporting news evidence. If you also have a market price (market_probability) or URL (market_url), pass it to get the model-vs-market edge — how mispriced the market is. Example: question="Will the Fed cut rates by March 2026?", market_probability=0.4 → {predicted_answer:"No", confidence:0.62, rationale, evidence_sources, market_analysis:{model_probability:0.54, edge:+0.14, stance:"model_above_market"}} Handles: binary YES/NO, multiple-choice, numeric ranges, and date questions.

• foresea_live_dataFree

  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_market_leaderboardFree

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

• foresea_market_tagsFree

  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 slice that is ordered neither alphabetically nor by market activity. So absence here does not mean a tag is unused, presence does not mean it is active, and some entries are one-off or misspelled. Treat it as a vocabulary sample, not a classification the markets are organised by.

• foresea_optimize_portfolioFree

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

• foresea_orderbookFree

  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_polymarket_metaFree

  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 holds, not the events themselves -- fetch a series by slug for those. 'sports' lists every league with the ids that link it to other tools, not league artwork or homepages. 'comments' gives the comment, its author address and its reaction count, not the commenters' profiles or individual reactions.

• foresea_price_historyFree

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

• foresea_recent_tradesFree

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

• foresea_scan_marketsFree

  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 edge today?", "Scan Polymarket for opportunities". Returns markets ranked by model-vs-market disagreement, each with model probability, market price, and edge. For a specific market, use foresea_analyze_market instead. Example: platform="kalshi", min_edge=0.1 → [{question, market_probability, model_probability, edge, market_url}].

• foresea_track_recordFree

  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 the Brier score?". Returns accuracy, Brier score, calibration (ECE), and skill-vs-market broken down by time horizon.

• foresea_venue_dataFree

  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_weather_forecastFree

  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 probability calculations for weather prediction markets.

• foresea_weather_radarFree

  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 ensembles, calibrated with station microclimate bias profiles. Returns ranked mispricings, strike bracket probabilities, and model-vs-market edge.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 566ms20/20
• Tool poisoning21 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
• Maintenancelast push 0 days ago15/15
• Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10

Safety score

80/100

higher than 64% of 915 Security servers

Tools

21

the typical Security server has 6

Tools that change things

5%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Security server answers 100%

Response time

388 ms

faster than 28% of 547 Security servers

Foresea Forecasting: common questions

Is Foresea Forecasting MCP server safe?

Mostly: it is graded B (80/100). Read the Foresea Forecasting safety report

How do I install Foresea Forecasting?

It runs remotely at foresea.ink. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Foresea Forecasting need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Foresea Forecasting maintained?

The last commit was 38 days ago (2026-09-27). The latest release is v1.0.0.

Is Foresea Forecasting up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Foresea Forecasting?

Servers from other publishers that do the same job: Kalshi Prediction Markets MCP server, PyMemoryEditor MCP server and Autopilot Jobhunt MCP server.

How does Foresea Forecasting compare with other Security MCP servers?

safety score 80/100 (higher than 64% of 915 Security servers); tools 21 (the typical Security server has 6); tools that change things 5% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.