Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Forecast future events and scan prediction-market edges.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://foresea.ink/mcp/Run this in your terminal
claude mcp add --transport http forecasting https://foresea.ink/mcp/Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"forecasting": {
"url": "https://foresea.ink/mcp/"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"forecasting": {
"type": "http",
"url": "https://foresea.ink/mcp/"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://foresea.ink/mcp/Menu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The publisher (foresea.ink) is not the repo owner (pareelamre); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Tools MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
Deployed on Google Cloud Run with high-concurrency scaling, streaming responses, and continuous delivery:
https://foresea.ink
# Health check
curl https://foresea.ink/health
curl -X POST https://foresea.ink/predict \ -H "Content-Type: application/json" \ -d '{ "question": "Will X happen by date Y?", "question_type": "binary", "description": "Context here.", "news_articles": [], "attach_evidence": true, "evidence_top_k": 5, "market_platform": "Polymarket", "market_probability": 0.42, "variant": "variant0_neutral_baseline" }'
When attach_evidence is true and no news_articles are supplied, /predict fetches and ranks current news evidence from GDELT, Google News RSS, and Stooq by default, injects it into the model prompt, and returns the selected evidence_articles with the forecast. Supplying news_articles skips automatic retrieval and uses the caller-provided evidence.
The response includes both the forecast and the evidence used by the model:
{
"question_type": "binary", "predicted_answer": "Yes", "confidence": 0.86, "options": [], "range_forecast": null, "rationale": "Model-generated explanation for the forecast.", "model_rationale": "Model-generated explanation for the forecast.", "variant": "variant0_neutral_baseline", "model_key": "gpt-oss-120b", "evidence_sources": [ { "source": "Reuters", "title": "Article headline", "url": "https://example.com/article", "publish_date": "2026-05-29T00:00:00Z", "relevance_score": 0.82 } ], "evidence_articles": [ { "title": "Article headline", "summary": "Cleaned article summary.", "source": "Reuters", "url": "https://example.com/article", "publish_date": "2026-05-29T00:00:00Z", "relevance_score": 0.82, "search_query": "query used for retrieval" } ], "evidence_error": null, "market_analysis": { "platform": "Polymarket", "market_url": "https://example.com/market", "outcome": "Yes", "market_probability": 0.42, "model_probability": 0.86, "edge": 0.44, "stance": "model_above_market", "summary": "Foresea is 44 percentage points above the market on Yes." } }
Use evidence_sources when a client only needs the source list and links. Use evidence_articles when a client needs the article-level details that were attached to the model prompt. rationale and model_rationale are generated by gpt-oss-120b and explain why the model chose its answer and confidence. When market_probability is supplied, market_analysis is computed deterministically from the model probability and the market-implied probability.
Foresea continuously evaluates state-of-the-art LLMs against real-world prediction markets, tracking statistical edge, calibration accuracy, and shadow portfolio performance across three dedicated views:
/edge or /edge/markets)buy_yes, buy_no, hold).static/track_record_live.json, calculating Brier scores, Expected Calibration Error (ECE), and lead-time skill once markets resolve./edge/mtm)/edge/agentic)gemma-4-26b-a4b-it)qwen3-8-27b)gpt-oss-120b)glm-5-3) & GLM 5.3 Flash (glm-5-3-flash)deepseek-v4-flash)minimax-m3)llama-3.3-70b-instruct)crowd-follow (no-LLM consensus control)The local crypto micro-market model in src/analyzing_llm_rationale/crypto_5m.py is built for 5-minute UP/DOWN markets where the goal is profitable selective trading, not constant action. It combines:
Each forecast returns predicted_outcome, probability_up, component_probabilities, model-vs-market edge, and a fee-aware strategy. The strategy only recommends a trade when net expected value clears fees and the configured no-trade threshold.
.venv/bin/python scripts/crypto_5m_backtest.py \
--benchmark \ --symbols BTC,ETH,SOL \ --days 1 \ --max-candles 1600 \ --lookback-minutes 60 \ --horizon-minutes 5 \ --market-probability 0.50 \ --fee-bps 2 \ --ml-modes fixed,adaptive \ --edge-thresholds 0,0.01,0.03,0.05,0.08 \ --selection-fraction 0.6 \ --folds 4 \ --training-window 120 \ --max-rows 80 \ --benchmark-log data/crypto_5m_benchmark_runs.jsonl
Use fold_aggregate and evidence_quality before risking capital. If selection is unstable or holdout PnL is weak, the correct profitable action is to abstain. --benchmark-log appends a compact JSONL record for tracking whether the selected threshold and model mode keep working across benchmark runs. Resolve completed markets against Binance candles:
.venv/bin/python scripts/crypto_5m_backtest.py \
--resolve \ --symbol BTCUSDT \ --target-price 62400.52 \ --start-time-ms 1780000000000 \ --horizon-minutes 5 \ --predicted-outcome down
The resolver returns pending before expiry and resolved afterward with actual_outcome, resolved_price, and prediction_correct.
Record and resolve paper signals over time:
.venv/bin/python scripts/crypto_5m_backtest.py \
--paper-signal \ --symbol BTCUSDT \ --market-probability 0.50 \ --fee-bps 2 \ --signal-log data/crypto_5m_signal_log.jsonl
.venv/bin/python scripts/crypto_5m_backtest.py \ --resolve-signal-log \ --signal-log data/crypto_5m_signal_log.jsonl
.venv/bin/python scripts/crypto_5m_backtest.py \ --signal-summary \ --signal-log data/crypto_5m_signal_log.jsonl \ --min-resolved-trades 200 \ --min-total-pnl 0 \ --min-hit-rate 0.53
.venv/bin/python scripts/crypto_5m_backtest.py \ --paper-loop \ --symbols BTC,ETH,SOL \ --iterations 12 \ --sleep-seconds 60 \ --market-probability 0.50 \ --fee-bps 2 \ --signal-log data/crypto_5m_signal_log.jsonl
The signal log is the running dataset for model improvement: each record stores the forecast, recommendation, later actual_outcome, correctness, and pnl_per_contract for actual buy_up/buy_down paper trades. Use --signal-summary to audit whether resolved paper trades are positive after fees; trade_ready stays false until the configured trade count, PnL, and hit rate thresholds are met. Use --dry-run with --paper-loop to preview signals without writing the log.
Production is served from the custom domain:
https://foresea.ink
The Cloud Run service name, project ID, and region are set at deploy time
Only the beginning is shown; read the rest in the repo