# Deptho (pypi · deptho-mcp)

Replay a crypto backtest's orders against trades and write tearsheets, locally.

- Trust score: 58/100 (low)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `deptho-mcp`: 58/100 (this document), [markdown](https://verifymcp.io/servers/io-deptho-deptho-mcp/deptho-mcp.md), [page](https://verifymcp.io/servers/io-deptho-deptho-mcp/deptho-mcp)

## Channel facts

- Registry: `pypi`
- Package: `deptho-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 36 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 644 tokens (~128/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 5 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).

## Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This view is read from the stored diagnostics trace and is never an input to the score. Each row links to its evidence.

### Repository

- Registry says: `https://github.com/jjinaustin/deptho-mcp`
- Package shows: `jjinaustin/quantview-wip`
- What it means: The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.
- Evidence: https://verifymcp.io/servers/io-deptho-deptho-mcp/deptho-mcp#diagnostics-provenance

## Install

### How do I install the Deptho MCP server?

Deptho runs locally as a PyPI package, launched with uvx deptho-mcp. 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 io-deptho-deptho-mcp -- uvx deptho-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "io-deptho-deptho-mcp": {
      "command": "uvx",
      "args": [
        "deptho-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-deptho-deptho-mcp": {
      "command": "uvx",
      "args": [
        "deptho-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add io-deptho-deptho-mcp -- uvx deptho-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-deptho-deptho-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "deptho-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-deptho-deptho-mcp --command uvx --arg deptho-mcp
```

### Hermes

```yaml
mcp_servers:
  io-deptho-deptho-mcp:
    command: "uvx"
    args: ["deptho-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "io-deptho-deptho-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "deptho-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-deptho-deptho-mcp -t stdio -c uvx -a deptho-mcp
```

### Other

```json
{
  "mcpServers": {
    "io-deptho-deptho-mcp": {
      "command": "uvx",
      "args": [
        "deptho-mcp"
      ]
    }
  }
}
```

## 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-11-21 (score 58, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-20 (score 73, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-18 (score 57, +1)

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

### 2026-11-16 (score 56, +1)

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

### 2026-11-15 (score 55, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-14 (score 70, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-13 (score 54, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-12 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (5)

### `replay_orders` (~168 tokens)

Replay a backtest's market orders against the trades that followed them.

orders_csv: CSV with columns time (ISO or epoch), side (+1/-1 or buy/sell), qty (base units).
trades_file: Binance archive aggTrades file (.zip or .csv) or Tardis.dev trades file (.csv or .csv.gz)
covering the orders' period. Writes one row per filled order (side, qty, price, ref_price,
slippage_bps) to fills_csv (default: next to the orders, <name>.fills.csv) and returns a summary.
Slippage is in bps against the last trade before each order; positive = cost.

Input parameters:

- `fills_csv`
- `orders_csv` (string, required)
- `trades_file` (string, required)

### `tearsheet` (~183 tokens)

Write Deptho's HTML tearsheet for a strategy and return its path and headline numbers.

bars_csv: CSV with columns time, price (mark/close) and position (exposure as a fraction of equity,
1.0 = 1x long, decided at each bar's close; it earns from the next bar). funding_csv (optional):
time and funding_rate (positive = longs pay). fee_bps and slippage_bps: per unit of turnover; use the
slippage measured with replay_orders rather than a guess. Writes one self-contained HTML file
(default: next to bars_csv, <name>.report.html).

Input parameters:

- `bars_csv` (string, required)
- `fee_bps` (number)
- `funding_csv`
- `report_html`
- `slippage_bps` (number)
- `title` (string)

### `pro_status` (~27 tokens)

Whether Deptho Pro is installed and licensed here. pro_sync and pro_replay need it.

### `pro_sync` (~91 tokens)

(Deptho Pro) Download Binance USD-M daily trade files from Binance's public archive for start..end
(YYYY-MM-DD, inclusive) and append them to one local memory-mapped dataset, "<SYMBOL>-aggTrades".
Days already on disk aren't downloaded again. Returns the dataset name and size.

Input parameters:

- `end` (string, required)
- `start` (string, required)
- `symbol` (string, required)

### `pro_replay` (~85 tokens)

(Deptho Pro) Replay an orders CSV (time, side, qty) against a dataset made by pro_sync (the name it
returned, e.g. "BTCUSDT-aggTrades"), straight off the memory-mapped columns. Same output as replay_orders.

Input parameters:

- `dataset` (string, required)
- `fills_csv`
- `orders_csv` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/io-deptho-deptho-mcp/deptho-mcp#diagnostics

## Score history

- 2026-11-21: 58
- 2026-11-20: 73
- 2026-11-19: 57
- 2026-11-18: 57
- 2026-11-17: 56
- 2026-11-16: 56
- 2026-11-15: 55
- 2026-11-14: 70
- 2026-11-13: 54
- 2026-11-12: 69
- 2026-11-11: 54
- 2026-11-10: 68
- 2026-11-09: 47
- 2026-11-08: 67
- 2026-11-07: 67
- 2026-11-06: 51
- 2026-11-05: 66

## Common questions

### What is the Deptho MCP server?

Deptho is an MCP server listed in the public MCP registry as io.deptho/deptho-mcp. Replay a crypto backtest's orders against trades and write tearsheets, locally. This page covers its PyPI package (deptho-mcp).

### Is the Deptho MCP server safe to use?

Deptho scores 58 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 Deptho MCP server expose?

Deptho exposes 5 tools: replay_orders, tearsheet, pro_status, pro_sync, pro_replay. Their descriptions and schemas cost roughly 554 tokens of context every time the server is loaded.

### Is the Deptho MCP server still maintained?

Deptho is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Deptho MCP server under?

Deptho declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Deptho MCP server?

VerifyMCP ran 14 checks on Deptho, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Deptho: Malware scan and Provenance. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/deptho-mcp/
- Socket report: https://socket.dev/pypi/package/deptho-mcp
- Repository: https://github.com/jjinaustin/deptho-mcp
- Website: https://deptho.io/go/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-deptho-deptho-mcp/deptho-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-deptho-deptho-mcp/deptho-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-deptho-deptho-mcp/deptho-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-deptho-deptho-mcp/deptho-mcp
