io.github.markankamaransheogarat-sys/crypto-pulse-mcp
NPM · CRYPTO-PULSE-MCP
Read-only crypto market data: prices, funding, open interest, DeFi TVL, stablecoins. No API keys.
Available components
Last scanned (3 hours ago)
Scores higher than 53% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 546 tokens (~109/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/crypto-pulse-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_defi_tvl DeFi total value locked ~139
DeFi TVL from DefiLlama. With no arguments: the largest chains and their share. With `chain` (e.g. Solana, Stellar): that chain's TVL, rank and its top protocols. With `protocol` (e.g. aave, jupiter): its TVL, category and 1h/1d/7d change.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain name, e.g. Solana, Ethereum, Stellar |
| limit | integer | – | How many rows to return |
| protocol | string | – | Protocol name or slug, e.g. aave, uniswap |
No output schema declared.
No examples provided.
get_derivatives Perpetual funding and open interest ~95
Perpetual-futures data for a coin: funding rate (and annualised), mark vs index price (basis), open interest in USD and its ratio to 24h volume on Bybit, plus Binance's mark price and latest funding rate. Useful for judging crowding and leverage.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Coin or pair, e.g. BTC, ETHUSDT. A bare coin means a USDT perpetual |
No output schema declared.
No examples provided.
get_market_overview Top coins by market cap or volume ~98
The largest coins by market cap (or 24h volume) with price, 24h change, market cap, volume, distance from the all-time high, and how many of them are rising. Data from CoinGecko.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many coins to return |
| sort_by | string | – | Ranking criterion |
| vs_currency | string | – | Quote currency, e.g. usd, eur, btc |
No output schema declared.
No examples provided.
get_price Spot price across exchanges ~90
Current spot price, 24h change, 24h range and quote volume for a coin on Bybit and Binance, plus the price gap between the two exchanges. Accepts BTC, ETH/USDT, SOLUSDT and similar; a bare coin means a USDT pair.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Coin or pair, e.g. BTC, ETH/USDT, SOLUSDT |
No output schema declared.
No examples provided.
get_stablecoins Stablecoin supply and flows ~69
The largest USD stablecoins by circulating supply with 1d/7d/30d supply change and market share, plus the total change across all of them. Supply growth is a rough proxy for money entering or leaving crypto.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many stablecoins to return |
No output schema declared.
No examples provided.
How do I install the io.github.markankamaransheogarat-sys/crypto-pulse-mcp server?
io.github.markankamaransheogarat-sys/crypto-pulse-mcp runs locally as an npm package, launched with npx -y crypto-pulse-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · crypto-pulse-mcp
claude mcp add markankamaransheogarat-sys-crypto-pulse-mcp -- npx -y crypto-pulse-mcp
What is the io.github.markankamaransheogarat-sys/crypto-pulse-mcp server?
io.github.markankamaransheogarat-sys/crypto-pulse-mcp is listed in the public MCP registry as io.github.markankamaransheogarat-sys/crypto-pulse-mcp. Read-only crypto market data: prices, funding, open interest, DeFi TVL, stablecoins. No API keys. This page covers its npm package (crypto-pulse-mcp).
Is the io.github.markankamaransheogarat-sys/crypto-pulse-mcp server safe to use?
io.github.markankamaransheogarat-sys/crypto-pulse-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.markankamaransheogarat-sys/crypto-pulse-mcp server expose?
io.github.markankamaransheogarat-sys/crypto-pulse-mcp exposes 5 tools: get_price, get_derivatives, get_market_overview, get_defi_tvl, get_stablecoins. Their descriptions and schemas cost roughly 491 tokens of context every time the server is loaded.
Is the io.github.markankamaransheogarat-sys/crypto-pulse-mcp server still maintained?
io.github.markankamaransheogarat-sys/crypto-pulse-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.markankamaransheogarat-sys/crypto-pulse-mcp server under?
io.github.markankamaransheogarat-sys/crypto-pulse-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.