Tastytrade MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASTYTRADE_CLIENT_SECRET | Yes | Tastytrade Client Secret | |
| TASTYTRADE_REFRESH_TOKEN | Yes | Tastytrade Refresh Token |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_price_historyB | |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct and standalone.
The single tool name follows a clear verb_noun pattern (get_price_history), and with only one tool, consistency is inherently perfect as there are no other tools to compare against.
A single tool is too few for a server named 'Tastytrade MCP Server', which implies a broader financial or trading domain. This minimal toolset feels thin and under-scoped for such a purpose.
The server is severely incomplete for its implied domain. It only provides historical price data, with no tools for account management, order placement, real-time quotes, or other core trading functionalities, leading to significant gaps.