Q&A

What is MCP?

MCP (Model Context Protocol) is an open standard that allows AI assistants to securely connect to external data sources and tools. It provides a unified interface for AI models to interact with APIs without needing custom integrations for each tool.

Which AI clients support MCP?

Currently supported clients include Claude Desktop, Claude Code, Cursor, and other MCP-compatible AI tools. The list continues to grow as more tools adopt the standard.

How do I get started?

1. Configure your AI client with the endpoint URL (see Quick Start)
2. Authorize via the OAuth flow when prompted by your AI client

Is my data secure?

Yes. All communication uses HTTPS (TLS 1.2+). Authentication goes through OAuth 2.0 with scoped permissions. No credentials are stored on the MCP server — access tokens and refresh tokens are saved locally by the AI client. Keep your tokens safe and do not share them with others, as leakage may pose security risks.

What permissions can I grant?

You can grant permissions independently:

• quote:read — market data (real-time quotes, candlesticks)
• quote:write — watchlist management (add/remove symbols)
• trade:read — portfolio queries (balance, positions, order history)
• trade:write — order execution (submit, cancel orders)

Can I revoke access?

Yes. You can invalidate tokens at any time from the Dashboard.

What happens if my token expires?

MCP clients handle token refresh automatically. If a refresh fails or the token has been inactive for more than 14 days, the client will prompt you to re-authorize.

What should I do if I suspect my credentials are compromised?

Immediately disable the affected token in the console.

Connected but some tools are unavailable

• Account or regional restrictions: certain markets or features may be limited by account tier or region
• Scope changes: if tool capabilities have been updated, you may need to re-authorize to obtain new scopes

Insufficient permissions for trade operations

• Check your account's trading permissions and market eligibility
• Confirm that the current MCP session's OAuth scope includes trade-related permissions