Is the Merx MCP server down?

mcp-registry/exchange.merx/mcp · v2.0.0

As of 2026-10-26 13:09 UTC, the Merx MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 7 minutes.

TRON energy exchange for AI agents. 54 tools, 30 prompts, 21 resources. A2A + ACP.

claude mcp add --transport http merx-mcp-server https://merx.exchange/mcp/sse

{
  "mcpServers": {
    "merx-mcp-server": {
      "type": "http",
      "url": "https://merx.exchange/mcp/sse"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (81/100)

What to fix (6)

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fexchange.merx%2Fmcp/fixes

{
  "name": "cancel_monitor",
  "description": "Cancel an active monitor by its UUID. The monitor stops firing notifications. Auth required (API key).",
  "inputSchema": {
    "type": "object",
    "required": [
      "monitor_id"
    ],
    "properties": {
      "monitor_id": {
        "type": "string",
        "description": "Monitor UUID to cancel."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

{
  "name": "cancel_standing_order",
  "description": "Cancel a standing order by its UUID. The order is moved to CANCELLED status and will not trigger again. Already-executed actions are NOT reversed. Auth required (API key).",
  "inputSchema": {
    "type": "object",
    "required": [
      "order_id"
    ],
    "properties": {
      "order_id": {
        "type": "string",
        "description": "Standing order UUID to cancel."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

{
  "name": "get_contract_info",
  "description": "Get on-chain metadata for a TRON smart contract: existence check, owner address, energy origin, code hash, contract name (if set), ABI entries count. Use this to check whether an address is a contract before calling read_contract or estimate_contract_call. For TRC20-specific metadata (name, symbol, decimals, totalSupply) use get_token_info instead. No auth required.",
  "inputSchema": {
    "type": "object",
    "required": [
      "address"
    ],
    "properties": {
      "address": {
        "type": "string",
        "description": "Contract TRON address (T...)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

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/exchange.merx/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/exchange.merx/mcp"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.92% uptime over 30 days.

Largest tool definitions

• create_monitor ~396 tokens
• estimate_transaction_cost ~357 tokens
• create_order ~326 tokens
• create_standing_order ~303 tokens
• withdraw ~292 tokens

Static 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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fexchange.merx%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fexchange.merx%2Fmcp?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fexchange.merx%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fexchange.merx%2Fmcp.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fexchange.merx%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fexchange.merx%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5c851fe99e32a2ab…, first seen 2026-10-22, included at leaf 47115 of 73,051. Version history · verify what your client received.

Tools (66)

• agent_status
• analyze_prices
• approve_trc20
• calculate_savings
• call_contract
• cancel_monitor
• cancel_standing_order
• check_address_resources
• compare_providers
• compile_policy
• convert_address
• create_account
• create_invoice
• create_monitor
• create_order
• create_paid_order
• create_standing_order
• deposit_trx
• enable_auto_deposit
• ensure_resources
• estimate_contract_call
• estimate_transaction_cost
• execute_intent
• execute_swap
• explain_concept
• get_account_info
• get_balance
• get_best_price
• get_block
• get_chain_parameters
• get_contract_info
• get_deposit_info
• get_order
• get_price_history
• get_prices
• get_standing_order
• get_swap_quote
• get_token_info
• get_token_price
• get_transaction
• get_transaction_history
• get_trc20_balance
• get_trx_balance
• get_trx_price
• list_monitors
• list_orders
• list_providers
• list_standing_orders
• login
• lookup_invoice
• pay_invoice
• read_contract
• register_agent
• request_payment
• resource_broadcast
• search_transaction_history
• set_api_key
• set_private_key
• simulate
• suggest_duration
• transfer_trc20
• transfer_trx
• validate_address
• wait_for_delegation
• watch_address
• withdraw

Compare: most reliable finance servers · most reliable other servers · most reliable blockchain servers · most reliable data servers · most reliable code servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Merx MCP server down right now?

As of 2026-10-26 13:09 UTC, the Merx MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Merx MCP server provide?

Merx MCP server advertises 66 tools, including agent_status, analyze_prices, approve_trc20, calculate_savings, call_contract.

How do I install Merx MCP server?

Point your MCP client at this streamable-http endpoint: https://merx.exchange/mcp/sse

Is the Merx MCP server safe to connect to an AI agent?

Glimind scanned all 66 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.

Operator of Merx MCP server?

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.