derive-options-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP transport only | 8080 |
| MCP_PATH | No | HTTP transport only | /mcp |
| DERIVE_NETWORK | No | v3-testnet to point at testnet | mainnet |
| DERIVE_HANDOFF_URL | No | Where trade links point | https://tacticalls.xyz |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| propose_tradesA | Given a view on a coin and a budget, return a few real option structures that express it, priced against the live book and sized to the budget. Use this for 'I think X will go up', 'what should I trade if I expect a big move', 'how do I bet on ETH staying flat'. Every result is tradable right now: candidates that cannot be filled are discarded, not softened. Each is ranked by what it pays if the market moves one standard deviation by that expiry — the market's own implied volatility, not a guess — divided by what it puts at risk. Structures whose loss has no limit are left out unless allow_uncapped is set. |
| propose_hedgeA | Given a holding and the level they want protected, return ways to protect it, priced against the live book. Use this for 'I hold 5000 dollars of ETH and want to protect it', 'how do I put a floor under my BTC'. The payoff returned is the WHOLE position — the coin plus the options — not the options alone, which is the only honest way to show what protection does. Says plainly where each one stops protecting and what it costs as a share of the holding. |
| price_structureA | Price a specific shape at a specific expiry against the live book — use when the shape is already decided, or to compare a variant of something propose_trades returned. |
| list_strategiesA | The option structures available, each with what it bets on and its trade-off, in plain language. Use to pick a shape id for price_structure, or to explain the options to someone. |
| list_currenciesA | Which coins can be traded here, with their current price and how many expiries are listed. |
| list_expiriesA | Every listed expiry for a coin, with how far away it is and how many strikes are quoted on it. |
| get_option_chainA | Every quoted strike on one expiry — bid, ask, mark, implied volatility and delta for both the up and down contract. Use when you need to reason about the actual book rather than take a proposal. |
| get_spotA | Current price, and optionally where it has been, so a view can be grounded in what actually happened. |
| get_tickerA | Bid, ask, mark, implied volatility and greeks for a single named instrument, e.g. 'ETH-20261030-3000-C'. |
| get_recent_tradesA | The most recent option trades on the whole exchange, newest first. Use to see what other people are actually putting money on before proposing something. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct resource and action: trade proposals, hedging, pricing specific structures, listing strategies, currencies, expiries, option chains, spot, tickers, and recent trades. No two tools have overlapping purposes; even the two proposal tools are clearly separated by intent (expressing a view vs. protecting a holding).
All tools follow a consistent verb_noun pattern with lowercase snake_case: propose_trades, propose_hedge, price_structure, list_strategies, list_currencies, list_expiries, get_option_chain, get_spot, get_ticker, get_recent_trades. Verbs (propose, price, list, get) clearly indicate the action, and the pattern is uniform across the set.
With 10 tools, the server is well-scoped for its domain of options analysis and trade generation. Each tool serves a clear purpose—generating ideas, hedging, pricing, listing available instruments, and retrieving market data—without redundancy or bloat.
The surface covers the core workflow: generating trade ideas, hedging existing holdings, pricing specific structures, listing strategies and market metadata, and accessing detailed market data. A minor gap is the lack of trade execution (the server seems focused on analysis and pricing), but this is likely intentional given the server's name and description. Overall, the domain is well-covered.