mcp-registry/io.github.mtcontext/mtcontext · v1.0.0
Also listed as glama/mtcontext/mtcontext
As of 2026-10-26 18:52 UTC, the Mtcontext MCP server is up (it requires sign-in) with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.
Connect any MCP client to MetaTrader 4/5 to read prices, manage positions, and place trades.
Point your MCP client at this streamable-http endpoint: https://mcp.mtcontext.com/mcp/v1
73 of 73 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
73 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 →
173 parameter(s) across 56 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 →
17 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
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 →
Requires authentication; tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 56 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mtcontext%2Fmtcontext/fixes
{
"name": "calculate_lot_size",
"description": "Calculates the appropriate lot size for a trade based on account equity and risk parameters. Uses live account equity and symbol contract specs from the connected terminal. Returns the recommended lot size, risk amount in account currency, and pip value. Returns LOT_TOO_SMALL if the computed lots are below the symbol minimum. Available at Free+ tier (no analytics capability required).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"symbol",
"risk_percent",
"stop_loss_pips"
],
"properties": {
"symbol": {
"type": "string",
"maxLength": 20,
"minLength": 1
},
"risk_percent": {
"type": "number",
"maximum": 100,
"exclusiveMinimum": 0
},
"stop_loss_pips": {
"type": "number",
"exclusiveMinimum": 0
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "cancel_alert",
"description": "Cancels an active alert by alert_id (from create_alert or list_alerts). Returns ALERT_NOT_FOUND if the alert does not exist, already fired, or was already cancelled. Available at Pro+ tier.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"alert_id"
],
"properties": {
"alert_id": {
"type": "string",
"format": "uuid"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "cancel_order",
"description": "Cancels a pending (limit or stop) order by ticket. Defaults to dry_run=true — set dry_run=false to execute live. Returns ORDER_NOT_FOUND if the ticket is not in pending orders. Requires the `trade` capability and inp_AllowTrading=true on the EA.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"ticket"
],
"properties": {
"ticket": {
"type": "integer",
"exclusiveMinimum": 0
},
"dry_run": {
"type": "boolean",
"default": true
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}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.mtcontext/mtcontext"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.mtcontext/mtcontext"}) over MCP.
set_prop_firm_rules ~490 tokensset_equity_guard ~375 tokensget_indicator ~358 tokensbacktest_strategy ~345 tokensget_market_snapshot ~345 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.mtcontext%2Fmtcontext?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mtcontext%2Fmtcontext?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mtcontext%2Fmtcontext.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mtcontext%2Fmtcontext.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.mtcontext%2Fmtcontext?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:dfb4b988cfa9a8e6…, first seen 2026-10-17, included at leaf 8308 of 75,084. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable communication servers · most reliable other servers · most reliable data servers · most reliable files 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-26 18:52 UTC, the Mtcontext MCP server is up (it requires sign-in) with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.
Mtcontext MCP server advertises 73 tools, including backtest_strategy, calculate_lot_size, cancel_alert, cancel_order, check_order.
Point your MCP client at this streamable-http endpoint: https://mcp.mtcontext.com/mcp/v1
Glimind scanned all 73 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.