# Bitfinex (npm · @pipeworx/mcp-bitfinex)

Bitfinex v2 public MCP.

- Trust score: 79/100 (medium)
- Change this week: +3
- 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-bitfinex/bitfinex-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-bitfinex/bitfinex-mcp)
- npm · `@pipeworx/mcp-bitfinex`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-bitfinex/pipeworx-mcp-bitfinex.md), [page](https://verifymcp.io/servers/pipeworx-io-bitfinex/pipeworx-mcp-bitfinex)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-bitfinex`
- 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-bitfinex).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 775 tokens (~70/item across 11 items; 11 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 Bitfinex MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 79, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-04 (score 79, +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-11-02 (score 78, +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-10-31 (score 77, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 61, −15)

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

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

First indexed and scored.

## MCP tools (11)

### `tickers` (~61 tokens)

Bitfinex crypto exchange — multi-symbol live tickers for crypto pairs. Pass comma-separated symbols like "tBTCUSD,tETHUSD" or "ALL". Returns bid/ask, last, daily change, volume per pair.

Input parameters:

- `symbols` (string, required)

### `ticker` (~51 tokens)

Bitfinex crypto exchange — single-pair live ticker (e.g. "tBTCUSD"). Returns bid/ask, last trade price, 24h volume + change percentage.

Input parameters:

- `symbol` (string, required)

### `ticker_history` (~79 tokens)

Bitfinex crypto exchange — historical ticker snapshots for one or more pairs (comma-separated symbols like 'tBTCUSD'). Optional start/end (ms epoch) and limit. Returns bid/ask/last per timestamp.

Input parameters:

- `end` (number)
- `limit` (number)
- `start` (number)
- `symbols` (string, required)

### `trades` (~88 tokens)

Bitfinex crypto exchange — recent trade tape for a pair (e.g. 'tBTCUSD'): trade ID, timestamp, amount, and price per execution. Optional start/end (ms epoch), limit, and sort order.

Input parameters:

- `end` (number)
- `limit` (number)
- `sort` (number)
- `start` (number)
- `symbol` (string, required)

### `book` (~73 tokens)

Bitfinex crypto exchange order book (bids + asks) for a crypto pair like "tBTCUSD". Returns price levels with size + count. Use for live depth-of-book analysis, spread, market microstructure.

Input parameters:

- `length` (number)
- `precision` (string)
- `symbol` (string, required)

### `stats` (~67 tokens)

Statistics by key.

Input parameters:

- `end` (number)
- `key` (string, required)
- `limit` (number)
- `section` (string)
- `side` (string)
- `sort` (number)
- `start` (number)
- `symbol` (string, required)

### `candles` (~105 tokens)

Bitfinex crypto OHLC candles for a crypto pair. Timeframes 1m through 1M. Returns timestamped open/high/low/close + volume. Use for charting, technical analysis, backtesting on Bitfinex.

Input parameters:

- `end` (number)
- `limit` (number)
- `section` (string, required)
- `sort` (number)
- `start` (number)
- `symbol` (string, required)
- `timeframe` (string, required)

### `derivatives_status` (~21 tokens)

Perpetual contract status.

Input parameters:

- `keys` (string)

### `derivatives_status_history` (~48 tokens)

Historical derivatives status.

Input parameters:

- `end` (number)
- `key` (string, required)
- `limit` (number)
- `sort` (number)
- `start` (number)

### `liquidations` (~117 tokens)

Bitfinex crypto exchange — the historical feed of forced margin liquidations across Bitfinex pairs (/v2/liquidations/hist). Each row carries the pair symbol, event timestamp, liquidated position size and the price it was closed at; optional start/end (ms epoch), limit and sort. Answers which leveraged crypto positions got liquidated on Bitfinex, when, and at what price.

Input parameters:

- `end` (number)
- `limit` (number)
- `sort` (number)
- `start` (number)

### `platform_status` (~11 tokens)

Platform status.

## Diagnostics

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

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 61
- 2026-10-29: 76

## Common questions

### What is the Bitfinex MCP server?

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

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

Bitfinex scores 79 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 Bitfinex MCP server expose?

Bitfinex exposes 11 tools: tickers, ticker, ticker_history, trades, book, and 6 more. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.

### Is the Bitfinex MCP server still maintained?

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

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