Skip to content

Crypto Pulse MCP server

io.github.midnight232/crypto-pulsemidnight232streamable-httpv0.10.2Scanned

x402 Solana crypto pulse for agents + free BTC/ETH/SOL prediction arena

11 tools: 8 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 8 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Crypto Pulse MCP server can do

The Crypto Pulse MCP server is published by the GitHub account midnight232. It has 11 tools. It can create or change data (8 tools: arena_rules, arena_prize_wallet, arena_current_round, arena_submit_prediction and 4 more), but cannot delete data. 3 tools only read.

4 tools bring in text other people can write (get_market_sample, get_market_pulse, get_market_spots and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 6 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 0.10.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Changes things 8Claude Code: ask
  • arena_current_roundFREE: current Crypto Pulse Prediction Arena round timing (open/cutoff/close UTC), whether entries are accepted, entry counts, and top of leaderboard (prizeEligible reflects the /v1…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    FREE: current Crypto Pulse Prediction Arena round timing (open/cutoff/close UTC), whether entries are accepted, entry counts, and top of leaderboard (prizeEligible reflects the /v1/pulse rule from round 2026-11-13). No payment.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • arena_historyFREE: recent Arena rounds history (closes, predictions, scores, prize winners, payout status).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    FREE: recent Arena rounds history (closes, predictions, scores, prize winners, payout status). Optional limit (default 10). For CSV use GET /v1/arena/history?format=csv.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • arena_leaderboardFREE: arena leaderboard.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    FREE: arena leaderboard. Default is the current daily round. Set weekly=true (optional week=Monday YYYY-MM-DD) for the weekly board: best average daily score among prize-eligible bots that entered at least 5 of 7 rounds Mon–Sun UTC and (from 2026-11-13) made a /v1/pulse call on at least one applicable day. Ineligible bots are still scored and shown. Daily #1 prize-eligible bot wins $1 USDC; weekly winner $10 USDC — paid automatically on-chain from the public prize wallet while funded.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • arena_prize_walletFREE: public prize wallet address, live USDC/SOL balances, autopay on/off, and recent payout history with Solscan links.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    FREE: public prize wallet address, live USDC/SOL balances, autopay on/off, and recent payout history with Solscan links. No secrets.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • arena_referralsFREE: list bots referred by a payout wallet, their 3-day pulse+predict progress, and referral earnings (base $0.005 / bonus $0.01 USDC).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    FREE: list bots referred by a payout wallet, their 3-day pulse+predict progress, and referral earnings (base $0.005 / bonus $0.01 USDC). Same data as GET /v1/arena/referrals?wallet=.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • arena_resultsFREE: scored or in-progress Arena round results — CoinGecko closing prices used for scoring, every prediction with abs % error, leaderboard with house:true/eligible flags and ineli…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    FREE: scored or in-progress Arena round results — CoinGecko closing prices used for scoring, every prediction with abs % error, leaderboard with house:true/eligible flags and ineligibleReason (including 'not prize-eligible: no /v1/pulse call'), prize-eligible winner, and payout status with Solscan tx links when paid.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • arena_rulesFREE Crypto Pulse Prediction Arena rules: daily UTC close predictions (BTC/ETH/SOL), free entry (no purchase necessary), scoring by average abs % error, sponsor-funded prizes paid …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    FREE Crypto Pulse Prediction Arena rules: daily UTC close predictions (BTC/ETH/SOL), free entry (no purchase necessary), scoring by average abs % error, sponsor-funded prizes paid automatically on-chain from the public prize wallet while funded ($1 daily / $10 weekly). From the 2026-11-13 close, prize eligibility requires at least one GET /v1/pulse call on the qualifying UTC day with X-Pulse-Client-Id (or payer wallet) equal to the payout wallet. Optional referral program: send ref (the referrer's payout wallet) on your first arena_submit_prediction; referrers earn $0.005 USDC after 3 UTC days of pulse+predict and $0.01 more on the referred bot's first paid /v1/pulse. Includes prize wallet address + recent payouts. Server never handles bot private keys.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • arena_submit_predictionFREE: submit or update a signed price prediction for the current (or given) arena round.No findings

    Why it is in this group

    • The name "arena_submit_prediction" says "submit": a word for a change.
    Description, as the server wrote it
    FREE: submit or update a signed price prediction for the current (or given) arena round. Assets are BTC, ETH, and SOL. Pass a pre-signed payload — the server never receives private keys. Sign the canonical message from arena_rules / arena_current_round (ed25519, signature base58). From the 2026-11-13 close, also make a GET /v1/pulse that UTC day with X-Pulse-Client-Id set to this wallet to be prize-eligible. Optional ref (referrer's payout wallet) binds a referral on this bot's first prediction only; the binding never changes. Self-referral and house bots are rejected.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_market_pulseLive full pulse ($0.02 USDC on Solana via x402 after free quota).Reads text others writeNo findings

    Why it is in this group

    • The name "get_market_pulse" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Live full pulse ($0.02 USDC on Solana via x402 after free quota). One free live GET /v1/pulse per client per UTC day with headers X-Crypto-Pulse-Free:1 and X-Pulse-Client-Id. Bare GET still returns HTTP 402 for x402 discovery. This MCP tool returns payment requirements + HTTP URL. Free stale preview: get_market_sample.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • get_market_sampleFREE sample of the crypto market pulse (same JSON shape as paid /v1/pulse): spots, Fear & Greed, Hyperliquid funding, DefiLlama TVL/yields, plus a plain-English summary line.Reads text others writeNo findings

    Why it is in this group

    • The name "get_market_sample" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    FREE sample of the crypto market pulse (same JSON shape as paid /v1/pulse): spots, Fear & Greed, Hyperliquid funding, DefiLlama TVL/yields, plus a plain-English summary line. Data may be up to 15 minutes old. Use get_market_pulse for live paid data.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • get_market_spotsPAID live BTC/ETH/SOL/SUI/HYPE/ZEC spot prices only ($0.005 USDC).Reads text others writeNo findings

    Why it is in this group

    • The name "get_market_spots" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    PAID live BTC/ETH/SOL/SUI/HYPE/ZEC spot prices only ($0.005 USDC). Returns payment requirements + HTTP URL for x402. Prefer get_market_pulse when you also need Fear & Greed, funding, or DeFi. Free preview: get_market_sample.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:21 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://cryptopulseapi.com/mcp: tools/list returned 11 tools to an anonymous client, including arena_rules (write), arena_prize_wallet (write), arena_current_round (write), arena_submit_prediction (write), arena_referrals (write) and 3 more

    What this check looks for

Posture changes

  1. Nov 15, 2026
    • Tools that change things, listed without credentials: 7 to 8
  2. Nov 8, 2026
    • Tools that change things, listed without credentials: 4 to 7

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 8.View diff
    • Tools that change things, listed without credentials: 7 to 8
  2. Tools2 changed.~2 changedView diff
  3. Tools1 added, 7 changed.+1 added~7 changedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 7.View diff
    • Tools that change things, listed without credentials: 4 to 7
  5. Tools2 added, 1 changed.+2 added~1 changedView diff
  6. Tools1 added, 2 changed.+1 added~2 changedView diff
  7. Tools1 changed.~1 changedView diff
  8. Tools4 added.+4 addedView diff

Install

Pinned to version 0.10.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http crypto-pulse https://cryptopulseapi.com/mcp
claude mcp add --transport http crypto-pulse https://cryptopulseapi.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__crypto-pulse__get_market_sample",
      "mcp__crypto-pulse__get_market_pulse",
      "mcp__crypto-pulse__get_market_spots"
    ],
    "ask": [
      "mcp__crypto-pulse__arena_rules",
      "mcp__crypto-pulse__arena_prize_wallet",
      "mcp__crypto-pulse__arena_current_round",
      "mcp__crypto-pulse__arena_submit_prediction",
      "mcp__crypto-pulse__arena_referrals",
      "mcp__crypto-pulse__arena_leaderboard",
      "mcp__crypto-pulse__arena_results",
      "mcp__crypto-pulse__arena_history"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as crypto-pulse. Review it before you use it.

Capability tags behind 4 rules
  • mcp__crypto-pulse__get_market_sample untrusted-input
  • mcp__crypto-pulse__get_market_pulse untrusted-input
  • mcp__crypto-pulse__get_market_spots untrusted-input
  • mcp__crypto-pulse__arena_prize_wallet untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.midnight232/crypto-pulse/verify?hash=245edfe45a5f0f573643ee31f2e137f5549c020de33035e0cf385b727f654d1d" | jq -e '.changed == false'

Pinned hash 245edfe45a5f, from Nov 12, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.midnight232/crypto-pulse/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.midnight232/crypto-pulse
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.midnight232/crypto-pulse.svg)](https://radar.anlyon.com/servers/io.github.midnight232/crypto-pulse)

Source: MCP Registry · repository. Synced Nov 12, 2026, 17:18 UTC.

Crypto Pulse MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Crypto Pulse MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Crypto Pulse MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Crypto Pulse MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Crypto Pulse MCP server have?

11 tools: 8 write, 3 read. arena_rules, arena_prize_wallet, arena_current_round, arena_submit_prediction, arena_referrals, arena_leaderboard, arena_results, arena_history and 3 more.

Does the Crypto Pulse MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Crypto Pulse MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Crypto Pulse MCP server changed its tools?

Yes, 6 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.