Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Forecast future events and scan prediction-market edges.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://foresea.ink/mcp/在终端中运行这条命令
claude mcp add --transport http forecasting https://foresea.ink/mcp/粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"forecasting": {
"url": "https://foresea.ink/mcp/"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"forecasting": {
"type": "http",
"url": "https://foresea.ink/mcp/"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://foresea.ink/mcp/菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
发布者(foresea.ink)不是仓库所有者(pareelamre);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, sync. labs
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
只显示了开头部分;其余内容请在仓库中阅读