Sato Hub
MCP

BlockBeats MCP

Official BlockBeats MCP: crypto newsflashes, articles, market metrics, ETF flows, and macro signals.

  • Sato Score41
  • ChainsMultichain
UnknownSelf-ReportedQuiet · 7mo ago

BlockBeats MCP is an open-source MCP server by BlockBeats, with last code activity on 2026-03-22 (Quiet). Sato Score 41/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 BlockBeats MCP →

Last commit Mar 22, 2026 · ★ 43

Listed from theblockbeats.info on 2026-07-13. Install: not attempted. Evidence →

Next step

Watch BlockBeats 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 blockbeatsofficial/blockbeats-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

BlockBeats, a Chinese-language crypto news outlet, publishes an official MCP server exposing its newsflashes, long-form articles, market metrics, ETF flow data, stablecoin stats, macro signals, and derivatives research. An agent builder plugs it in to give a research or trading agent a live crypto-news and market-context feed without scraping.

Sato Score

41/100· Medium

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

Maintenance & liveness
5/35
Code transparency
18/20
Interface verifiability
0/10
Docs & demo
6/10
Listing transparency & provenance
12/15
Independent verification
0/10

Sato Check

v1.0.4 · as of 2026-09-28
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 theblockbeats.info on 2026-07-13. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reportedgithub.com/BlockBeatsOfficial/blockbeats-MCPas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedtheblockbeats.infoas of 2026-10-15
Recent activitylast commit 2026-03-22observedgithub.com/BlockBeatsOfficial/blockbeats-MCP2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted by Sato Hubself-reportedgithub.com/BlockBeatsOfficial/blockbeats-MCPas of 2026-07-20
Website answersdid not answer our checkobservedtheblockbeats.info2026-10-15
Daily check record0 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-09-28
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-09-28
Deploys asnpm (global install)confidence 0.85self-reportedgithub.com/BlockBeatsOfficial/blockbeats-MCPas of 2026-07-14
Works withClaude Desktop, Cursorconfidence 0.85self-reportedgithub.com/BlockBeatsOfficial/blockbeats-MCPas of 2026-07-14
Sato Score41/100 (Medium)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 — as documented by the project, not run by us

Runtime: Node.js 18+

npm install -g blockbeats-mcp
npx -y blockbeats-mcp

You supply: BLOCKBEATS_API_KEY (obtained via application at theblockbeats.info)

Add to CursorAdd to VS Code
claude mcp add satohub-blockbeats-mcp -- npx -y blockbeats-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-20. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-17

0%of 45 checks since 2026-09-01 succeeded
Currently unreachable from our probe for 45 days
Succeeded
35
Failed
56
Their error
0
Unattributed
56

State changed on 2026-08-21 (responding → unclear), 2026-09-01 (unclear → unreachable from our probe).

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
fewer than 2 points—
7-day rolling; unattributable days are gaps · 0/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
41
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 (global install)
Works with
Claude Desktop, 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.

#mcp#news#market-data#research#blockbeats
See something inaccurate or outdated?Submit a correction →

Listing History

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

  1. Jul 20, 2026
    Edited: deploy spec
  2. Jul 18, 2026
    Sato Hub began tracking this listing
  3. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  4. Jul 14, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about BlockBeats MCP

Is BlockBeats MCP open source?
Yes. BlockBeats MCP is open source under the MIT license; the repository is https://github.com/BlockBeatsOfficial/blockbeats-MCP. Checked as of 2026-10-15.
Which chains does BlockBeats MCP support?
BlockBeats MCP lists support for Multichain as of 2026-10-15.
Is BlockBeats MCP still maintained?
The most recent code activity Sato Hub observed was on 2026-03-22 (last commit 2026-03-22), 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 BlockBeats MCP?
Node.js 18+. Install: npm install -g blockbeats-mcp. Entry: npx -y blockbeats-mcp. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (npx -y blockbeats-mcp).
Is BlockBeats MCP verified on Sato Hub?
No independent verification is on record for BlockBeats MCP; its verification status is "Self-Reported" and its Sato Score is 41 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "BlockBeats MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/blockbeats-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.