BTC DCA Engine
REMOTE · BTCDCAENGINE.COM
Historical dollar-cost-averaging simulator for Bitcoin and other assets.
Available components
Last scanned (3 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 646 tokens (~107/item across 6 items; 4 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 57 to 77. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://btcdcaengine.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=btcdcaengine.com | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9ab92de818230e6a13f9378b4e8c7419 |
| SANs: btcdcaengine.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of btcdcaengine.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| btcdcaengine.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://btcdcaengine.com/mcp | Verified | 200 | |
| http (plaintext) | http://btcdcaengine.com/mcp | HTTPS enforced | 301 | https://btcdcaengine.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_plans Compare plans ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | – |
| include | object | – | – |
| plans | array | yes | The plans to compare: up to 2 anonymously or on a Free-account key, up to 5 with a signed-in Pro account or a Pro API key. |
| settings | object | – | Chart overlays carried into share_url, and the figures they add to each summary. Flags marked "Pro only" need a signed-in Pro account or a Pro API key; without one, the call returns an error naming t… |
No output schema declared.
No examples provided.
data_status Data status ~22
The vintage of the loaded price data and how often it refreshes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_assets List assets ~35
Assets this endpoint can simulate, with the date each series starts and ends. Call before composing a plan so start dates fall inside coverage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_dca Run a DCA plan ~317
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | USD per contribution, or the single amount for lump-sum. |
| as_of | string | – | Pin the answer to this data vintage so the share link keeps returning the same number. |
| asset | string | yes | Asset key from list_assets, e.g. "btc_daily", "Ethereum", "S&P 500". |
| end_date | string | – | Window end. Defaults to the last loaded close, never a relative "today". |
| frequency | string | – | Contribution cadence. Default "monthly". Quarterly is the coarsest offered: wider gaps behave like a few lump sums (see the knowledge base, "The gap between buys"). |
| include | object | – | – |
| last_buy_date | string | – | Stop buying here and hold to end_date. |
| settings | object | – | Chart overlays carried into share_url, and the figures they add to each summary. Flags marked "Pro only" need a signed-in Pro account or a Pro API key; without one, the call returns an error naming t… |
| start_date | string | yes | First scheduled contribution. |
| type | string | – | "dca" repeats on the schedule; "lump-sum" buys once at the start. Default "dca". |
| wait_periods | integer | – | Save this many scheduled contributions as cash before the first purchase. |
No output schema declared.
No examples provided.
How do I install the BTC DCA Engine MCP server?
BTC DCA Engine is a hosted endpoint at https://btcdcaengine.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · btcdcaengine.com
claude mcp add --transport http com-btcdcaengine-btc-dca-engine 'https://btcdcaengine.com/mcp'
What is the BTC DCA Engine MCP server?
BTC DCA Engine is an MCP server listed in the public MCP registry as com.btcdcaengine/btc-dca-engine. Historical dollar-cost-averaging simulator for Bitcoin and other assets. This page covers its hosted endpoint (https://btcdcaengine.com/mcp).
Is the BTC DCA Engine MCP server safe to use?
BTC DCA Engine scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BTC DCA Engine MCP server expose?
BTC DCA Engine exposes 4 tools: list_assets, data_status, run_dca, compare_plans. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.
Does the BTC DCA Engine MCP server require authentication?
No. We connected to BTC DCA Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BTC DCA Engine MCP server still maintained?
BTC DCA Engine is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.