Foresea Forecasting

● Active

ink.foresea/forecasting

Forecast future events and scan prediction-market edges.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "forecasting": {
      "url": "https://foresea.ink/mcp/"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http forecasting https://foresea.ink/mcp/
VS Code
code --add-mcp '{"name":"forecasting","type":"http","url":"https://foresea.ink/mcp/"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Data & Analytics
Version
1.0.0
Registry
active
Published
6/6/2026

Live check

checked Nov 19, 2026, 18:07 UTC
● Working151 msprotocol 2025-06-18v1.30.0promptsresourcestools

The endpoint answered the MCP handshake as "Foresea" and listed 28 tools. Answering since Nov 18, 2026.

Context cost ≈ 6.8k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 28 tools.

Tools (28)

tool list changed Nov 19, 2026, 18:07 UTC
  • foresea_forecast13 params

    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.

    Show parameters
    • questionstringrequired
    • descriptionstring
    • resolution_criteriastring
    • question_type
    • options
    • categories
    • variantstring
    • attach_evidenceboolean
    • evidence_top_kinteger
    • market_platform
    • market_url
    • market_outcome
    • market_probability
  • foresea_analyze_market13 params

    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}.

    Show parameters
    • question
    • platform
    • slug
    • market_id
    • ticker
    • market_probability
    • variantstring
    • evidence_top_kinteger
    • skills
    • builtin_skillsboolean
    • ground_in_recordboolean
    • tool_loopboolean
    • max_tool_stepsinteger
  • foresea_scan_markets5 params

    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}].

    Show parameters
    • platformstring
    • limitinteger
    • min_edgenumber
    • evidence_top_kinteger
    • query
  • foresea_batch_quotes1 param

    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}.

    Show parameters
    • refsarrayrequired
  • foresea_check_run1 param

    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.

    Show parameters
    • client_run_keystringrequired
  • foresea_track_record1 param

    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. Pass optional fields list (e.g. ['brier_score', 'accuracy', 'n_snapshots_resolved']) to reduce token usage.

    Show parameters
    • fields
  • foresea_edge_board4 params

    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. Supports cursor pagination, limit, min_edge threshold, and field masking.

    Show parameters
    • limitinteger
    • min_edgenumber
    • fields
    • cursorinteger
  • foresea_venue_data4 params

    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.

    Show parameters
    • platformstring
    • operationstring
    • parameters
    • body
  • foresea_exchange_status

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

  • foresea_orderbook2 params

    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.

    Show parameters
    • ticker_or_tokenstringrequired
    • platformstring
  • 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 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_price_history2 params

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

    Show parameters
    • ticker_or_marketstringrequired
    • series_tickerstring
  • foresea_live_data3 params

    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.

    Show parameters
    • event_tickerstring
    • data_typestring
    • milestone_idstring
  • foresea_polymarket_meta2 params

    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.

    Show parameters
    • targetstring
    • market_idstring
  • foresea_recent_trades3 params

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

    Show parameters
    • platformstring
    • ticker_or_tokenstring
    • limitinteger
  • foresea_market_leaderboard1 param

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

    Show parameters
    • limitinteger
  • foresea_debate_market4 params

    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.

    Show parameters
    • questionstringrequired
    • platformstring
    • market_probability
    • resolution_criteriastring
  • foresea_optimize_portfolio3 params

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

    Show parameters
    • bankroll_usdnumber
    • kelly_fractionnumber
    • min_edgenumber
  • foresea_feed_latest2 params

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

    Show parameters
    • limitinteger
    • min_edgenumber
  • foresea_weather_radar1 param

    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.

    Show parameters
    • target_date
  • foresea_weather_forecast2 params

    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.

    Show parameters
    • station_or_querystringrequired
    • target_date
  • foresea_batch_forecast6 params

    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.

    Show parameters
    • questions
    • items
    • concurrency_limitinteger
    • variantstring
    • attach_evidenceboolean
    • evidence_top_kinteger
  • foresea_crypto_edge2 params

    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 reliability, and realized paper equity curves.

    Show parameters
    • min_edgenumber
    • limitinteger
  • foresea_webhook_subscribe3 params

    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.

    Show parameters
    • urlstringrequired
    • events
    • min_edgenumber
  • foresea_trade_account_status

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

  • foresea_preview_order11 params

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

    Show parameters
    • platformstringrequired
    • actionstringrequired
    • outcomestringrequired
    • pricenumberrequired
    • quantitynumberrequired
    • order_typestring
    • ticker
    • slug
    • token_id
    • time_in_force
    • post_onlyboolean
  • foresea_place_order14 params

    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.

    Show parameters
    • platformstringrequired
    • actionstringrequired
    • outcomestringrequired
    • pricenumberrequired
    • quantitynumberrequired
    • confirmationstringrequired
    • executeboolean
    • order_typestring
    • ticker
    • slug
    • token_id
    • time_in_force
    • post_onlyboolean
    • client_order_id
  • foresea_cancel_order3 params

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

    Show parameters
    • order_idstringrequired
    • platformstring
    • ticker

