Next free-source huntWe check for new free data every weekday.
FinancialMCP serverFirst audited Nov 13, 2026

BTC DCA Engine

Historical dollar-cost-averaging simulator for Bitcoin and other assets.The vendor's description, from its MCP Registry listing.

Passed public checksAudited Nov 13, 2026

Every public check ran and passed. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit

Does it work?
YesConnected in 490 ms.
Sign-up?
None neededIt answered without any account or key.
Can it change things?
No, read-onlyAll 4 tools say they only read.
Endpointhttps://btcdcaengine.com/mcp

Website Streamable HTTP · protocol 2025-11-25 · server version 1.4.0

What we checked, the evidence, and the tools it offers.

What we checked

Security

  • Passed: Connections are encrypted (HTTPS).

  • Passed: No hidden instructions found in tool text.

Safety labels

  • Passed: Every tool says whether it only reads or can change things.

Tools

  • Passed: 4 tools listed.

  • Passed: Every tool describes its inputs with a valid schema.

Protocol

  • Passed: The MCP handshake works (Streamable HTTP).

  • Passed: Protocol version 2025-11-25 (latest).

  • Passed: Unknown requests are refused.

Connection

  • Passed: The server responds.

Tools (4)

As the server describes them. The labels are the server's own: it says whether each tool only reads or can change things.

  • list_assetsAssets this endpoint can simulate, with the date each series starts and ends. Call before composing a plan so start dates fall inside coverage.Read-only
  • data_statusThe vintage of the loaded price data and how often it refreshes.Read-only
  • run_dcaSimulate 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.Read-only
  • compare_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). Use to compare assets, cadences or start dates side by side. One share_url open…Read-only

Audit history

  1. Nov 13Passed

What we sent

Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.

RequestAnswerTime
initializeHTTP 200490 ms
initializedHTTP 202474 ms
tools/listHTTP 200112 ms
resources/listHTTP 200107 ms
unknown-methodHTTP 20093 ms

Run this server, or disagree with the result?

Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.