Analytics
btcdcaengine.com
Simulates dollar-cost-averaging investment plans against historical price data and compares plan outcomes.
ENDPOINT 1
https://btcdcaengine.com/mcp
MCP server metadata
- Name
- btc-dca-engine
- Version
- 1.4.0
Historical dollar-cost-averaging simulator for Bitcoin and other assets. Every result carries a share_url that opens the same run in the web app, pinned to the data vintage it was computed against. Call list_assets first to see coverage windows. Results are historical arithmetic, not advice.
Known tools 4
list_assetsAssets this endpoint can simulate, with the date each series starts and ends.
Inferred read-onlycompare_plansRun 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).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.btc-dca-engine]
url = "https://btcdcaengine.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"btc-dca-engine": {
"type": "http",
"url": "https://btcdcaengine.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: btc-dca-engine
Remote MCP URL: https://btcdcaengine.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"btc-dca-engine": {
"url": "https://btcdcaengine.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"btc-dca-engine": {
"type": "http",
"url": "https://btcdcaengine.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "btc-dca-engine",
"transport": "streamable-http",
"url": "https://btcdcaengine.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.