Sato Hub
MCP

MERX MCP

TRON infrastructure MCP (hosted SSE + local stdio): energy/bandwidth prices, resource optimization, and TRC-20 stablecoin payments.

  • Sato Score84
  • ChainsTron
UnknownUnverifiedQuiet · 6mo ago

MERX MCP is an open-source MCP server on Tron, with last code activity on 2026-04-08 (Quiet). Latest release on 2026-04-02. Sato Score 84/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install MERX MCP →

Last commit Apr 8, 2026 · Last release Apr 2, 2026 · ★ 3

Listed from github.com/Hovsteder/merx-mcp on 2026-07-13. Install: not attempted. Evidence →

Next step

Watch MERX MCP

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on hovsteder/merx-mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

MERX MCP is a community MCP server for TRON infrastructure, listed in the MCP Registry, that runs either as a hosted SSE endpoint or locally over stdio. It exposes tools for TRON energy and bandwidth pricing, resource optimization, and TRC-20 stablecoin payment workflows. An agent builder plugs it in to give an agent TRON resource-cost awareness and stablecoin payment handling without integrating TRON APIs directly.

Sato Score

84/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
17/20
Interface verifiability
10/10
Docs & demo
6/10
Listing transparency & provenance
13/15
Independent verification
3/10

Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).

Sato Check

as of 2026-10-02
Does it take your key?
Asks for a key
Does your key leave?
Not observed
Can it move funds on its own?
13 actions
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from github.com/Hovsteder/merx-mcp on 2026-07-13. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedTronself-reportedmerx.exchangeas of 2026-10-15
Verification statusUnverified — not independently reviewedself-reportedgithub.com/Hovsteder/merx-mcpas of 2026-10-15
Recent activitylast release 2026-04-02 · last commit 2026-04-08observedgithub.com/Hovsteder/merx-mcp2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted by Sato Hubself-reportedgithub.com/Hovsteder/merx-mcpas of 2026-07-20
MCP endpoint answersanswered — 66 tools listedobservedmerx.exchange2026-10-15
Daily check record90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Takes your keyasks for a private key or seed phrasedeclaredsatohub.aias of 2026-10-02
Key leaves the machinenot observed during install and start-uplater or triggered code paths are not coveredobservedsatohub.ai2026-10-02
Moves funds on its own13 actions can sign or send fundstracedsatohub.ai2026-10-02
Creator profilehttps://github.com/Hovstederconfidence 0.80self-reportedgithub.com/Hovsteder/merx-mcpas of 2026-07-14
Deploys asnpmconfidence 0.75self-reportedgithub.com/Hovsteder/merx-mcpas of 2026-07-14
Works withClaude, Cursorconfidence 0.65self-reportedgithub.com/Hovsteder/merx-mcpas of 2026-07-14
Docshttps://merx.exchange/docsconfidence 0.85self-reportedgithub.com/Hovsteder/merx-mcpas of 2026-07-14
Sato Score84/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — as documented by the project, not run by us

Runtime: Node.js 18+ (for local stdio mode)

npm install -g merx
npx merx-mcp

You supply: MERX_API_KEY (authentication API key from merx.exchange account), TRON_PRIVATE_KEY (optional, 64-char hex — risk: enables write/trading operations, controls funds)

MCP invocation: hosted SSE: https://merx.exchange/mcp/sse (22 read-only tools, no key needed); local: npx merx-mcp

Read from the project’s own docs as of 2026-07-20. What a deploy spec is →

