Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Backtesting engine client: indicators, strategy validation, backtests, signals and market data.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"backtestport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/backtestport",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add backtestport -- npx -y @reneturcios/backtestport mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"backtestport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/backtestport",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"backtestport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/backtestport",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, HotCodePush
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Backtest a trading strategy without standing up your own engine. backtestport is a small client for the Backtest360 hosted backtesting engine: you hand it a strategy document and it validates the document, runs the backtest, evaluates the latest signal, compares several strategies on the same data, and fetches the market and macroeconomic data the engine can work with — plus the indicator catalog, templates and reference data you need to write the strategy in the first place.
This is a backtesting client only. It has no live-trading, order-placement or account tools, and nothing it does moves money.
Responses come back exactly as the engine returned them: nothing is trimmed, renamed or summarised on the way through, apart from the output byte cap described below.
Four environment variables control the client:
BACKTEST360_API_KEY (required) — sent on every request as the X-API-Key header. When it is not set, every tool fails with BACKTEST360_API_KEY is not set before any request is made.BACKTEST360_ENGINE_URL (optional) — engine base URL. Defaults to https://api.backtest360.com.BACKTEST360_MCP_TIMEOUT (optional) — per-request timeout in seconds, default 300. A request that runs past it fails with backtest360 request timed out.BACKTEST360_MCP_MAX_OUTPUT_BYTES (optional) — response size cap in bytes, default 100000. A longer body is truncated to the cap and a final line {"truncated_by_mcp": true} is appended, so a huge equity curve cannot flood the caller.Two engine answers that look like failures are not:
{valid: false, errors: [...]} when the document has problems. That is a normal result — the errors are structured and locatable so you can fix the document.{accepted: false}. That is also a normal result.Actual failures are errors: HTTP 429 fails with backtest360 rate limited (HTTP 429); retry after when the engine sends a Retry-After header (without the suffix when it does not), any other non-2xx reply fails with backtest360 error: HTTP , and an unreachable engine fails with backtest360 unreachable.
Strategy arguments (strategy, and each item of strategies) accept either a JSON object or a JSON string, which is parsed before sending; a string that does not parse fails with strategy is not valid JSON.
Three arguments shape a backtest run:
response_detail — summary (default), stats or full: how much of the verdict comes back.max_series_points — cap on returned series length, default 500; it must be an integer of at least 2, checked locally before any request (max_series_points must be an integer >= 2).include — any of trades, equity_curve, monthly_returns, yearly_returns and signal_diagnostics, each adding its series to the verdict.Discovery and account:
engine_info — engine version, API contract, health.get_me — what the configured key can do: permission scopes, limits, current usage, capability flags.get_catalog — the reference catalogs (operators, execution modes, stop types, sizing methods, bar frequencies, metric sections); pass catalog to fetch just one.list_indicators — indicator discovery with per-indicator parameter schemas; search narrows the list.list_templates — predesigned strategy templates, listed compactly, or one in full when id is given.get_strategy_schema — the JSON Schema for strategy documents.Strategies and runs:
validate_strategy — check a strategy document without running it.run_backtest — run a backtest; symbol, start, end, the shaping arguments above, and data (inline bars as an object) are all optional.get_latest_signal — evaluate the most recent bar only; no P&L.compare_backtests — run several strategies on the same data, side by side.compute_stats — compute the metric set from an externally produced returns series.Market and macro data:
search_tickers / list_tickers — the fetchable symbol universe.get_data_range — available history and a bar-count estimate for a symbol.get_ticker_info — symbol identity and data coverage in a single call.get_quote — latest available price for a symbol.get_price_history — OHLCV history over a date range (start, end, frequency; with server-side data the engine fixes bars at 1d — the argument is accepted and forwarded).list_macro_series / get_macro_series — the macroeconomic series catalog, and one series' observations over an optional date range.The original project's README pins the 19 tools, the shaping-argument semantics, the four environment variables with their defaults, the X-API-Key header and the rule that validation results and engine rejections are data. The wire paths below are reconstructions, labelled as such: GET /engine/info, GET /me, GET /catalogs, GET /indicators, GET /templates[/{id}], GET /strategy/schema, POST /strategy/validate, POST /backtests, POST /signals/latest, POST /backtests/compare, POST /stats, GET /tickers/search, GET /tickers, GET /tickers/{symbol}/data-range, GET /tickers/{symbol}, GET /tickers/{symbol}/quote, GET /tickers/{symbol}/history, GET /macro, GET /macro/{series} — all under the configured base URL, with path segments and query values URL-encoded.
Each tool is a subcommand taking one JSON argument string:
npx @reneturcios/backtestport engine_info '{}'
npx @reneturcios/backtestport validate_strategy '{"strategy":{"name":"sma-cross","rules":[]}}' npx @reneturcios/backtestport run_backtest '{"strategy":{"name":"sma-cross"},"symbol":"AAPL","include":["equity_curve"]}' npx @reneturcios/backtestport get_quote '{"symbol":"AAPL"}' npx @reneturcios/backtestport --version
Output is the tool's result text (the upstream JSON on success). Exit codes: 0 on success, 1 on a runtime error (including a missing key, a validation failure or an upstream failure), 2 on a usage error.
npx -y @reneturcios/backtestport mcp
MCP client config:
{
"mcpServers": { "backtestport": { "command": "npx", "args": ["-y", "@reneturcios/backtestport", "mcp"], "env": { "BACKTEST360_API_KEY": " " } } } }
docker run -i ghcr.io/cloudcorprecords/backtestport
docker run --rm ghcr.io/cloudcorprecords/backtestport get_quote '{"symbol":"AAPL"}'
npm install
npm run build # tsc -> dist/ npm test # tsx --test test/*.test.ts (fake fetch only, no network) npm run dev # run the CLI from source
MIT — Copyright (c) 2026 Rene Turcios