MERX - TRON Resource Exchange

REMOTE · MERX.EXCHANGE · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · merx.exchange 67 npm · merx-mcp 68

+4 this week 67 67 Trust /100

Trust breakdown (6 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 →

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 Usability83

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities20

Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · merx.exchange

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.exchange-merx-mcp]
url = "https://merx.exchange/mcp/sse"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "exchange-merx-mcp": {
      "type": "remote",
      "url": "https://merx.exchange/mcp/sse",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add exchange-merx-mcp --url https://merx.exchange/mcp/sse --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  exchange-merx-mcp:
    url: "https://merx.exchange/mcp/sse"

// mcp.json

{
  "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.

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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
26 Jul 26 63

First indexed and scored.

Show 7 earlier entries Hide earlier entries

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 3 Aug 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	4 Jun 2026	2 Sept 2026	ECDSA 256	ECDSA-SHA384	605b0e3ebe35d18cb617d90f31c96e3c3d8
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

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'; 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 https://api.merx.exchange wss://merx.exchange
x-content-type-options	nosniff
x-frame-options	DENY
referrer-policy	strict-origin-when-cross-origin
permissions-policy	geolocation=(), microphone=(), camera=()

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 · ~5,922 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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	63
27 Jul	63
28 Jul	64
29 Jul	65
30 Jul	65
31 Jul	65
1 Aug	66
2 Aug	66
3 Aug	67