Deriv API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DERIV_API_TOKEN | Yes | Your Deriv API 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_active_symbolsD | – |
| get_account_balanceD | – |
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 2 tools
The two tools have completely distinct purposes: one retrieves account balance information, while the other fetches available trading symbols. There is no overlap in functionality, making it impossible to confuse them.
Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming is perfectly uniform across the set.
With only two tools, the server feels severely under-scoped for a Deriv API integration. A financial trading API would typically require many more operations (e.g., place orders, check positions, view history) to be useful.
The toolset is extremely incomplete for a trading API domain. It lacks core operations like creating trades, managing orders, viewing transaction history, or accessing market data beyond symbols. Agents cannot perform meaningful trading workflows.