Public support channels

Support

First distinguish the local plugin from the public read-only MCP service, then provide a minimal reproduction with sensitive information removed.

First install

Follow the getting-started guide through installation, doctor, offline demo, MCP, and dashboard verification.

Read the guide →

Bug reports

Include the version, operating system, reproduction steps, expected and actual results, and sanitized logs.

Open an issue →

Ideas and discussion

Share first-use feedback, data-source requests, and roadmap ideas in GitHub Discussions.

Open Discussions →

Public MCP checks

Open the service /health endpoint and confirm an OK response.
Connect the client to the HTTPS /mcp endpoint, not this static website.
Call get_public_capabilities or read_demo_dataset before diagnosing an upstream market-data failure.
Include the time, tool name, input category, and stable error code in a report. Never include credentials.

Security issues

Do not disclose vulnerabilities, leaked credentials, or access to non-public state in an issue or discussion. Follow the repository security policy.

Support boundary

Community maintenance does not provide investment decisions, return promises, managed trading, or emergency trading support. The public service does not connect to a live broker.