# BTC DCA Engine (remote · btcdcaengine.com)

Historical dollar-cost-averaging simulator for Bitcoin and other assets.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `btcdcaengine.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-btcdcaengine-btc-dca-engine/btcdcaengine.md), [page](https://verifymcp.io/servers/com-btcdcaengine-btc-dca-engine/btcdcaengine)

## Channel facts

- Endpoint: `https://btcdcaengine.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 646 tokens (~107/item across 6 items; 4 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-btcdcaengine-btc-dca-engine 'https://btcdcaengine.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-btcdcaengine-btc-dca-engine": {
      "url": "https://btcdcaengine.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-btcdcaengine-btc-dca-engine": {
      "type": "http",
      "url": "https://btcdcaengine.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-btcdcaengine-btc-dca-engine]
url = "https://btcdcaengine.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-btcdcaengine-btc-dca-engine": {
      "type": "remote",
      "url": "https://btcdcaengine.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-btcdcaengine-btc-dca-engine --url 'https://btcdcaengine.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-btcdcaengine-btc-dca-engine:
    url: "https://btcdcaengine.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-btcdcaengine-btc-dca-engine": {
      "Transport": "http",
      "Url": "https://btcdcaengine.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-btcdcaengine-btc-dca-engine -t streamable-http -u 'https://btcdcaengine.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-btcdcaengine-btc-dca-engine": {
      "type": "http",
      "url": "https://btcdcaengine.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 73, +8)

- [security improvement] Authorization: unverified → partial
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “compare_plans” reworded the description of “settings”
- [cosmetic] “run_dca” reworded the description of “settings”

### 2026-09-17 (score 65)

First indexed and scored.

## MCP tools (4)

### `list_assets` (~35 tokens)

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.

### `data_status` (~22 tokens)

Data status

The vintage of the loaded price data and how often it refreshes.

### `run_dca` (~317 tokens)

Run a DCA plan

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.

Input parameters:

- `amount` (number, required): 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, required): 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, required): 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.

### `compare_plans` (~167 tokens)

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.

Input parameters:

- `as_of` (string)
- `include` (object)
- `plans` (array, required): 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…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-btcdcaengine-btc-dca-engine/btcdcaengine#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 65

## Common questions

### 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 74 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://btcdcaengine.com/mcp
- Website: https://btcdcaengine.com/docs?article=agent_access
- Changelog RSS feed: https://verifymcp.io/servers/com-btcdcaengine-btc-dca-engine/btcdcaengine.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-btcdcaengine-btc-dca-engine/btcdcaengine.json
- HTML version of this page: https://verifymcp.io/servers/com-btcdcaengine-btc-dca-engine/btcdcaengine