MERX - TRON Resource Exchange
REMOTE · MERX.EXCHANGE · 2 COMPONENTS · SCANNED SEP 23
TRON energy exchange for AI agents. 54 tools, 30 prompts, 21 resources. A2A + ACP.
Available components
Recent critical change
Authorization (3 Sept 2026). See the changelog before you install this server.
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (transfer_trx). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 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 6138 tokens (~76/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 7 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
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
claude mcp add --transport http exchange-merx-mcp 'https://merx.exchange/mcp/sse'
{
"mcpServers": {
"exchange-merx-mcp": {
"url": "https://merx.exchange/mcp/sse"
}
}
} {
"servers": {
"exchange-merx-mcp": {
"type": "http",
"url": "https://merx.exchange/mcp/sse"
}
}
} [mcp_servers.exchange-merx-mcp] url = "https://merx.exchange/mcp/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"exchange-merx-mcp": {
"type": "remote",
"url": "https://merx.exchange/mcp/sse",
"enabled": true
}
}
} openclaw mcp add exchange-merx-mcp --url 'https://merx.exchange/mcp/sse' --transport streamable-http
mcp_servers:
exchange-merx-mcp:
url: "https://merx.exchange/mcp/sse" {
"McpServers": {
"exchange-merx-mcp": {
"Transport": "http",
"Url": "https://merx.exchange/mcp/sse"
}
}
} assistant mcp add exchange-merx-mcp -t streamable-http -u 'https://merx.exchange/mcp/sse'
{
"mcpServers": {
"exchange-merx-mcp": {
"type": "http",
"url": "https://merx.exchange/mcp/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Sept 26 0
- Authorization: unverified → fail ▼ critical
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: fail → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Score status: failed → scored ▲ functional
- 2 Sept 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 79
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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
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 23 Sept 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 | 3 Aug 2026 | 1 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 627dc0113789170312c49251ec1aef9a1bb |
| SANs: admin.merx.exchange, 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. | present | 46084 | 8 | Verified |
| merx.exchange. | absent | 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 |
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 →
pay_invoice ~135
Pay an x402 invoice by signing and broadcasting a TRX transfer to the invoice address, then verifying the payment with the facilitator. x402 (Coinbase + Cloudflare HTTP 402 standard) is the protocol AI agents use to pay APIs per call. Use this when you receive an invoice_id from a paywalled service or another agent. REQUIRES: TRON_PRIVATE_KEY in env (use set_private_key first) AND a valid invoice_id from create_invoice or x402 challenge response. The transfer is signed locally — your private key never leaves the MCP process.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | Invoice ID to pay |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_address | string | yes | Contract TRON address. |
| function_selector | string | yes | Function signature, e.g. "balanceOf(address)". |
| parameter | string | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Optional human-readable label (max 64 chars) |
| tron_address | string | yes | Your 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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usdt | string | yes | Amount in token units (e.g. "5.00") |
| description | string | – | What this payment is for |
| timeout_seconds | number | – | Wait timeout (10-3600, default 300) |
| tolerance_pct | number | – | Amount tolerance % (default 0 = exact) |
| webhook_url | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| signed_tx | string | yes | Hex-encoded signed TRON transaction |
| target_address | string | yes | TRON 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | TRON address. |
| limit | number | – | Max results (default: 20). |
| type | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your Merx API key (starts with sk_live_) |
No output schema declared.
No examples provided.
set_private_key ~77
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 local - never sent to Merx servers.
| Name | Type | Req | Description |
|---|---|---|---|
| private_key | string | yes | Your 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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource_strategy | string | – | Resource acquisition strategy (default: batch_cheapest). |
| steps | array | yes | Array of { action, params } steps to simulate. |
No output schema declared.
No examples provided.
suggest_duration ~48
Recommend a rental duration based on your use case. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction_count | number | – | Expected number of transactions (optional). |
| use_case | string | yes | Your intended use case. |
No output schema declared.
No examples provided.
transfer_trc20 ~77
Transfer TRC-20 tokens with automatic energy optimization. Signs and broadcasts on-chain. Requires TRON_PRIVATE_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to transfer (human-readable). |
| to_address | string | yes | Recipient TRON address. |
| token | string | yes | Token symbol (USDT, USDC) or contract address. |
No output schema declared.
No examples provided.
transfer_trx ~65
Send TRX to an address. Checks bandwidth, buys via Merx if needed. Signs and broadcasts on-chain. Requires TRON_PRIVATE_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_trx | string | yes | Amount of TRX to send. |
| to_address | string | yes | Recipient 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | TRON 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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order UUID returned by create_order. |
| poll_interval_sec | number | – | How often to check status in seconds (default: 3, min: 1). |
| timeout_sec | number | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | TRON address to watch (T...) |
| event_types | array | – | Event types to watch |
| min_amount_usdt | string | – | Minimum amount filter (default "0") |
| ttl_hours | number | – | Watch duration in hours (1-720, default 24) |
| webhook_url | string | yes | Webhook 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Destination TRON address (starts with T). |
| amount | string | – | Amount to withdraw, in units of the chosen currency. E.g. "100" with currency=TRX = 100 TRX, "100" with currency=USDT = 100 USDT. |
| amount_trx | string | – | DEPRECATED alias for "amount" — kept for backwards compatibility. Pass "amount" instead in new code. |
| currency | string | – | Currency to withdraw. Default: TRX. |
No output schema declared.
No examples provided.
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 80 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 5,922 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 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.