BTC DCA Engine is an MCP server with 4 tools an agent can call, among them compare_plans, data_status, list_assets. It answers at https://btcdcaengine.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 17 September 2026; the last check, on 24 October 2026, succeeded.
Historical dollar-cost-averaging simulator for Bitcoin and other assets.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
compare_plans | Run up to 5 plans over the same data and rank them by final value (2 without a signed-in Pro account or a Pro API key). Use to compare assets, cadences or start dates side by side. One share_url opens them all together. Inputs: plans, as_of, settings, include |
data_status | The vintage of the loaded price data and how often it refreshes. |
list_assets | Assets this endpoint can simulate, with the date each series starts and ends. Call before composing a plan so start dates fall inside coverage. |
run_dca | Simulate one dollar-cost-averaging plan against real historical closes. Returns totals, end-of-year checkpoints and a share_url that opens the same run in the app. Inputs: asset, type, amount, frequency, start_date, end_date |
Every block below points at https://btcdcaengine.com/mcp. Pick your client and copy.
claude mcp add --transport http btc-dca-engine https://btcdcaengine.com/mcp
{
"mcpServers": {
"btc-dca-engine": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://btcdcaengine.com/mcp"]
}
}
}{
"mcpServers": {
"btc-dca-engine": {
"url": "https://btcdcaengine.com/mcp"
}
}
}{
"servers": {
"btc-dca-engine": {
"type": "http",
"url": "https://btcdcaengine.com/mcp"
}
}
}{
"context_servers": {
"btc-dca-engine": {
"url": "https://btcdcaengine.com/mcp"
}
}
}{
"mcpServers": {
"btc-dca-engine": {
"serverUrl": "https://btcdcaengine.com/mcp"
}
}
}{
"mcpServers": {
"btc-dca-engine": {
"url": "https://btcdcaengine.com/mcp"
}
}
}name: BTC DCA Engine
version: 0.0.1
schema: v1
mcpServers:
- name: BTC DCA Engine
type: streamable-http
url: https://btcdcaengine.com/mcp{
"mcpServers": {
"btc-dca-engine": {
"httpUrl": "https://btcdcaengine.com/mcp"
}
}
}{
"mcpServers": {
"btc-dca-engine": {
"type": "http",
"url": "https://btcdcaengine.com/mcp"
}
}
}{
"mcpServers": {
"btc-dca-engine": {
"url": "https://btcdcaengine.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fbtcdcaengine.com%2Fmcp&type=streamable_http&id=btc-dca-engine&name=BTC%20DCA%20Engine
It answered our last check on 24 October 2026 in 362 ms. Over 4 checks since 17 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by btcdcaengine.com and served from btcdcaengine.com, the vendor's own domain: https://btcdcaengine.com/mcp.
4, as returned by the server's own tools/list on 24 September 2026: compare_plans, data_status, list_assets, run_dca.
It answered our last check on 24 October 2026 in 362 ms. Over 4 checks since 17 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://btcdcaengine.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.btcdcaengine. Endpoint host: btcdcaengine.com. ARD identifier: urn:air:com.btcdcaengine:mcp:btc-dca-engine.
First indexed 17 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.