Foresea Forecasting
ink.foresea/forecastingVersion 1.0.0Forecast future events and scan prediction-market edges.
Status
Responds205 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:32 UTC
- Latency
- 205 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://foresea.ink/mcp/Responds205 msNo sign-in
Claude Code
claude mcp add --transport http forecasting https://foresea.ink/mcp/Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: forecasting
Remote MCP server URL: https://foresea.ink/mcp/Cursor
{
"mcpServers": {
"forecasting": {
"url": "https://foresea.ink/mcp/"
}
}
}VS Code
code --add-mcp '{"name":"forecasting","type":"http","url":"https://foresea.ink/mcp/"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
28 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
foresea_analyze_marketCall 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}. | Not declared | Not declared | Not declared | Not declared |
foresea_batch_forecastSubmit 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. | Not declared | Not declared | Not declared | Not declared |
foresea_batch_quotesCall 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}. | Not declared | Not declared | Not declared | Not declared |
foresea_cancel_orderCancel an active open order on Kalshi or Polymarket using its venue order ID. | Not declared | Not declared | Not declared | Not declared |
foresea_check_runCall 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. | Not declared | Not declared | Not declared | Not declared |
foresea_crypto_edgeScan 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. | Not declared | Not declared | Not declared | Not declared |
foresea_debate_marketConduct an adversarial multi-agent debate (Bull vs. Bear vs. Chief Risk Judge) to cross-examine evidence and isolate blind spots on a forecasting question. | Not declared | Not declared | Not declared | Not declared |
foresea_edge_boardCall 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. | Not declared | Not declared | Not declared | Not declared |
foresea_exchange_statusCall this to check Kalshi exchange operational status (trading active flag)
and operational hours/schedule. | Not declared | Not declared | Not declared | Not declared |
foresea_feed_latestFetch the real-time unified Foresea Alpha & Agent Feed, combining live prediction market edge signals, autonomous agent trades & theses, and leaderboard standings. | Not declared | Not declared | Not declared | Not declared |
foresea_forecastCall 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. | Not declared | Not declared | Not declared | Not declared |
foresea_live_dataCall 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. | Not declared | Not declared | Not declared | Not declared |
foresea_market_leaderboardCall this to fetch the top profitable prediction market trader leaderboard and rankings from Polymarket. | Not declared | Not declared | Not declared | Not declared |
foresea_market_tagsCall 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. | Not declared | Not declared | Not declared | Not declared |
foresea_optimize_portfolioCalculate optimal mathematical Fractional Kelly capital allocations and position sizes across live Grade A/B prediction market opportunities. | Not declared | Not declared | Not declared | Not declared |
foresea_orderbookCall 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. | Not declared | Not declared | Not declared | Not declared |
foresea_place_orderSubmit 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. | Not declared | Not declared | Not declared | Not declared |
foresea_polymarket_metaCall 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. | Not declared | Not declared | Not declared | Not declared |
foresea_preview_orderValidate, normalize, and simulate guardrail checks for a real Kalshi or
Polymarket order without submitting it to the exchange. | Not declared | Not declared | Not declared | Not declared |
foresea_price_historyCall this to retrieve historical price series or OHLC candlesticks for a
market (e.g. Kalshi ticker or Polymarket token/slug). | Not declared | Not declared | Not declared | Not declared |
foresea_recent_tradesCall this to fetch recent public executed trades / trade tape (prices, sizes, timestamps) on Kalshi or Polymarket. | Not declared | Not declared | Not declared | Not declared |
foresea_scan_marketsCall 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}]. | Not declared | Not declared | Not declared | Not declared |
foresea_track_recordCall 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. | Not declared | Not declared | Not declared | Not declared |
foresea_trade_account_statusCheck real prediction-market trading readiness, max order notional limits,
and venue configuration statuses for Kalshi and Polymarket. | Not declared | Not declared | Not declared | Not declared |
foresea_venue_dataRead 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. | Not declared | Not declared | Not declared | Not declared |
foresea_weather_forecastRetrieve 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. | Not declared | Not declared | Not declared | Not declared |
foresea_weather_radarScan 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. | Not declared | Not declared | Not declared | Not declared |
foresea_webhook_subscribeSubscribe 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. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Jun 6, 2026
- Updated
- Jun 6, 2026
- Categories (suggested)
- Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared