mcpbeat

Foresea Forecasting MCP Server

ink.foresea/forecasting
answering

Foresea Forecasting is answering right now. Last checked 12 min ago. It exposes 5 tools. Last commit 4 Aug 2026.

Forecast future events and scan prediction-market edges.

Uptime history 40 hours of history · worst hour 75%
40 hours agonow
97.8%
Uptime 24h
89 of 91 checks
5
Tools
read from the server
360 ms
Response time
average over 24h
0
Stars
last commit 4 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add forecasting --transport http https://foresea.ink/mcp/
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "forecasting": {
      "url": "https://foresea.ink/mcp/"
    }
  }
}
~/.codex/config.toml
[mcp_servers.forecasting]
url = "https://foresea.ink/mcp/"
.cursor/mcp.json
{
  "mcpServers": {
    "forecasting": {
      "url": "https://foresea.ink/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "forecasting": {
      "url": "https://foresea.ink/mcp/"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

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

Endpoints

URLTransportStateLatencyChecked
https://foresea.ink/mcp/ streamable-http answering 264 ms 12 min ago

Foresea Forecasting — questions

Answers built from our own checks of this server.

What can Foresea Forecasting do?
It exposes 5 tools, read directly from the server on our last check. Among them: foresea_analyze_market, foresea_edge_board, foresea_forecast, foresea_scan_markets, foresea_track_record. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Foresea Forecasting working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 360 ms. The bar chart above shows every period we have measured.
How do I connect Foresea Forecasting?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Foresea Forecasting need an API key?
No. Foresea Forecasting completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Foresea Forecasting?
It answers our handshake in 360 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Foresea Forecasting open source?
Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.