# Bitstamp (npm · @pipeworx/mcp-bitstamp)

Bitstamp MCP (public endpoints).

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-bitstamp`
- 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-bitstamp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 519 tokens (~74/item across 7 items; 7 tools + 0 resources), lean.
  - 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**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 Bitstamp MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-05 (score 81, +1)

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

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

### 2026-10-31 (score 78, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 63, −14)

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

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

First indexed and scored.

## MCP tools (7)

### `ticker` (~52 tokens)

Fetch current Bitstamp ticker for a currency pair (e.g. btcusd): last price, bid, ask, 24h high/low/volume/vwap, and open.

Input parameters:

- `currency_pair` (string, required)

### `ticker_hour` (~56 tokens)

Fetch Bitstamp last-hour ticker stats for a currency pair (e.g. btcusd): last, bid, ask, high, low, volume, and vwap over the past 60 minutes.

Input parameters:

- `currency_pair` (string, required)

### `order_book` (~69 tokens)

Bitstamp crypto exchange (European; oldest active crypto exchange — est. 2011) order book for a crypto pair like "btcusd": bids + asks. Use for live depth-of-book on Bitstamp-listed pairs.

Input parameters:

- `currency_pair` (string, required)
- `group` (number)

### `transactions` (~61 tokens)

Fetch recent Bitstamp trades for a currency pair; optional time filter (minute, hour, day) sets the lookback window. Returns trade id, price, amount, type, and timestamp.

Input parameters:

- `currency_pair` (string, required)
- `time` (string)

### `eur_usd` (~106 tokens)

Bitstamp's own EUR↔USD conversion rate — the buy/sell prices Bitstamp applies when converting fiat balances on the exchange, quoted with the exchange's retail markup (the two legs can differ by several percent). Use when you need the rate a Bitstamp account actually transacts at. For the market FX rate — "EURUSD spot", "current euro to dollar rate", anything macro or reporting-grade — use ecb_exchange_rate, which publishes the official euro reference rate.

### `trading_pairs` (~35 tokens)

List all Bitstamp trading pairs with metadata: base/counter currency, minimum order, symbol, trading enabled status, and URL symbol.

### `ohlc` (~88 tokens)

Fetch OHLC candlestick data from Bitstamp for a currency pair; step sets candle duration in seconds, limit caps candle count, with optional Unix start/end range.

Input parameters:

- `currency_pair` (string, required)
- `end` (number)
- `exclude_current_candle` (boolean)
- `limit` (number, required)
- `start` (number)
- `step` (number, required)

## Diagnostics

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

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 63
- 2026-10-29: 77

## Common questions

### What is the Bitstamp MCP server?

Bitstamp is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bitstamp. Bitstamp MCP (public endpoints). This page covers its npm package (@pipeworx/mcp-bitstamp).

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

Bitstamp scores 81 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 Bitstamp MCP server expose?

Bitstamp exposes 7 tools: ticker, ticker_hour, order_book, transactions, eur_usd, and 2 more. Their descriptions and schemas cost roughly 467 tokens of context every time the server is loaded.

### Is the Bitstamp MCP server still maintained?

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

Bitstamp 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-bitstamp
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-bitstamp
- Repository: https://github.com/pipeworx-io/mcp-bitstamp
- Website: https://pipeworx.io/packs/bitstamp
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-bitstamp/pipeworx-mcp-bitstamp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-bitstamp/pipeworx-mcp-bitstamp.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-bitstamp/pipeworx-mcp-bitstamp