options-chain-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATA_PROVIDER | No | Optional, explicitly select provider: 'alpaca' or 'tradier' | |
| TRADIER_TOKEN | No | Your Tradier sandbox token for data provider | |
| ALPACA_API_KEY_ID | No | Your Alpaca API key ID | |
| ALPACA_SECRET_KEY | No | Your Alpaca secret key |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find-options-chainA | Query the data provider for the options chain of a symbol on a specific expiration date. The result is filtered to options with volume, bid, and ask greater than 0.10 and strikes within a configurable percentage of the underlying price. If nothing is found the result may be empty — check that the symbol and expiration are valid. |
| historical-pricesB | Historical OHLCV bars for a stock symbol or OCC option contract over a time range. |
| find-option-expirationsC | List valid option expiration dates for an underlying symbol. |
| get-quoteA | Get the latest quote for a stock symbol or single OCC option contract. For option symbols the response includes Greeks and implied volatility when the provider supports it. |
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 4 tools
Each tool has a clearly distinct purpose: historical bars, expiration listing, latest quote with Greeks, and options chain query. No overlap in functionality.
Three tools follow verb_noun pattern (find-option-expirations, get-quote, find-options-chain), but historical-prices is a noun phrase without a verb, creating a minor inconsistency.
With 4 tools, the server covers essential options data operations (historical, expirations, quotes, chain) without being too sparse or bloated.
Core data retrieval is covered, but there is a minor gap: find-options-chain does not explicitly include Greeks for options in the chain, and there is no tool for retrieving option-specific Greeks across multiple contracts in a batch.