Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MERX - TRON Resource Exchange

REMOTE · MERX.EXCHANGE · 2 COMPONENTS

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

0 this week 79 Trust /100

Last scanned (18 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Recent critical change

Authorization (3 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 6239 tokens (~77/item across 80 items; 66 tools + 14 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 4 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 67 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97.

  • 10 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 97 to 93.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97.

  • 8 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 97 to 93.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Oct 26 0
    • Tool “set_private_key” rewrote its description, which is the text the model reads security
    • Tool “enable_auto_deposit” rewrote its description, which is the text the model reads security
  • 23 Oct 26 79
    • A breaking change shipped without a version bump: still 2.0.0 ▼ security
    • Tool “compare_providers” rewrote its description, which is the text the model reads security
    • Tool “get_best_price” rewrote its description, which is the text the model reads security
    • Tool “get_prices” rewrote its description, which is the text the model reads security
    • Tool “suggest_duration” rewrote its description, which is the text the model reads security
    • “create_order” added a required parameter “idempotency_key”, so existing callers break ▼ functional
    • “suggest_duration” added a required parameter “target_address”, so existing callers break ▼ functional
    • “calculate_savings” added a required parameter “target_address”, so existing callers break ▼ functional
    • “get_best_price” added a required parameter “duration”, so existing callers break ▼ functional
    • “get_best_price” added a required parameter “target_address”, so existing callers break ▼ functional
    • “get_best_price” made “amount” required, so existing callers break ▼ functional
    • Resource “Best Prices” was removed ▼ functional
    • New resource “Executable Quote Help” functional
    • “get_prices” added an optional parameter “amount” cosmetic
    • “get_prices” added an optional parameter “target_address” cosmetic
    • “create_order” reworded the description of “amount” cosmetic
    • “create_order” reworded the description of “duration_sec” cosmetic
    • “create_order” reworded the description of “max_price_sun” cosmetic
    • “ensure_resources” reworded the description of “duration_sec” cosmetic
    • “get_prices” reworded the description of “duration” cosmetic
  • 21 Oct 26 0
    • Tool “create_order” rewrote its description, which is the text the model reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://merx.exchange/mcp/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=merx.exchange CN=YE2,O=Let's Encrypt,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA384 606529321092cb14ae29dfe8390b0fa2dab
SANs: agent.merx.exchange, merx.exchange, rpc.merx.exchange, www.merx.exchange, x402.merx.exchange
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of merx.exchange. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
exchange. DS published 5011 8 Verified
merx.exchange. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://merx.exchange wss://merx.exchange; frame-src https://challenges.cloudflare.com
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://merx.exchange/mcp/sse Verified 200
http (plaintext) http://merx.exchange/mcp/sse HTTPS enforced 301 https://merx.exchange/mcp/sse
MCP tools · 66 exposed · ~6,021 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
pay_invoice ~45

Unavailable legacy resource-invoice payment. No transaction is sent. Fund your personal Merx account and use quoted resource orders instead.

NameTypeReqDescription
invoice_idstringyesLegacy invoice ID

No output schema declared.

No examples provided.

read_contract ~73

Call a view/pure function on a TRON smart contract. No auth or private key required.

NameTypeReqDescription
contract_addressstringyesContract TRON address.
function_selectorstringyesFunction signature, e.g. "balanceOf(address)".
parameterstring–ABI-encoded parameter hex (optional).

No output schema declared.

No examples provided.

register_agent ~128

Register your TRON address as an agent on agent.merx.exchange. Required ONCE before using request_payment, create_invoice, watch_address, agent_status, or any other agent payment tool. Pass the TRON address you want to use as the on-chain identity for this API key. Idempotent — calling twice with the same key returns the existing registration. Auth required (API key).

NameTypeReqDescription
labelstring–Optional human-readable label (max 64 chars)
tron_addressstringyesYour TRON address (T...) that will receive payments and act as the agent identity.

No output schema declared.

No examples provided.

request_payment ~160

Create a TRC20 payment request on TRON (USDT, USDC, USDD, or any TRC20). Returns a payment address. Fires webhook when payment arrives (<3 seconds). Use for receiving payments from other agents or humans. Requires agent registration first — call register_agent if you get AGENT_NOT_REGISTERED error.

NameTypeReqDescription
amount_usdtstringyesAmount in token units (e.g. "5.00")
descriptionstring–What this payment is for
timeout_secondsnumber–Wait timeout (10-3600, default 300)
tolerance_pctnumber–Amount tolerance % (default 0 = exact)
webhook_urlstring–URL to notify on payment (optional)

No output schema declared.

No examples provided.

resource_broadcast ~178

Broadcast a signed TRON transaction with automatic energy optimization. If the target address lacks sufficient energy, MERX purchases the deficit at the best market price before broadcasting. One call: estimate, buy energy, wait for delegation, broadcast. Requires MERX_API_KEY with the "broadcast" scope, and a pre-signed transaction. Returns txid on success, refunds on timeout. NOTE: This endpoint is currently behind a feature flag and disabled by default in production. If you get a 503 MAINTENANCE error, use the manual flow instead: call ensure_resources to provision energy, then sign and broadcast the transaction with your own TronWeb client.

NameTypeReqDescription
signed_txstringyesHex-encoded signed TRON transaction
target_addressstringyesTRON address that will execute the transaction (must match TX sender)

No output schema declared.

No examples provided.

search_transaction_history ~62

Get on-chain transaction history for a TRON address. No auth required.

NameTypeReqDescription
addressstringyesTRON address.
limitnumber–Max results (default: 20).
typestring–Transaction type filter (default: all).

No output schema declared.

No examples provided.

set_api_key ~60

Set your Merx API key for this session. Unlocks all authenticated tools (trading, balance, orders). Use this if you already have an API key.

NameTypeReqDescription
api_keystringyesYour Merx API key (starts with sk_live_)

No output schema declared.

No examples provided.

set_private_key ~86

Set your TRON private key for this session. Address is derived automatically. Enables write tools: transfer_trx, transfer_trc20, approve_trc20, execute_swap, deposit_trx. Key stays in the MCP process; when using a hosted MCP server, that server receives the key.

NameTypeReqDescription
private_keystringyesYour TRON private key (64 hex characters)

No output schema declared.

No examples provided.

simulate ~110

Dry-run a multi-step operation (transfer, swap, buy resources, etc) without sending anything on-chain. Returns per-step energy and bandwidth estimates plus a total TRX cost. Use this to preview a plan before committing — for example, before transferring USDT to multiple recipients you can simulate to see the total energy cost. No auth required.

NameTypeReqDescription
resource_strategystring–Resource acquisition strategy (default: batch_cheapest).
stepsarrayyesArray of { action, params } steps to simulate.

No output schema declared.

No examples provided.

suggest_duration ~70

Recommend a supported duration and return the executable MERX quote and quoted provider for a target address.

NameTypeReqDescription
target_addressstringyesTRON recipient address required for an executable offer.
transaction_countnumber–Expected number of transactions (optional).
use_casestringyesYour intended use case.

No output schema declared.

No examples provided.

transfer_trc20 ~109

Transfer TRC-20 tokens with automatic energy optimization. Signs and broadcasts on-chain. Requires TRON_PRIVATE_KEY.

NameTypeReqDescription
amountstringyesAmount to transfer (human-readable).
resource_operation_idstring–Optional stable ID for resource purchases. Reuse on retries; this does not make the token transfer itself idempotent.
to_addressstringyesRecipient TRON address.
tokenstringyesToken symbol (USDT, USDC) or contract address.

No output schema declared.

No examples provided.

transfer_trx ~97

Send TRX to an address. Checks bandwidth, buys via Merx if needed. Signs and broadcasts on-chain. Requires TRON_PRIVATE_KEY.

NameTypeReqDescription
amount_trxstringyesAmount of TRX to send.
resource_operation_idstring–Optional stable ID for resource purchases. Reuse on retries; this does not make the token transfer itself idempotent.
to_addressstringyesRecipient TRON address.

No output schema declared.

No examples provided.

validate_address ~36

Validate a TRON address format and check on-chain status. No auth required.

NameTypeReqDescription
addressstringyesTRON address to validate.

No output schema declared.

No examples provided.

wait_for_delegation ~149

Block until an order reaches a terminal state (FILLED, PARTIAL, FAILED, or CANCELLED) by polling get_order at fixed intervals. Use this right after create_order when you need to confirm the energy/bandwidth has actually been delegated on-chain before sending the next transaction. Returns the final order details including the on-chain delegation tx hash. Auth required.

NameTypeReqDescription
order_idstringyesThe order UUID returned by create_order.
poll_interval_secnumber–How often to check status in seconds (default: 3, min: 1).
timeout_secnumber–Maximum time to wait in seconds (default: 60, max: 300).

No output schema declared.

No examples provided.

watch_address ~127

Watch any TRON address for TRC20 transfers (USDT, USDC, USDD, or any token). Fires webhook on each matching transfer. Persistent - runs 24/7 even when conversation ends.

NameTypeReqDescription
addressstringyesTRON address to watch (T...)
event_typesarray–Event types to watch
min_amount_usdtstring–Minimum amount filter (default "0")
ttl_hoursnumber–Watch duration in hours (1-720, default 24)
webhook_urlstringyesWebhook URL for notifications

No output schema declared.

No examples provided.

withdraw ~216

Withdraw TRX or USDT from your Merx account to an external TRON address. The "amount" parameter is interpreted in the currency specified by "currency" — i.e. for currency=TRX it is TRX units, for currency=USDT it is USDT units. (The legacy parameter "amount_trx" is still accepted as an alias for backwards compatibility, but is misleading when currency is USDT — prefer "amount" in new code.) Requires MERX_API_KEY.

NameTypeReqDescription
addressstringyesDestination TRON address (starts with T).
amountstring–Amount to withdraw, in units of the chosen currency. E.g. "100" with currency=TRX = 100 TRX, "100" with currency=USDT = 100 USDT.
amount_trxstring–DEPRECATED alias for "amount" — kept for backwards compatibility. Pass "amount" instead in new code.
currencystring–Currency to withdraw. Default: TRX.

No output schema declared.

No examples provided.

Install

How do I install the MERX - TRON Resource Exchange MCP server?

MERX - TRON Resource Exchange is a hosted endpoint at https://merx.exchange/mcp/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · merx.exchange

# add to Claude Code
claude mcp add --transport http exchange-merx-mcp 'https://merx.exchange/mcp/sse'
Common questions

What is the MERX - TRON Resource Exchange MCP server?

MERX - TRON Resource Exchange is an MCP server listed in the public MCP registry as exchange.merx/mcp. TRON energy exchange for AI agents. 54 tools, 30 prompts, 21 resources. A2A + ACP. This page covers its hosted endpoint (https://merx.exchange/mcp/sse).

Is the MERX - TRON Resource Exchange MCP server safe to use?

MERX - TRON Resource Exchange scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MERX - TRON Resource Exchange MCP server expose?

MERX - TRON Resource Exchange exposes 66 tools: get_prices, get_best_price, analyze_prices, get_price_history, compare_providers, and 61 more. Their descriptions and schemas cost roughly 6,021 tokens of context every time the server is loaded.

Does the MERX - TRON Resource Exchange MCP server require authentication?

No. We connected to MERX - TRON Resource Exchange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MERX - TRON Resource Exchange MCP server still maintained?

MERX - TRON Resource Exchange is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the MERX - TRON Resource Exchange MCP server?

VerifyMCP ran 13 checks on MERX - TRON Resource Exchange, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.