用于与 Deriv API 交互的模型上下文协议 (MCP) 服务器和 OpenAI 函数调用服务。
活动符号列表
获取账户余额
Related MCP server: Bybit MCP Server
curl -LsSf https://astral.sh/uv/install.sh | sh构建 Docker 镜像：
docker build -t deriv-api-mcp .在项目根目录中创建一个.env文件：
DERIV_API_TOKEN=your_api_key_hereClaude Desktop 全面支持 MCP 功能。使用方法如下：
添加到您的 Claude Desktop 配置：
在 macOS 上： ~/Library/Application Support/Claude/claude_desktop_config.json
在 cline VSCode 上： /Users/raju/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
在 Windows 上： %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"deriv-api-mcp": {
"command": "uv",
"args": [
"--directory",
"/Users/raju/Sites/deriv/mcp-deriv-api-server",
"run",
"server.py"
]
}
}
}{
"mcpServers": {
"deriv-api-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"deriv-api-mcp"
]
}
}
}重启Claude桌面
该服务器提供以下工具：
get_active_symbols ：获取活跃交易符号列表
get_account_balance ：获取当前账户余额
请参阅Deriv API 文档了解当前速率限制和使用指南。
麻省理工学院
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_account_balanceget_active_symbolsScored 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.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for OpenMM — exposes market data, account, trading, and strategy tools to AI agents
Trade 16 crypto exchanges + MetaTrader 5 from your AI assistant via one MCP connection.
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
