Connect any MCP client to MetaTrader 4/5 to read prices, manage positions, and place trades.
Dev & Codev1.0.0streamable-httpmcp.mtcontext.com repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 66ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo mt-mcp@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 73 tools e.g. "get_tick"; 73/73 described, 73/73 fully-typed schemas, median description 284 chars |
| latency | 10 / 10 | initialize round-trip 66ms |
| provenance | 15 / 15 | description present; repository linked; version 1.0.0; namespace io.github.mtcontext matches endpoint/repo |
Score 100/100 · latency 66ms · 73 tools · protocol access: open ⓘ
Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.
| Dimension | Metric | Status | Evidence | Source |
|---|---|---|---|---|
| security | sensitive_capabilities_declared | concern | 24 discovered tool(s) advertise potentially state-changing or privileged capabilities. Tool names: get_terminal_info, place_order, close_position, modify_position, cancel_order, partial_close, modify_order, close_all_positions, set_breakeven, reverse_position, calculate_lot_size, get_economic_calendar, get_rate_expectations, get_currency_strength, create_alert, list_alerts, set_equity_guard, set_prop_firm_rules, get_prop_firm_status, remove_prop_firm_rules. Classification is description-based and does not prove exploitability. Observed value: get_terminal_info, place_order, close_position, modify_position, cancel_order, partial_close, modify_order, close_all_positions, set_breakeven, reverse_position, calculate_lot_size, get_economic_calendar, get_rate_expectations, get_currency_strength, create_alert, list_alerts, set_equity_guard, set_prop_firm_rules, get_prop_firm_status, remove_prop_firm_rules Sample: n=24 | live_probe |
| security | authentication_boundary | observed | Live protocol probe observed auth_state=open. This describes discovery/access behavior; it is not by itself a vulnerability finding. Observed value: open | live_probe |
Machine-readable receipt: /api/trust/io.github.mtcontext/mtcontext.json
Claude Code:
claude mcp add --transport http mtcontext https://mcp.mtcontext.com/mcp/v1
Generic MCP client config:
{ "mcpServers": { "mtcontext": { "type": "http", "url": "https://mcp.mtcontext.com/mcp/v1" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/io.github.mtcontext/mtcontext · referral link https://mcpqueen.com/go/io.github.mtcontext/mtcontext (counts as “routed via the queen”).
Live operational-grade badge, re-probed continuously — not a security or data-quality certification. Put it in your README and link to the complete receipt:
[](https://mcpqueen.com/s/io.github.mtcontext/mtcontext)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-28 18:16 | A | 100 | 66ms |