Tool inventory — 66 tools, probed live 2026-10-15

  • get_prices — Get current energy and bandwidth prices from all Merx providers, sorted by best (minimum) price across all duration tiers. Each provider lists ALL its duration tiers (5min/1h/1d/7d/30d etc) — short re
  • get_best_price — Quick lookup of the single cheapest provider for a resource type, with optional minimum amount filter. CAVEAT: this returns a single representative price per provider, not broken down by duration tier
  • analyze_prices — Market price analysis with trends and recommendations. No auth required.
  • get_price_history — Historical price snapshots. No auth required.
  • compare_providers — Side-by-side provider comparison with prices and availability. No auth required.
  • estimate_transaction_cost — Estimate cost of a TRON transaction BEFORE sending. Aliases: estimate_cost, calculate_cost, transaction_cost, energy_cost, transfer_cost. Calculate exactly how much energy, bandwidth, and TRX a TRON t
  • check_address_resources — Check energy, bandwidth, and TRX balance for any TRON address. No auth required.
  • create_order — Buy energy or bandwidth at the Merx market quote, fulfilled by PowerSun. Confirmed Merx funds and API key required; no commission.
  • get_order — Get order status by UUID. Aliases: get_order_status, check_order, order_status, order_details, fetch_order. Check the status and fill details of an existing order by its UUID. Returns current status (
  • list_orders — List recent orders with optional status filter. Auth required.
  • ensure_resources — Declarative resource provisioning. Checks current resources on target address and purchases only what is missing. Auth required.
  • wait_for_delegation — 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/ban
  • get_balance — Get your Merx account balance (TRX, USDT, locked). Requires MERX_API_KEY.
  • get_deposit_info — Get your Merx deposit address and memo. Requires MERX_API_KEY.
  • get_transaction_history — Get your Merx account transaction history. Requires MERX_API_KEY.
  • explain_concept — Explain a TRON or Merx concept in plain language. Hardcoded topics (exact match): energy, bandwidth, staking, delegation, sun_units, burn_vs_rent, merx_routing, provider_types. The lookup is fuzzy — s
  • suggest_duration — Recommend a rental duration based on your use case. No authentication required.
  • calculate_savings — Calculate savings from renting energy vs burning TRX. No authentication required.
  • list_providers — List all Merx providers with types, durations, and availability. No authentication required.
  • get_account_info — Inspect any TRON address. Aliases: check_address, get_address_info, get_wallet_info, address_info, account_status. Read the full on-chain state of ANY TRON address (does not have to be your own): TRX
  • get_trx_balance — Quick TRX balance for a TRON address. No auth required.
  • get_trc20_balance — Get TRC-20 token balance for an address. Supports symbol (USDT, USDC) or contract address. No auth required.
  • get_transaction — Look up a transaction by ID on TRON. No auth required.
  • get_block — Get TRON block info by number (or latest if omitted). No auth required.
  • get_chain_parameters — Get TRON network parameters (energy fee, bandwidth cost, etc.) with Merx price comparison. No auth required.
  • convert_address — Convert TRON address between base58 (T...) and hex (41...) formats. No auth required.
  • get_trx_price — Get current TRX price from CoinGecko. No auth required.
  • validate_address — Validate a TRON address format and check on-chain status. No auth required.
  • search_transaction_history — Get on-chain transaction history for a TRON address. No auth required.
  • transfer_trx — Send TRX to an address. Checks bandwidth, buys via Merx if needed. Signs and broadcasts on-chain. Requires TRON_PRIVATE_KEY.
  • transfer_trc20 — Transfer TRC-20 tokens with automatic energy optimization. Signs and broadcasts on-chain. Requires TRON_PRIVATE_KEY.
  • approve_trc20 — Approve TRC-20 spending allowance. Signs and broadcasts on-chain. Requires TRON_PRIVATE_KEY.
  • get_token_info — Get TRC-20 token metadata: name, symbol, decimals, total supply. No auth required.
  • read_contract — Call a view/pure function on a TRON smart contract. No auth or private key required.
  • estimate_contract_call — Estimate energy and bandwidth cost for a smart contract call. Compares rental vs burn cost. No auth required.
  • call_contract — Execute a state-changing smart contract function. Estimates resources, buys via Merx if needed. Requires TRON_PRIVATE_KEY and TRON_ADDRESS.
  • get_contract_info — 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
  • get_swap_quote — Get a real swap quote from SunSwap V2. No auth required.
  • execute_swap — Execute a token swap on SunSwap V2. Requires TRON_PRIVATE_KEY.
  • get_token_price — Get token price via SunSwap quote + CoinGecko USD rate. No auth required.
  • create_account — Create a new Merx account, generate an API key, and get deposit info. No auth needed.
  • login — Log in to an existing Merx account. No MERX_API_KEY needed.
  • set_api_key — Set your Merx API key for this session. Unlocks all authenticated tools (trading, balance, orders). Use this if you already have an API key.
  • set_private_key — 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
  • deposit_trx — Deposit TRX to your Merx account. Requires MERX_API_KEY + TRON_PRIVATE_KEY.
  • enable_auto_deposit — Configure automatic top-up when balance drops below a threshold. The configuration lives ONLY in the current MCP session — it is held in memory by the MCP server process and is lost on server restart,
  • pay_invoice — 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 A
  • create_paid_order — Create a zero-registration order via x402 pay-per-use. Requires TRON_PRIVATE_KEY.
  • execute_intent — Plan a multi-step operation (transfer, swap, buy resources, etc) and return a cost estimate, total energy/bandwidth needed, and the cheapest resource acquisition strategy. NOTE: actual on-chain execut
  • simulate — 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
  • create_standing_order — Create a server-side standing order with trigger-based automation. Auth required.
  • list_standing_orders — List all standing orders with optional status filter. Auth required.
  • get_standing_order — Get full details of a single standing order by its UUID. Returns trigger config, action params, budget, executions count, and status. Auth required (API key).
  • cancel_standing_order — 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).
  • create_monitor — Create a persistent server-side monitor that fires notifications when a condition is met. Four monitor types: delegation_expiry (warns when leased energy is about to expire so you can re-rent), balanc
  • list_monitors — List all monitors you created with create_monitor, optionally filtered by status (ACTIVE/CANCELLED). Each row shows the full monitor UUID (pass to cancel_monitor), monitor type, target address, and st
  • cancel_monitor — Cancel an active monitor by its UUID. The monitor stops firing notifications. Auth required (API key).
  • withdraw — 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 curr
  • compile_policy — Convert a natural language energy management policy into MERX automation. Creates standing orders and monitors based on your instructions. Examples: - "Keep 500k energy on my wallet, buy when price i
  • resource_broadcast — 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
  • register_agent — 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 a
  • request_payment — 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 hum
  • lookup_invoice — Look up a MERX invoice. Shows amount, recipient, token, and status. Agent must sign and broadcast the transfer separately (non-custodial).
  • create_invoice — Create an invoice for another agent or human to pay. Returns payment URL, address, and QR code. Payment is detected automatically via ZeroMQ (<3 seconds).
  • watch_address — 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.
  • agent_status — Get a snapshot of your agent payment service: registered TRON address, count of pending payment requests (request_payment), active address watches (watch_address), and outstanding invoices (create_inv
Answers a handshake
yes · 2026-10-15
Answers a call
yes — get_prices returned in 151 ms

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Observed record — 91 daily checks since 2026-07-17

100%of 91 checks since 2026-07-17 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
66
from the server's own tools/list · 29/30 days
Sato Score
84
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Tron
Agent types
MCP Server
Open source
Yes
Deploys as
npm
Works with
Claude, Cursor
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#tron#trc-20#stablecoin#payments#mcp
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to MERX MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Jul 20, 2026
    Edited: mcp endpoint url
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 19, 2026
    Edited: mcp endpoint url
  4. Jul 19, 2026
    Sato Score tier: Medium → High
    Score 55 → 80.
  5. Jul 18, 2026
    Sato Hub began tracking this listing
  6. Jul 14, 2026
    Enriched: deployment options, supported integrations
  7. Jul 14, 2026
    Auto-enriched: creator profile url, docs url
  8. Jul 14, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about MERX MCP

Is MERX MCP open source?
Yes. MERX MCP is open source under the MIT license; the repository is https://github.com/Hovsteder/merx-mcp. Checked as of 2026-10-15.
Which chains does MERX MCP support?
MERX MCP lists support for Tron as of 2026-10-15.
Is MERX MCP still maintained?
The most recent code activity Sato Hub observed was on 2026-04-08 (last commit 2026-04-08, last release 2026-04-02), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run MERX MCP?
Node.js 18+ (for local stdio mode). Install: npm install -g merx. Entry: npx merx-mcp. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (hosted SSE: https://merx.exchange/mcp/sse (22 read-only tools, no key needed); local: npx merx-mcp).
Is MERX MCP verified on Sato Hub?
Sato Hub holds one earned check for MERX MCP: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 84 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "MERX MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/merx-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.