
Hyperd Mcp
io.github.hyperd-aiPublished by GitHub account hyperd-aiv1.1.1Updated Oct 24, 2026
Pre-trade DeFi intelligence: 24 paid x402 tools incl. 6 synthesis verdicts, USDC on Base.
Overview
Paid DeFi intelligence MCP server: 24 x402 tools for token, wallet, protocol and risk data, paid per call in USDC on Base from a local wallet.
- What you can do
- Look up balances, token metadata, protocol TVL, gas estimates and DEX quotes
- Check token security scores, contract audits, wallet risk, sanctions and anomaly signals
- Assess yield options, liquidation risk, wallet P&L and behavioral wallet classification
- Get composed synthesis verdicts such as full wallet audits, token archetypes and threat briefs
- Summarize DAO governance proposals and translate Snapshot/Tally proposals into plain language
- Create, list and cancel prepaid liquidation watches, or batch several paid calls in one settlement
- When to use it
- Useful when an assistant needs on-chain due diligence before a trade or DeFi position: token and contract risk, wallet reputation, liquidation exposure, yield comparison or governance summaries. It suits users who accept small per-call USDC payments instead of a subscription.
- Requirements
- Runs locally over stdio via npx hyperd-mcp, so Node 20+ is needed. Requires a wallet holding USDC on Base and its private key in HYPERD_WALLET_PRIVATE_KEY (a BIP-39 mnemonic is also supported). Optional HYPERD_API_BASE and HYPERD_BASE_RPC overrides. Network access to api.hyperd.ai; a remote MCP-over-HTTPS endpoint exists as an alternative.
Installation
In SourceWeft
- Open Hyperd Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
hyperD MCP Server
Exposes 24 paid hyperD x402 tools — 17 data/risk endpoints, 6 premium synthesis verdicts ($0.30–$1.50), and a multi-call bundle — plus 3 free meta tools (and 3 watch tools when enabled) from api.hyperd.ai. Drop into Claude Desktop, Cursor, Cline, Zed, or any MCP-compatible client.
What it does
Each tool call:
- Sends a request to the corresponding
api.hyperd.aiendpoint - Receives an HTTP 402 with payment requirements
- Signs an EIP-3009 USDC transfer authorization with your wallet
- Retries with the payment header
- Returns the data to the AI assistant
You pay $0.005–$1.50 in USDC on Base per call — data/risk endpoints $0.005–$0.10, premium synthesis verdicts $0.30–$1.50. No subscription. No accounts.
Try it free
First 5 calls per IP per 24h are free — no wallet, no signup, no API key. Just curl:
Lifetime cap: 10 calls per IP. After that (or when daily quota is exhausted), the endpoint returns HTTP 402 — sign a small EIP-3009 USDC payment on Base via the Python SDK or TypeScript MCP server. The premium synthesis tier ($0.30+) always requires payment — it is not free-tier eligible.
/api/wallet/pnl has a tighter free-tier cap of 1 call/IP/day (heavy upstream).
What you need
- A wallet with at least $0.30 USDC on Base (the seed cost for trying every tool once is ~$0.62)
- The wallet's private key OR 12-word BIP-39 mnemonic
- Node 20+ installed
Install + configure
Step 1 — Generate or use an existing wallet
For testing, use a fresh wallet, not your main one. A simple way:
Send ~$1 of USDC on Base to the printed address.
Step 2 — Claude Desktop
Edit your Claude Desktop config (location: macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json):
Restart Claude Desktop. The hyperD tools appear in the conversation tool list.
Step 3 — Try it
Ask Claude in any conversation:
"What's the security score for USDC on Base? Use the hyperd.token.security tool."
Claude calls our endpoint, pays $0.05 from your wallet, returns the result. The whole flow takes ~2 seconds.
Cursor / Cline / Zed
Each MCP-compatible client has a similar config file. Same pattern: name the server hyperd, command is npx -y hyperd-mcp, set HYPERD_WALLET_PRIVATE_KEY env var.
For the full MCP client list and per-client config docs see https://modelcontextprotocol.io/clients.
Local-development install (without npm publish)
If you want to run from source instead of npx:
Then in your Claude Desktop config, point at the local build:
Available tools
Synthesis tier — composed verdicts (Haiku 4.5, v1.1.0)
Each synthesis tool fans out multiple sub-calls internally and returns a single verdict + inputs + methodology.version + coverage envelope, authored by Claude Haiku 4.5.
Full HTTP API docs: https://api.hyperd.ai/api/discover
Security
- Use a hot wallet, not your primary. The MCP server has the private key in process memory while it runs.
- Cap your spend by transferring only what you want to use. There's no built-in spending limit; the wallet's balance IS the limit.
- Don't commit your private key. The Claude Desktop config file is local; don't share it.
Configuration via mnemonic instead of private key
If you have a 12 or 24-word BIP-39 mnemonic instead of a raw key:
Derives at the standard Ethereum path m/44'/60'/0'/0/0.
Optional env vars
HYPERD_API_BASE— defaulthttps://api.hyperd.ai. Override for testnet or self-hosted.HYPERD_BASE_RPC— default public Base RPC. Override for higher rate limits.
Remote MCP-over-HTTPS (no install)
If you don't want to run the stdio server locally, hyperD's full tool catalog is also available as a remote MCP server:
Same 24 paid tools, same free-tier quota (5 calls/IP/day, 10 lifetime), same X-Payment auth model for paid calls after quota. No npm install, no per-IDE config — just a URL.
Useful when:
- You're deploying an agent to a serverless platform (Vercel, Lambda) and don't want to bundle the stdio process
- You're using an MCP-aware service that expects a remote URL (Smithery enterprise, hosted gateways)
- You want to test the API surface from the command line with
curlbefore committing to a local install
Server card: https://api.hyperd.ai/.well-known/mcp.json.
License
MIT — same as the parent repo.
Source: README.md at commit c12c2a2
Tools
0Version history
1- v1.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts