Skip to main content

deptho-mcp

An MCP server that gives coding assistants (Claude Code, Claude Desktop, Cursor and others) Deptho's backtest checks: replay a backtest's market orders against the trades that followed them, and write a tearsheet that splits returns into fees, funding and slippage. It runs on your machine over stdio, reads and writes local files, and sends nothing anywhere.

Tools

tool does
replay_orders orders CSV + trades file → fills CSV and a slippage summary (mean, median, p90, p99 bps)
tearsheet bars CSV (time, price, position) → self-contained HTML report, its path and headline numbers
pro_status whether Deptho Pro is installed and licensed here
pro_sync Deptho Pro: download Binance USD-M days from the public archive into a local memory-mapped dataset
pro_replay Deptho Pro: replay an orders CSV against that dataset

Orders CSV: time (ISO 8601 or epoch), side (+1/-1 or buy/sell), qty (base units, e.g. BTC). Trades file: a Binance archive aggTrades file (.zip or .csv) or a Tardis.dev trades file (.csv or .csv.gz) covering the orders' period.

Fills are modeled from trade prints: each order fills at the VWAP of the same-side trades after it until its size is covered. Order book depth and queue position are not modeled.

Install

pip install deptho-mcp

Use a virtual environment if you like; then point your assistant at that environment's deptho-mcp (which deptho-mcp prints the full path). For the Pro tools, install Deptho Pro into the same environment with your license key.

Claude Code

claude mcp add deptho -- deptho-mcp

Claude Desktop

Settings → Developer → Edit Config, then add to claude_desktop_config.json:

{
  "mcpServers": {
    "deptho": { "command": "/full/path/to/deptho-mcp" }
  }
}

Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "deptho": { "command": "/full/path/to/deptho-mcp" }
  }
}

Then ask, for example: "Replay orders.csv against BTCUSDT-aggTrades-2026-09-30.zip and tell me the p90 slippage."

Privacy

Every tool works on local files. Nothing is sent to Deptho. The only download is pro_sync, which fetches Binance's public archive (data.binance.vision) when you ask it to.

License: Apache-2.0. Market data comes from Binance's public archive or from files you supply; Deptho is not affiliated with Binance or Tardis.dev.

Metadata

Release files for deptho-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for deptho-mcp 0.1.0
File Size Uploaded Provenance Actions
deptho_mcp-0.1.0.tar.gz 12.8 kB With provenance Details for deptho_mcp-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for deptho-mcp 0.1.0
File Interpreter ABI Platform Actions
deptho_mcp-0.1.0-py3-none-any.whl Python 3 none any Details for deptho_mcp-0.1.0-py3-none-any.whl

Total release size: 23.7 kB

Release files / deptho_mcp-0.1.0.tar.gz

Download URL deptho_mcp-0.1.0.tar.gz
Size 12.8 kB
Tags Source
SHA-256 checksum
How to use checksums
243c32f3b274b2c0c7c8f35529c9edc62538b800e047194d69440a56962dc2f7
BLAKE2b-256 checksum
How to use checksums
15b05779ec55f6a1f7117a6ecca974ddabedebf6667a7ed79d79e35a3dfba56f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.

Transparency log

Release files / deptho_mcp-0.1.0-py3-none-any.whl

Download URL deptho_mcp-0.1.0-py3-none-any.whl
Size 10.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
25ee4807d33f4748311066bb70a57c893ef2137c589f9194de5ede09869d09dc
BLAKE2b-256 checksum
How to use checksums
27694a8fb3678695fff9905cf7d0b25c0892e3537fedd0594b07fd7b6f032847
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.

Transparency log

Security for deptho-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for deptho_mcp-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page