Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Deptho

PYPI · DEPTHO-MCP

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

Available components

−12 this week 58 Trust /100

Last scanned (15 hours ago)

Scores higher than 53% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 36 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • 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. View diagnostics → Unverified
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 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
What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Provenance in Provenance & TransparencyBuild 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.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • Repository

    Registry says
    https://github.com/jjinaustin/deptho-mcp
    Package shows
    jjinaustin/quantview-wip

    The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale. See the evidence →

Changelog

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.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 15 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

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 21 Nov 2026 · Analysed pypi/deptho-mcp@0.1.0

Provenance Repository mismatch

The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.

Result Repository mismatch
Ecosystem pypi
Reason Repository mismatch
Discovered via Registry attestation endpoint
Source repo jjinaustin/quantview-wip
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/jjinaustin/quantview-wip/.github/workflows/release-mcp.yml@refs/heads/main
Rekor log index 3695412343
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:243c32f3b274b2c0c7c8f35529c9edc62538b800e047194d69440a56962dc2f7

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 36 packages
Packages resolved 36
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~554 tokens

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 →

Tool Tokens
pro_replay ~85

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

NameTypeReqDescription
datasetstringyes–
fills_csv–––
orders_csvstringyes–

No output schema declared.

No examples provided.

pro_status ~27

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pro_sync ~91

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

NameTypeReqDescription
endstringyes–
startstringyes–
symbolstringyes–

No output schema declared.

No examples provided.

replay_orders ~168

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.

NameTypeReqDescription
fills_csv–––
orders_csvstringyes–
trades_filestringyes–

No output schema declared.

No examples provided.

tearsheet ~183

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

NameTypeReqDescription
bars_csvstringyes–
fee_bpsnumber––
funding_csv–––
report_html–––
slippage_bpsnumber––
titlestring––

No output schema declared.

No examples provided.

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.

pypi · deptho-mcp

# add to Claude Code
claude mcp add io-deptho-deptho-mcp -- uvx deptho-mcp
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.