Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bitfinex

NPM · @PIPEWORX/MCP-BITFINEX · 2 COMPONENTS

Bitfinex v2 public MCP.

+3 this week 79 Trust /100

Last scanned (5 hours ago)

Scores higher than 61% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-bitfinex). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 775 tokens (~70/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 5 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 4 Nov 26 +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.

  • 2 Nov 26 +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.

  • 31 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 29 Oct 26 76

    First indexed and scored.

Diagnostics

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 · Analysed npm/@pipeworx/mcp-bitfinex@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-bitfinex
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-bitfinex/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3601476575
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ae0509d02f15960eb7719726901185a3cc96085575dcc06cbf79b563da11bbf2218686e0312e0a94694a7dcb6c39a580e877f522546379045375003b2

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~721 tokens

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 →

Tool Tokens
book ~73

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.

NameTypeReqDescription
lengthnumber––
precisionstring––
symbolstringyes–

No output schema declared.

No examples provided.

candles ~105

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.

NameTypeReqDescription
endnumber––
limitnumber––
sectionstringyes–
sortnumber––
startnumber––
symbolstringyes–
timeframestringyes–

No output schema declared.

No examples provided.

derivatives_status ~21

Perpetual contract status.

NameTypeReqDescription
keysstring––

No output schema declared.

No examples provided.

derivatives_status_history ~48

Historical derivatives status.

NameTypeReqDescription
endnumber––
keystringyes–
limitnumber––
sortnumber––
startnumber––

No output schema declared.

No examples provided.

liquidations ~117

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.

NameTypeReqDescription
endnumber––
limitnumber––
sortnumber––
startnumber––

No output schema declared.

No examples provided.

platform_status ~11

Platform status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

stats ~67

Statistics by key.

NameTypeReqDescription
endnumber––
keystringyes–
limitnumber––
sectionstring––
sidestring––
sortnumber––
startnumber––
symbolstringyes–

No output schema declared.

No examples provided.

ticker ~51

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

NameTypeReqDescription
symbolstringyes–

No output schema declared.

No examples provided.

ticker_history ~79

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.

NameTypeReqDescription
endnumber––
limitnumber––
startnumber––
symbolsstringyes–

No output schema declared.

No examples provided.

tickers ~61

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.

NameTypeReqDescription
symbolsstringyes–

No output schema declared.

No examples provided.

trades ~88

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.

NameTypeReqDescription
endnumber––
limitnumber––
sortnumber––
startnumber––
symbolstringyes–

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-bitfinex

# add to Claude Code
claude mcp add pipeworx-io-bitfinex -- npx -y @pipeworx/mcp-bitfinex
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.