Checked by Serverdex with a plain initialize + tools/list call to foresea.ink/mcp/, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Nov 18, 2026
License
MIT

Python

From the README

Foresea: Autonomous Prediction Market Intelligence & LLM Rationale Benchmark Foresea (foresea.ink) is an autonomous prediction market intelligence platform and empirical research framework. It combines real-time probability forecasting across Polymarket and Kalshi, statistical edge discovery, multi-model shadow trading tournaments, an autonomous 19-tool ReAct execution agent, and a public Model Context Protocol (MCP) server. The repository also serves as the artifact for research studying how explicit rationale instructions, evidence injection, and reasoning structures affect LLM forecasting behavior and calibration on Metaculus-style questions. 📑 Table of Contents • Live Platform & Web Views • Edge Board & Autonomous Shadow Trading Desk • 5-Minute Crypto Micro-Markets • Production Deployment & Infrastructure • Using the API & Endpoints • Agent: Automated Intelligence Layer & ReAct Tools • Model Context Protocol (MCP) Integration • Custom Integrations & Ecosystem Tools • Trading Execution & KMS Guardrails • Repository Contents & Prompt Variants • Foresea Autoresearch • Reproducing Core Outputs & SQL Analytics • Quality Checks & Development Live Platform & Web Views Deployed on Google Cloud Run with high-concurrency scaling, streaming responses, and continuous delivery: Core Web Applications & Routes • Market Desk (/): Real-time landing view with market radar, model-vs-market gap highlights, and interactive walkthroughs.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://foresea.ink/mcp/

Alternatives to Foresea Forecasting

Best Data & Analytics servers →

The most-starred Data & Analytics servers in the index, with their live-check result.

ServerStarsLast pushLive check
Metabase50,336Nov 2026Not an MCP endpoint
PostHog MCP Server40,870Nov 2026Needs sign-in
OpenMetadata15,781Nov 2026Not an MCP endpoint
Agent-Native Analytics7,707Nov 2026Needs sign-in
TradingMCP5,284Nov 2026Needs sign-in

Foresea Forecasting: questions people ask

Is Foresea Forecasting a remote or a local MCP server?
According to its entry in the official MCP registry, Foresea Forecasting ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Foresea Forecasting need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 19, 2026. Individual tools may still ask for a key when called.
Is Foresea Forecasting still maintained?
Active: the repository's last commit 2 days ago. Last push Nov 18, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
What tools does Foresea Forecasting expose?
28 tools as listed by the server itself during the live check, including foresea_forecast, foresea_analyze_market, foresea_scan_markets, foresea_batch_quotes, foresea_check_run. The full list with parameters is in the Live check section above.
How do I add Foresea Forecasting to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Data & Analytics →

Add the badge to your site

Show visitors that Foresea Forecasting is listed here — it’s also the link we check for a free listing.

Foresea Forecasting — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/ink-foresea-forecasting?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Foresea Forecasting — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Foresea Forecasting — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/ink-foresea-forecasting?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.