# io.github.vip0123/cryptopulse (remote · cryptopulse.uno)

Live whale movements, wallet intel and Alpha-bot signals across 34+ EVM chains, over MCP.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `cryptopulse.uno`: 69/100 (this document), [markdown](https://verifymcp.io/servers/vip0123-cryptopulse/api-mcp.md), [page](https://verifymcp.io/servers/vip0123-cryptopulse/api-mcp)

## Channel facts

- Endpoint: `https://cryptopulse.uno/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 348 tokens (~49/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http vip0123-cryptopulse 'https://cryptopulse.uno/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "vip0123-cryptopulse": {
      "url": "https://cryptopulse.uno/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vip0123-cryptopulse": {
      "type": "http",
      "url": "https://cryptopulse.uno/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.vip0123-cryptopulse]
url = "https://cryptopulse.uno/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vip0123-cryptopulse": {
      "type": "remote",
      "url": "https://cryptopulse.uno/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vip0123-cryptopulse --url 'https://cryptopulse.uno/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vip0123-cryptopulse:
    url: "https://cryptopulse.uno/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "vip0123-cryptopulse": {
      "Transport": "http",
      "Url": "https://cryptopulse.uno/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vip0123-cryptopulse -t streamable-http -u 'https://cryptopulse.uno/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "vip0123-cryptopulse": {
      "type": "http",
      "url": "https://cryptopulse.uno/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 69, +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.

### 2026-09-17 (score 68, +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.

### 2026-09-15 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 65, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-11 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-09 (score 64)

First indexed and scored.

## MCP tools (7)

### `get_whale_movements` (~90 tokens)

Recent large 'whale' transactions (buys, sells, transfers) across 34+ EVM chains. Use to see what smart money is doing right now.

Input parameters:

- `chain` (string): Chain id, e.g. ethereum, base, arbitrum, bnb. Omit for all chains.
- `limit` (number): Max results (default 20, max 100).

### `get_wallet_intel` (~66 tokens)

Wallet intelligence for a specific address: balances, recent activity, labels, and smart-money score. Supports multichain lookup.

Input parameters:

- `address` (string, required): EVM wallet address (0x...).
- `multichain` (boolean): Aggregate across all chains (default true).

### `get_market_overview` (~22 tokens)

Crypto market overview — prices and stats for major tracked tokens.

### `list_supported_chains` (~29 tokens)

List the 34+ blockchains CryptoPulse tracks (id, name, symbol, category).

### `get_smart_money` (~30 tokens)

Recent smart-money wallet activity — moves by high-scoring funds, market makers, and notable wallets.

### `get_bot_status` (~28 tokens)

Status of the CryptoPulse Alpha trading bot — active strategy version, symbol, and performance stats.

### `get_trading_signals` (~40 tokens)

Latest algorithmic buy/sell trading signals from the Alpha bot (entry, stop-loss, take-profit). Requires a Trader or API plan key.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vip0123-cryptopulse/api-mcp#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 69
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64

## Common questions

### 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 34+ 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 69 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 305 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://cryptopulse.uno/api/mcp
- Website: https://cryptopulse.uno/agents
- Changelog RSS feed: https://verifymcp.io/servers/vip0123-cryptopulse/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/vip0123-cryptopulse/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/vip0123-cryptopulse/api-mcp