mcp-deribit-options
by pipeworx-io
README.md
# @pipeworx/deribit-options
Crypto options open interest from Deribit public market data: per-strike call and put open interest for BTC and ETH options, put/call open-interest ratio per expiry, and max pain.
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2006+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `deribit_option_expiries(currency)` — the live expiries for BTC or ETH with instruments listed, total call and put open interest and the put/call ratio per expiry, plus the snapshot time.
- `deribit_options_open_interest(currency, expiry?)` — per-strike call and put open interest for one expiry (default: the nearest; accepts 20NOV26 or 2026-11-20), the expiry's totals, the put/call open-interest ratio, max pain, the underlying price, and a summary of every expiry.
## Auth
Keyless.
## Data sources
- Deribit, public market data (option book summaries): open interest for every listed option, read live on each call. Every response carries `data_as_of`, the snapshot time stated by Deribit.
## Honest limits
Open interest is Deribit's published figure, in contracts (one contract covers one unit of the coin). The put/call ratio and max pain are computed here from that snapshot. Deribit does not publish max pain: it is the settlement price that minimizes the total intrinsic value owed to option holders, using open interest by strike, and it is an estimate, not a forecast. BTC and ETH inverse options only (no USDC-margined options). A live snapshot, not history. An expiry that is not listed returns `no_match: true` with the listed expiries; a book that cannot be read is an error.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"deribit-options": {
"url": "https://gateway.pipeworx.io/deribit-options/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/deribit-options/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:
```json
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
```
Both URLs reach the same gateway and the same 2006+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.
## No MCP client? Call it over HTTP
```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/deribit_option_expiries \
-H 'Content-Type: application/json' \
-d '{"currency":"BTC"}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/deribit_option_expiries`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-deribit-options` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/deribit-options/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"deribit-options": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-deribit-options"]
}
}
}
```
Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.
## Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:
```
ask_pipeworx({ question: "your question about Deribit Options data" })
```
The gateway picks the right tool and fills the arguments automatically.
## More
- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)
## License
MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessOutdated data