mcp-registry/io.github.hatgit/forex-gpt-mcp · v2.0.0
As of 2026-10-18 19:17 UTC, the Hatgit Forex Gpt MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 46 outages in 90 days, with a median recovery of 6 minutes.
AI-powered forex and crypto trading analysis with real-time data across 127+ instruments.
Claude Code
claude mcp add --transport http hatgit-forex-gpt-mcp-server https://mcp.forex-gpt.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"hatgit-forex-gpt-mcp-server": {
"type": "http",
"url": "https://mcp.forex-gpt.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 tool(s) have no description.
Describe what each tool does, when to use it and what it returns in one or two sentences. Models choose tools almost entirely from this text. How to fix →
69 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
255 parameter(s) across 53 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
Handshake + tools/list takes ~2,189 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.hatgit/forex-gpt-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.hatgit/forex-gpt-mcp"}) over MCP.
agent_start ~773 tokensagent_modify ~671 tokenstrade_limit_order ~528 tokenstrade_market_order ~473 tokensscan_market ~454 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.hatgit%2Fforex-gpt-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.hatgit%2Fforex-gpt-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hatgit%2Fforex-gpt-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hatgit%2Fforex-gpt-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.hatgit%2Fforex-gpt-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:81c10f549f00d55d…, first seen 2026-10-17, included at leaf 14598 of 23,164. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable communication servers · most reliable data servers · most reliable ml servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 19:17 UTC, the Hatgit Forex Gpt MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 46 outages in 90 days, with a median recovery of 6 minutes.
Hatgit Forex Gpt MCP server advertises 69 tools, including add_to_watchlist, agent_approve, agent_history, agent_link_telegram, agent_list_strategies.
Point your MCP client at this streamable-http endpoint: https://mcp.forex-gpt.ai/mcp
Glimind scanned all 69 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.