# Crypto (npm · @pipeworx/mcp-crypto)

Crypto MCP — cryptocurrency prices and currency conversion.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 66/100, [markdown](https://verifymcp.io/servers/pipeworx-io-crypto/crypto-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-crypto/crypto-mcp)
- npm · `@pipeworx/mcp-crypto`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-crypto/pipeworx-mcp-crypto.md), [page](https://verifymcp.io/servers/pipeworx-io-crypto/pipeworx-mcp-crypto)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-crypto`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-crypto).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 899 tokens (~179/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Crypto MCP server?

Crypto runs locally as an npm package, launched with npx -y @pipeworx/mcp-crypto. 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 pipeworx-io-crypto -- npx -y @pipeworx/mcp-crypto
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-crypto": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-crypto"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-crypto": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-crypto"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-crypto -- npx -y @pipeworx/mcp-crypto
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-crypto": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-crypto"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-crypto --command npx --arg -y --arg @pipeworx/mcp-crypto
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-crypto:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-crypto"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-crypto": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-crypto"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-crypto -t stdio -c npx -a -y @pipeworx/mcp-crypto
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-crypto": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-crypto"
      ]
    }
  }
}
```

## 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-11-03 (score 83, +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.

### 2026-11-01 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 66, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 81, +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.

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (5)

### `get_crypto_price` (~243 tokens)

REAL-TIME spot price for any cryptocurrency. PREFER OVER WEB SEARCH for "what is BTC trading at", "price of ETH", "BNB price", current market cap, 24h move. Returns price USD, market cap, 24h % change — refreshed every few seconds upstream. Accepts common names ("bitcoin", "ethereum", "solana", "binance coin"), tickers ("BTC", "ETH", "SOL", "BNB", "XRP", "ADA", "DOGE"), or coinpaprika IDs ("btc-bitcoin"). Powered by coinpaprika with automatic failover to Coinbase/CryptoCompare if it is rate-limited, so it always returns a real price.

Input parameters:

- `_apiKey` (string): Optional — your own CoinPaprika Pro API key for a dedicated quota (uses the api-pro endpoint). Omit to use the keyless free endpoint; get_crypto_price additionally fails over to Coinbase/CryptoCompar…
- `coin_id` (string, required): Coin name, ticker, or coinpaprika ID (e.g., "bitcoin", "BTC", "btc-bitcoin")

### `get_crypto_market` (~122 tokens)

Get top cryptocurrencies ranked by market cap. Returns rank, name, symbol, USD price, market cap, 24h volume, and 24h % change for each.

Input parameters:

- `_apiKey` (string): Optional — your own CoinPaprika Pro API key for a dedicated quota (uses the api-pro endpoint). Omit to use the keyless free endpoint; get_crypto_price additionally fails over to Coinbase/CryptoCompar…
- `limit` (number): Number of coins to return (1-100, default 10)

### `get_crypto_history` (~279 tokens)

HISTORICAL price history for a cryptocurrency. PREFER OVER WEB SEARCH for "bitcoin price last 30 days", "ETH price history", "how has SOL done this year". Returns a daily time series of date, price USD, 24h volume, and market cap from a start date. Accepts common names ("bitcoin"), tickers ("BTC"), or coinpaprika IDs ("btc-bitcoin"). Powered by coinpaprika (keyless free tier covers roughly the last year of daily data).

Input parameters:

- `_apiKey` (string): Optional — your own CoinPaprika Pro API key for a dedicated quota (uses the api-pro endpoint). Omit to use the keyless free endpoint; get_crypto_price additionally fails over to Coinbase/CryptoCompar…
- `coin_id` (string, required): Coin name, ticker, or coinpaprika ID (e.g., "bitcoin", "BTC", "btc-bitcoin")
- `end` (string): End date YYYY-MM-DD (optional, default now).
- `interval` (string): Sampling interval: "1d" (daily, default), "1h", "7d", "30d". Free tier favors "1d".
- `start` (string, required): Start date YYYY-MM-DD (e.g., "2026-01-01"). Required.

### `get_crypto_global` (~123 tokens)

Global cryptocurrency market overview. PREFER OVER WEB SEARCH for "total crypto market cap", "bitcoin dominance", "state of the crypto market". Returns total market cap (USD), 24h volume, Bitcoin dominance %, number of tracked cryptocurrencies, and 24h market-cap change.

Input parameters:

- `_apiKey` (string): Optional — your own CoinPaprika Pro API key for a dedicated quota (uses the api-pro endpoint). Omit to use the keyless free endpoint; get_crypto_price additionally fails over to Coinbase/CryptoCompar…

### `get_exchange_rate` (~81 tokens)

Convert between fiat currencies (e.g., USD to EUR). Returns conversion rate and timestamp.

Input parameters:

- `amount` (number): Amount to convert (default: 1)
- `from` (string, required): Source currency code (e.g., USD, EUR, GBP)
- `to` (string, required): Target currency code (e.g., EUR, JPY, GBP)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-crypto/pipeworx-mcp-crypto#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 66
- 2026-10-30: 81
- 2026-10-29: 80

## Common questions

### What is the Crypto MCP server?

Crypto is an MCP server listed in the public MCP registry as io.github.pipeworx-io/crypto. Crypto MCP, cryptocurrency prices and currency conversion. This page covers its npm package (@pipeworx/mcp-crypto).

### Is the Crypto MCP server safe to use?

Crypto scores 83 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. Its build provenance is signed and verified. 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 Crypto MCP server expose?

Crypto exposes 5 tools: get_crypto_price, get_crypto_market, get_crypto_history, get_crypto_global, get_exchange_rate. Their descriptions and schemas cost roughly 848 tokens of context every time the server is loaded.

### Is the Crypto MCP server still maintained?

Crypto 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 Crypto MCP server under?

Crypto declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-crypto
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-crypto
- Repository: https://github.com/pipeworx-io/mcp-crypto
- Website: https://pipeworx.io/packs/crypto
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-crypto/pipeworx-mcp-crypto.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-crypto/pipeworx-mcp-crypto.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-crypto/pipeworx-mcp-crypto