io.github.vip0123/cryptopulse
REMOTE · CRYPTOPULSE.UNO
Live whale movements, wallet intel and Alpha-bot signals across 17 EVM chains, over MCP.
Available components
Last scanned (50 minutes ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 358 tokens (~51/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 28 Oct 26 0
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 27 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Oct 26 +1
- Stability: 0.93 → pass security
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 93. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Tool “get_whale_movements” rewrote its description, which is the text the model reads security
- Tool “list_supported_chains” rewrote its description, which is the text the model reads security
- 25 Sept 26 0
- Tool “get_whale_movements” rewrote its description, which is the text the model reads security
- Tool “list_supported_chains” rewrote its description, which is the text the model reads security
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- “get_whale_movements” reworded the description of “chain” cosmetic
- 21 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_trading_signals” rewrote its description, which is the text the model reads security
- Tool “get_whale_movements” rewrote its description, which is the text the model reads security
- Tool “list_supported_chains” rewrote its description, which is the text the model reads security
- MCP protocol: pass → fail ▼ functional
- MCP protocol version: 2025-11-25 → 2025-06-18 functional
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 · Probed https://cryptopulse.uno/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cryptopulse.uno | CN=YR1,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | RSA 2048 | SHA256-RSA | 64f6da46568ebaf91f7c5e318d3e19bc150 |
| SANs: *.cryptopulse.uno, cryptopulse.uno | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cryptopulse.uno. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uno. | present | 49457 | 13 | Verified |
| cryptopulse.uno. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cryptopulse.uno/api/mcp | Verified | 200 | |
| http (plaintext) | http://cryptopulse.uno/api/mcp | HTTPS enforced | 301 | https://cryptopulse.uno/api/mcp |
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_bot_status ~28
Status of the CryptoPulse Alpha trading bot — active strategy version, symbol, and performance stats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_market_overview ~22
Crypto market overview — prices and stats for major tracked tokens.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_smart_money ~30
Recent smart-money wallet activity — moves by high-scoring funds, market makers, and notable wallets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trading_signals ~40
Latest algorithmic buy/sell trading signals from the Alpha bot (entry, stop-loss, take-profit). Requires a Trader or Api plan key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_wallet_intel ~66
Wallet intelligence for a specific address: balances, recent activity, labels, and smart-money score. Supports multichain lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM wallet address (0x...). |
| multichain | boolean | – | Aggregate across all chains (default true). |
No output schema declared.
No examples provided.
get_whale_movements ~88
Recent large 'whale' transactions (buys, sells, transfers) across 17 EVM chains. Use to see what smart money is doing right now.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain id, e.g. ethereum, base, arbitrum, optimism. Omit for all chains. |
| limit | number | – | Max results (default 20, max 100). |
No output schema declared.
No examples provided.
list_supported_chains ~28
List the 17 blockchains CryptoPulse tracks (id, name, symbol, category).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.vip0123/cryptopulse MCP server?
io.github.vip0123/cryptopulse is a hosted endpoint at https://cryptopulse.uno/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · cryptopulse.uno
claude mcp add --transport http vip0123-cryptopulse 'https://cryptopulse.uno/api/mcp'
What is the io.github.vip0123/cryptopulse MCP server?
io.github.vip0123/cryptopulse is an MCP server listed in the public MCP registry as io.github.vip0123/cryptopulse. Live whale movements, wallet intel and Alpha-bot signals across 17 EVM chains, over MCP. This page covers its hosted endpoint (https://cryptopulse.uno/api/mcp).
Is the io.github.vip0123/cryptopulse MCP server safe to use?
io.github.vip0123/cryptopulse scores 76 out of 100 on VerifyMCP. 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.vip0123/cryptopulse MCP server expose?
io.github.vip0123/cryptopulse exposes 7 tools: get_whale_movements, get_wallet_intel, get_market_overview, list_supported_chains, get_smart_money, and 2 more. Their descriptions and schemas cost roughly 302 tokens of context every time the server is loaded.
Does the io.github.vip0123/cryptopulse MCP server require authentication?
No. We connected to io.github.vip0123/cryptopulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.vip0123/cryptopulse MCP server still maintained?
io.github.vip0123/cryptopulse 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.