get_order_status — Epsilon MCP Tool Read-only

get_order_status (get order status) is one of 15 tools on the Epsilon MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call get_order_status from your client

Claude Code Epsilon get_order_status run in your project directory
Claude Desktop Epsilon get_order_status ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Epsilon get_order_status ~/.cursor/mcp.json
VS Code Epsilon get_order_status .vscode/mcp.json
Zed Epsilon get_order_status ~/.config/zed/settings.json
Windsurf Epsilon get_order_status ~/.codeium/windsurf/mcp_config.json
Cline Epsilon get_order_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Epsilon get_order_status ~/.gemini/settings.json
Grok Epsilon get_order_status .mcp.json (in your project root)
ChatGPT Epsilon get_order_status Settings → Connectors → Advanced → Developer mode
Claude.ai Epsilon get_order_status Settings → Connectors → Add custom connector
LangChain Epsilon get_order_status pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http epsilon https://api.epsilon.exchange/mcp

Other tools on this server

error_catalog
get_example
get_market_overview
get_orderbook
get_quote
get_route
list_examples
list_orders
market_stats
order_preflight
recent_swaps
search_docs
search_tokens
token_volume

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Epsilon MCP server