Sperax Crypto MCP
Official Sperax MCP for USDs/SPA protocol data: peg health, collateral, yield strategies, and vault risk on Arbitrum and BNB Chain.
- Sato Score74
- ChainsArbitrum, BNB Chain
Sperax Crypto MCP is an open-source MCP server by Sperax on Arbitrum and BNB Chain, with last code activity on 2026-09-20 (Active). Sato Score 74/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 Sperax Crypto MCP →Last commit Sep 20, 2026 · ★ 16
Listed from sperax.io on 2026-07-13. Install: not attempted. Evidence →
Next step
Watch Sperax Crypto 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 sperax/sperax-crypto-mcp 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
Sperax's open-source MCP server exposes protocol-specific tools for the Sperax ecosystem: USDs stablecoin peg health and collateral composition, SPA and veSPA data, Demeter farms, yield-strategy stats, and vault-risk workflows on Arbitrum and BNB Chain. An agent builder plugs it in to give a DeFi monitoring or research agent direct Sperax protocol telemetry without wiring the contracts and subgraphs by hand.
Sato Score
74/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 18/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 12/15
- Independent verification
- 3/10
Evidence — listed vs checked · what the words mean
Listed from sperax.io on 2026-07-13. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Arbitrum, BNB Chain | self-reported | github.com/Sperax/sperax-crypto-mcp | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | sperax.io | as of 2026-10-15 |
| Recent activity | last commit 2026-09-20 | observed | github.com/Sperax/sperax-crypto-mcp | 2026-10-15 |
| Install works | documented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_spec | self-reported | github.com/Sperax/sperax-crypto-mcp | as of 2026-09-14 |
| Website answers | answered (HTTP 307) | observed | sperax.io | 2026-10-15 |
| Daily check record | 90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| ERC-8004 registration | declared address not found in the registry | observed | — | 2026-10-15 |
| Deploys as | npx (stdio for Claude Desktop, HTTP for other integrations)confidence 0.80 | self-reported | github.com/Sperax/sperax-crypto-mcp | as of 2026-07-14 |
| Works with | Claude Desktop, Cursor, VS Codeconfidence 0.80 | self-reported | github.com/Sperax/sperax-crypto-mcp | as of 2026-07-14 |
| Sato Score | 74/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-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 — not run by us — no falsifiable install+entry probe from deploy_spec
Runtime: node
git clone https://github.com/Sperax/sperax-crypto-mcp cd sperax-crypto-mcp pnpm install pnpm build pnpm start (stdio) or pnpm start:http (HTTP)
You supply: Arbitrum/BNB Chain RPC URL (optional — falls back to public RPC)
MCP invocation: pnpm start (dist/index.js, stdio)
Read from the project’s own docs as of 2026-09-14. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- 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. 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. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-15, 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
- Arbitrum, BNB Chain
- Agent types
- MCP Server, Data Provider
- Open source
- Yes
- Deploys as
- npx (stdio for Claude Desktop, HTTP for other integrations)
- Works with
- Claude Desktop, Cursor, VS Code
- 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.
Where Sperax Crypto MCP fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to Sperax Crypto MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 20, 2026Sato Score tier: Medium → HighScore 64 → 74.
- Jul 21, 2026Edited: onchain address
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Auto-enriched: deployment options, supported integrations
- Jul 14, 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 Sperax Crypto MCP
- Is Sperax Crypto MCP open source?
- Yes. Sperax Crypto MCP is open source under the MIT license; the repository is https://github.com/Sperax/sperax-crypto-mcp. Checked as of 2026-10-15.
- Which chains does Sperax Crypto MCP support?
- Sperax Crypto MCP lists support for Arbitrum, BNB Chain as of 2026-10-15.
- Is Sperax Crypto MCP still maintained?
- The most recent code activity Sato Hub observed was on 2026-09-20 (last commit 2026-09-20), 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 Sperax Crypto MCP?
- node. Install: git clone https://github.com/Sperax/sperax-crypto-mcp && cd sperax-crypto-mcp && pnpm install && pnpm build. Entry: pnpm start (stdio) or pnpm start:http (HTTP). This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (pnpm start (dist/index.js, stdio)).
- Is Sperax Crypto MCP verified on Sato Hub?
- No independent verification is on record for Sperax Crypto MCP; its verification status is "Self-Reported" and its Sato Score is 74 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Sperax Crypto MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/sperax-crypto-mcpData 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.