com.fxapis/mt5-insights
fxapis — MetaTrader 5 insights (read-only)
Is the fxapis MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.
Read-only MetaTrader 5 for AI agents: balances, positions, history and prices. Sign in with OAuth.
needs auth probed 2026-11-15 · unchanged since 2026-11-12 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Sign in to fxapis to connect (your MCP client ope- Endpoint
- https://api.fxapis.com/mcp/insights (streamable-http)
- Host
- api.fxapis.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.fxapis.com/mcp/insights registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server api.fxapis.com, PKCE S256, grants authorization_code, refresh_token.
Scopes accounts:read trading:read history:read.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://docs.fxapis.com/guides/mcp-read-only
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Other registry entries on api.fxapis.com.
- fxapis — MetaTrader 5 com.fxapis/mt5 · needs auth
Servers that mention insights.
- AdWeave — Meta Ads MCP Server ai.adweave/meta-ads-mcp · needs auth
- AI-Advisors ai.ai-advisors/mcp · needs auth
- Conveo ai.conveo/conveo · needs auth
- Magic Insights ai.magicinsights/insights · needs auth
- Mozark MCP Server ai.mozark/mcp · not found
- Reka ai.reka/mcp · alive
- ai.smithery/Artin0123-gemini-image-mcp-server · not found
- Time Machine ai.timeml/time-machine · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.