MistTrack MCP
MCP server from SlowMist exposing MistTrack address risk scoring and fund-flow tracing to AI agents.
- Sato Score70
- ChainsEthereum, Bitcoin +3
MistTrack MCP is an open-source security tool by SlowMist on Ethereum, Bitcoin, Polygon and other chains, with last code activity on 2026-04-28 (Quiet). Sato Score 70/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →
See how to install MistTrack MCP →Last commit Apr 28, 2026 · ★ 39
Listed from misttrack.io on 2026-07-19. Install: reproduced by Sato Hub on 2026-07-21. Evidence →
Next step
Watch MistTrack MCP
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on slowmist/misttrackmcp before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
MistTrack MCP integrates SlowMist's MistTrack AML/tracing platform with MCP-compatible AI clients, exposing tools for address risk scoring, transaction tracing, and fund-flow visualization across 19 blockchains. An agent builder uses it to screen wallet addresses against a large labeled-address database and sanction lists before interacting with a counterparty, or to trace suspicious fund flows during an investigation.
Sato Score
70/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 18/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 15/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v1.0.7 · as of 2026-09-29- Does it take your key?
- No key read found
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from misttrack.io on 2026-07-19. Install: reproduced by Sato Hub on 2026-07-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Ethereum, Bitcoin, Polygon, Solana, Multichain | self-reported | docs.misttrack.io | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | misttrack.io | as of 2026-10-21 |
| Recent activity | last commit 2026-04-28 | observed | github.com/slowmist/MistTrackMCP | 2026-10-21 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/slowmist/MistTrackMCP | 2026-07-21 |
| Website answers | answered (HTTP 200) | observed | misttrack.io | 2026-10-21 |
| Daily check record | 90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-09-29 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-09-29 |
| Built by | SlowMistconfidence 0.85 | self-reported | misttrack.io | as of 2026-10-06 |
| Deploys as | npx, npm global install, local developmentconfidence 0.80 | self-reported | github.com/slowmist/MistTrackMCP | as of 2026-10-06 |
| Works with | Claude Desktop, MistTrack OpenAPIconfidence 0.85 | self-reported | github.com/slowmist/MistTrackMCP | as of 2026-10-06 |
| Sato Score | 70/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-21 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — reproduced in a container Jul 21, 2026
Runtime: Node.js >=18 (npm package "misttrack")
npx -y misttrack@latest --key YOUR_MISTTRACK_API_KEY
npm install -g misttrack && misttrack --key YOUR_MISTTRACK_API_KEY
export MISTTRACK_API_KEY=YOUR_MISTTRACK_API_KEY && npx -y misttrack@latest
{"mcpServers": {"misttrack": {"command": "npx", "args": ["-y", "misttrack@latest", "--key", "YOUR_MISTTRACK_API_KEY"]}}}You supply: MISTTRACK_API_KEY — MistTrack OpenAPI key from https://dashboard.misttrack.io/apikeys, requires a MistTrack plan with OpenAPI access; not a private key, no custody risk
claude mcp add satohub-misttrack-mcp -- npx -y misttrack@latest --key YOUR_MISTTRACK_API_KEY
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-07-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-21, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Ethereum, Bitcoin, Polygon, Solana, Multichain
- Agent types
- MCP server
- Open source
- Yes
- Pricing
- Free tier; paid Premium/enterprise KYT plans
- Deploys as
- npx, npm global install, local development
- Works with
- Claude Desktop, MistTrack OpenAPI
- Last checked
- 2026-10-21
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where MistTrack MCP fits
Related concepts: What Are Onchain Agents?, Onchain Agents vs Offchain Agents
Listing History
Recorded changes to MistTrack MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 6, 2026Auto-enriched: supported integrations, deployment options, creator name, has pricing
- Oct 6, 2026Sato Score tier: Medium → HighScore 63 → 70.
- Sep 26, 2026Edited: entity class, resource type
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 21, 2026Verified: deploy spec
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about MistTrack MCP
- Is MistTrack MCP open source?
- Yes. MistTrack MCP is open source under the Unknown license; the repository is https://github.com/slowmist/MistTrackMCP. Checked as of 2026-10-21.
- Which chains does MistTrack MCP support?
- MistTrack MCP lists support for Ethereum, Bitcoin, Polygon, Solana, Multichain as of 2026-10-21.
- Is MistTrack MCP still maintained?
- The most recent code activity Sato Hub observed was on 2026-04-28 (last commit 2026-04-28), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run MistTrack MCP?
- Node.js >=18 (npm package "misttrack"). Install: npx -y misttrack@latest --key YOUR_MISTTRACK_API_KEY && npm install -g misttrack && misttrack --key YOUR_MISTTRACK_API_KEY && export MISTTRACK_API_KEY=YOUR_MISTTRACK_API_KEY && npx -y misttrack@latest. Entry: {"mcpServers": {"misttrack": {"command": "npx", "args": ["-y", "misttrack@latest", "--key", "YOUR_MISTTRACK_API_KEY"]}}}. Sato Hub reproduced this install in a container on 2026-07-21. It runs as an MCP server (npx -y misttrack@latest --key YOUR_MISTTRACK_API_KEY (stdio)).
- Is MistTrack MCP verified on Sato Hub?
- Sato Hub holds one earned check for MistTrack MCP: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 70 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "MistTrack MCP — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/misttrack-mcpData last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.