Sato Hub
MCP

CryptoQuant MCP

Official CryptoQuant MCP server exposing on-chain metrics like MVRV, SOPR, and exchange flows to agents.

  • Sato Score75
  • ChainsMultichain
UnknownSelf-ReportedActive · 9d ago

CryptoQuant MCP is an open-source MCP server by CryptoQuant, with last code activity on 2026-10-06 (Active). Latest release on 2026-10-02. Sato Score 75/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install CryptoQuant MCP →

Last commit Oct 6, 2026 · Last release Oct 2, 2026 (v1.0.0) · ★ 7

Listed from cryptoquant.com on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21. Evidence →

Next step

Watch CryptoQuant 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/mcp
Run Sato Hub Preflight on cryptoquantofficial/cryptoquant-mcp before I use it.
Full setup: Claude Code, Cursor, others →

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

CryptoQuant's official MCP server (npm package cryptoquant-mcp) lets agents query on-chain analytics in natural language — MVRV, SOPR, exchange flows, funding rates, and whale-activity tracking across BTC, ETH, major alts, stablecoins, ERC20 tokens, TRX, and XRP.

Sato Score

75/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
17/20
Interface verifiability
8/10
Docs & demo
0/10
Listing transparency & provenance
12/15
Independent verification
3/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

Sato Check

v1.0.0 · as of 2026-10-02
Does it take your key?
No key read found
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

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 cryptoquant.com on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reportedcryptoquant.comas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedcryptoquant.comas of 2026-10-15
Recent activitylast release 2026-10-02 · last commit 2026-10-06observedgithub.com/CryptoQuantOfficial/cryptoquant-mcp2026-10-15
Install worksreproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour✓ reproducedgithub.com/CryptoQuantOfficial/cryptoquant-mcp2026-07-21
Website answersanswered, but declined our check (HTTP 403)observedcryptoquant.com2026-10-15
Daily check record44 of 44 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-10-02
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-10-02
Deploys asnpmconfidence 0.85self-reportedgithub.com/CryptoQuantOfficial/cryptoquant-mcpas of 2026-07-14
Works withClaude Desktop, Claude Code, Cursorconfidence 0.85self-reportedgithub.com/CryptoQuantOfficial/cryptoquant-mcpas of 2026-07-14
Sato Score75/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

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

npx -y cryptoquant-mcp
npx -y cryptoquant-mcp (stdio); call initialize() with an API key to start a session

You supply: CryptoQuant API key

Add to CursorAdd to VS Code
claude mcp add satohub-cryptoquant-mcp -- npx -y cryptoquant-mcp

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-17

100%of 45 checks since 2026-09-01 succeeded
Currently responding for 45 days
Succeeded
45
Failed
46
Their error
0
Unattributed
46

State changed on 2026-09-01 (unclear → responding).

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. 46 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. The rate above leaves those checks out; the counts include them.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
75
as snapshotted that day · 29/30 days

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
Multichain
Agent types
MCP Server, Data Provider
Open source
Yes
Deploys as
npm
Works with
Claude Desktop, Claude Code, Cursor
Last checked
2026-10-15

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.

#on-chain-data#market-data#mcp-server#analytics
See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from CryptoQuant MCP, pulled from its GitHub and X.

Listing History

Recorded changes to CryptoQuant MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Oct 2, 2026
    Sato Score tier: Medium → High
    Score 57 → 72.
  2. Oct 2, 2026
    New release published
  3. Oct 2, 2026
    Active again — shipped after a quiet spell
  4. Jul 21, 2026
    Verified: deploy spec
  5. Jul 18, 2026
    Sato Hub began tracking this listing
  6. Jul 14, 2026
    Enriched: has pricing
  7. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  8. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about CryptoQuant MCP

Is CryptoQuant MCP open source?
Yes. CryptoQuant MCP is open source under the MIT license; the repository is https://github.com/CryptoQuantOfficial/cryptoquant-mcp. Checked as of 2026-10-15.
Which chains does CryptoQuant MCP support?
CryptoQuant MCP lists support for Multichain as of 2026-10-15.
Is CryptoQuant MCP still maintained?
The most recent code activity Sato Hub observed was on 2026-10-06 (last commit 2026-10-06, last release 2026-10-02), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run CryptoQuant MCP?
node. Install: npx -y cryptoquant-mcp. Entry: npx -y cryptoquant-mcp (stdio); call initialize() with an API key to start a session. Sato Hub reproduced this install in a container on 2026-07-21. It runs as an MCP server (npx -y cryptoquant-mcp).
Is CryptoQuant MCP verified on Sato Hub?
Sato Hub holds one earned check for CryptoQuant MCP: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 75 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "CryptoQuant MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/cryptoquant-mcp

Data last refreshed 2026-10-15; 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.