Crypto Pulse MCP server
Commit Nov 14, 2026Provides AI agents with aggregated crypto market data, including spot prices, sentiment, funding rates, and DeFi yields in a single plain-English summary.
Also known as midnight232/crypto-pulse-api, crypto-pulse-api
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.10.2
- Last commit
- Nov 14, 2026
- License
- MIT
What is Crypto Pulse MCP?
Crypto Pulse provides AI agents with aggregated crypto market data, including spot prices, sentiment, funding rates, and DeFi yields in a single plain-English summary.
Summary generated from the project's README
About Crypto Pulse MCP server
Automating crypto market analysis for AI agents is what Crypto Pulse enables by consolidating multiple data streams into a single request. Instead of chaining separate calls for spot prices, sentiment, funding rates, and DeFi yields, developers can use one tool to receive a plain-English summary and deterministic signals. This approach reduces both latency and costs compared to fetching data from individual sources like CoinGecko, alternative.me, Hyperliquid, or DefiLlama.
Users can connect via a remote HTTP MCP or a local stdio proxy. The service operates on a pay-per-request model gated by x402 USDC on the Solana blockchain, using Coinbase CDP as a facilitator on mainnet. Developers can test the integration for free using the devnet network or by utilizing the free sample tool which provides data that may be up to 15 minutes old. The server also hosts a Prediction Arena where bots can compete for daily and weekly USDC prizes by predicting the daily close of BTC, ETH, and SOL.
What you can do with it
- 1Consolidate market data fetchesAn AI agent can replace four separate data fetches with a single call to get spot prices, sentiment, funding, and yields.
- 2Generate natural language market briefsProvide users with a concise, human-readable summary of current crypto market conditions.
- 3Compete in price prediction contestsA developer can build a bot to predict the daily closing prices of Bitcoin, Ethereum, or Solana to win prizes.
- 4Monitor specific asset trendsRequest market data for a single specific ticker like BTC or SOL.
Written from the project's README. Every use case is checked against a quote from it.
How to install Crypto Pulse MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Crypto Pulse MCP in Claude Code
$ claude mcp add --transport http crypto-pulse-api https://cryptopulseapi.com/mcpInstall Crypto Pulse MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"crypto-pulse-api": {
"url": "https://cryptopulseapi.com/mcp"
}
}
}Install Crypto Pulse MCP in VS Code
.vscode/mcp.json
{
"servers": {
"crypto-pulse-api": {
"type": "http",
"url": "https://cryptopulseapi.com/mcp"
}
}
}Install Crypto Pulse MCP in VS Code CLI
$ code --add-mcp '{"name":"crypto-pulse-api","type":"http","url":"https://cryptopulseapi.com/mcp"}'Install Crypto Pulse MCP in Codex
$ codex mcp add crypto-pulse-api --url https://cryptopulseapi.com/mcpInstall Crypto Pulse MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.crypto-pulse-api] url = "https://cryptopulseapi.com/mcp"
Install Crypto Pulse MCP in Gemini CLI
$ gemini mcp add -s user --transport http crypto-pulse-api https://cryptopulseapi.com/mcpInstall Crypto Pulse MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"crypto-pulse-api": {
"url": "https://cryptopulseapi.com/mcp",
"type": "http"
}
}
}Configuration
PUBLIC_BASE_URL
| Name | Description | |
|---|---|---|
| PUBLIC_BASE_URL | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablemidnight232/crypto-pulse-api is public and reachablegithub.com/midnight232/crypto-pulse-api ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/midnight232/crypto-pulse-api ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 42 msPass
README
View on GitHubcrypto-pulse-api (Solana x402)
Pay-per-request crypto market pulse for AI agents. One call replaces four data fetches (spots + Fear & Greed + Hyperliquid funding + DefiLlama TVL/yields), returns a plain-English summary + signals, and is gated by x402 USDC on Solana.
Set
NETWORK=devnet(default locally) for free testing, orNETWORK=mainnetfor production.Live: https://cryptopulseapi.com (legacy alias still up: https://137-184-201-7.sslip.io) — source: https://github.com/midnight232/crypto-pulse-api — mainnet
payTo37CP6YemJJQ6sMu4Ue6C7pgC7BXkN6iCcCHVeZunvPod. Facilitator: Coinbase CDP (PayAI listing retained). See DEPLOY.md.Free Crypto Pulse Prediction Arena: bots predict the daily close (BTC, ETH, and SOL). Free entry (no wagering). Sponsor-funded prizes: $1 USDC daily / $10 USDC weekly, paid automatically on-chain while funded. From the 2026-11-13 close, prize eligibility requires at least one
GET /v1/pulsecall on the qualifying UTC day (X-Pulse-Client-Id= payout wallet). Optional referrals: sendref(the referrer's payout wallet) on a bot's firstPOST /v1/arena/predict. Disclosedofficial-*house bots are ineligible. Results: /arena/results.
What it returns
GET /v1/pulse (paid, $0.02 USDC) returns compact JSON:
- BTC / ETH / SOL / HYPE spot USD (CoinGecko, no API key)
- Crypto Fear & Greed (alternative.me)
- Hyperliquid perpetual funding for BTC / ETH / SOL / HYPE
- DefiLlama total TVL + a few high-TVL stablecoin yields
summary: one plain-English line derived from those fieldssignals: deterministic sentiment + funding bias flags
Each block includes source, fetchedAt, and graceful ok: false + error if a source fails. Live responses are cached in-memory for 60 seconds.
Also:
GET /v1/pulse/:asset— single ticker (BTC|ETH|SOL|HYPE),$0.02GET /v1/spots— spots only + summary,$0.005GET /v1/sample— free same shape as full pulse, may be up to 15 minutes old (10 req/min/IP)POST /mcp— Streamable HTTP MCP (get_market_samplefree; paid tools return x402 payment requirements + HTTP URLs; free arena tools)- Prediction Arena (free):
GET /arena,/arena/results,GET /v1/arena/rules,GET /v1/arena/round,POST /v1/arena/predict,GET /v1/arena/entry?wallet=,GET /v1/arena/referrals?wallet=,GET /v1/arena/leaderboard,GET /v1/arena/results/:roundId,GET /v1/arena/history,GET /v1/arena/house-bots,GET /v1/arena/prize-wallet— daily UTC close predictions (BTC/ETH/SOL). Free entry, no wagering. From the 2026-11-13 close, a bot is prize-eligible only if it made at least oneGET /v1/pulsethat qualifying UTC day withX-Pulse-Client-Id(or payer wallet) equal to its payout wallet. Ineligible bots are still scored and shown. Optionalrefon the first predict binds a referral ($0.005after 3 UTC days of pulse+predict;$0.01on the first paid pulse).official-*house bots are labeled and never prize-eligible. Prizes paid automatically on-chain from the public prize wallet while funded. - Free live pulse: 1×
GET /v1/pulseper client per UTC day withX-Crypto-Pulse-Free: 1+X-Pulse-Client-Id(bare GET still returns HTTP 402 for x402 discovery). Plus free staleGET /v1/sample.
Free discovery: GET /, GET /health, GET /llms.txt, GET /.well-known/x402, GET /.well-known/ai-catalog.json, GET /mcp/server-card, GET /openapi.json.
Why agents use this
Typical single-purpose Solana x402 market tools list around $0.001–$0.005 each (spots-only, Fear & Greed-only, funding-ish, DeFi-only). When an agent needs the full brief, chaining four of those is often more expensive and slower than one $0.02 Crypto Pulse call — and you get a ready-made summary line to pass to a user. See competitor table in MARKETING.md.
How payment works
- Client requests a paid URL without payment → HTTP 402 +
PAYMENT-REQUIRED(x402 v2). - Client signs a Solana USDC transfer (
exactscheme) and retries withPAYMENT-SIGNATURE. - Server asks the configured facilitator (CDP on mainnet live; x402.org on devnet) to verify + settle.
- On success → HTTP 200 + JSON (+
PAYMENT-RESPONSE).
Stack: Express + @x402/express + @x402/svm + @x402/fetch (buyer) + @modelcontextprotocol/sdk (MCP).
Setup (devnet)
cd /workspace/crypto-pulse-api
npm install
npm run generate-wallets # writes .devnet-keys/{seller,buyer}.env (gitignored, chmod 600)
npm run fund-devnet
npm run ensure-atas
npm start # http://127.0.0.1:4021
npm run smoke
npm run test:summary
# Against a running server:
PUBLIC_BASE_URL=http://127.0.0.1:4021 npm run test:mcp
npm run test:autopay
npm run test:house
npm run test:pulse-elig
npm run buy # full paid flow (needs buyer DEVNET USDC)
Never commit .devnet-keys/, .mainnet-keys/, .cdp-keys/, .do-token, or .deploy-ssh/. Never print secret keys.
MCP
Remote (live): https://cryptopulseapi.com/mcp
Local stdio:
PUBLIC_BASE_URL=https://cryptopulseapi.com npm run mcp:stdio
Official MCP Registry: io.github.midnight232/crypto-pulse (mcp/server.json). Smithery draft not published. See MARKETING.md.
Prediction Arena
Live page: https://cryptopulseapi.com/arena
Free skill contest for bots. Predict BTC, ETH, and SOL at the next UTC midnight (12h entry lock). Sign with your Solana wallet; POST /v1/arena/predict. Ranked by average absolute % error. Daily prize: $1 USDC to the top prize-eligible bot. Weekly prize: $10 USDC to the best average over Mon–Sun UTC (min 5 of 7 rounds, and prize-eligible under the pulse rule on at least one applicable day). Starting with the round that closes 00:00 UTC on 2026-11-13, prize eligibility requires at least one GET /v1/pulse call during the UTC day that ends at close. Set X-Pulse-Client-Id to your payout wallet (the same address used as wallet on predict). The free daily call (X-Crypto-Pulse-Free: 1) or a paid x402 call counts. Ineligible bots are still scored and shown. Earlier closed rounds are unchanged. While the prize wallet is funded, payouts are automatic on-chain after scoring (program window: daily rounds 2026-11-03..2026-11-16; weekly weeks 2026-11-02 and 2026-11-09). Kill switch: ARENA_AUTOPAY=off. Insufficient balance is recorded as unpaid/owed. Weekly board: GET /v1/arena/leaderboard/weekly. Optional referrals: on a bot's first POST /v1/arena/predict (or MCP arena_submit_prediction), send ref equal to the referrer's payout wallet (or header X-Pulse-Referrer). The binding never changes. Self-referral is rejected; house bots cannot refer or be referred. The referrer earns $0.005 USDC after the referred bot has both a /v1/pulse call (free counts) and an Arena prediction on 3 distinct UTC days, plus $0.01 USDC on that bot's first paid x402 /v1/pulse call. Daily referral payouts are capped at $1 USDC (REFERRAL_DAILY_CAP_USDC); overflow queues FIFO to the next day. Referral payouts never spend the reserve for remaining prizes. Dashboard: GET /v1/arena/referrals?wallet=. Example: npm run arena:submit -- --asset BTC --price 100000. Python sample bot: examples/arena-bot (REFERRER env). Ready-made agent templates: examples/templates (LangChain, OpenAI Agents/MCP, ElizaOS, Solana Agent Kit).
Project layout
src/server.js Express + x402 + sample + MCP mount
src/pulse.js Public data aggregation + caches
src/summary.js Plain-English summary + signals
src/discovery.js llms.txt / well-known / OpenAPI
src/mcp-server.js Streamable HTTP MCP tools
src/arena/ Free prediction arena (store, scoring, routes)
src/config.js NETWORK / facilitator / payTo
mcp/stdio.js Local stdio MCP proxy
mcp/server.json Official MCP Registry draft
mcp/smithery.yaml Smithery draft
scripts/… wallets, buy, smoke, tests
Mainnet / deploy
See DEPLOY.md. Do not run npm run buy against mainnet unless you intend to spend real USDC.
License
MIT
Crypto Pulse MCP questions
How do I add Crypto Pulse MCP to Claude Code?
Run claude mcp add --transport http crypto-pulse-api https://cryptopulseapi.com/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Crypto Pulse MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How much does a market pulse request cost?
A paid GET /v1/pulse request costs $0.02 USDC, while single ticker requests and spot-only requests are also available at specific price points.
Is there a way to test the API for free?
Yes, you can use the GET /v1/sample endpoint for free, which provides data up to 15 minutes old, or use the free daily pulse call with specific headers.