merx-mcp

Merx MCP Server

MERX gives AI agents tools for TRON resource rentals, blockchain queries, token transfers, swaps, and payment collection. It serves developers building agent workflows that need transaction cost estimates, resource provisioning, invoices, and address monitoring.

Server facts

merx-mcp

Project

Author
Hovsteder
License
Not specified

Tech

Runtime / language
Not specified
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
3
Last commit
Data as of

Tags

  • a2a
  • acp
  • agent payments
  • ai agents
  • blockchain
  • defi
  • energy
  • gasfree
  • mcp
  • stablecoin
  • sunswap
  • tron
  • usdc
  • usdd
  • usdt
  • x402

Overview

TRON resource management and agent payments come together in MERX’s MCP interface. Agents can compare energy and bandwidth offers by rental duration, estimate transaction costs, inspect wallet resources, and purchase missing capacity before a transfer. Order tracking lets a workflow check whether delegation has completed before continuing. Blockchain tools cover balances, transaction history, contract inspection, token transfers, and SunSwap V2 quotes and swaps. Read-only queries generally need no authentication, while resource orders use a MERX API key and transaction-signing tools require a TRON private key.

For payment workflows, agents register a TRON address, request token payments, issue invoices, and watch addresses for incoming transfers. The payment service covers USDT, USDC, and USDD, alongside x402 invoice payment support. Standing orders and persistent monitors support conditional actions and notifications, while natural-language policies can produce automation previews before application. Multi-step simulation provides resource and cost estimates, but execute_intent currently returns a plan rather than executing its steps. The resource_broadcast endpoint is also disabled by default in production, so workflows should distinguish available planning tools from restricted execution paths.

merx-mcp setup notes

  • merx-mcp records stdio only; confirm a network transport upstream before planning remote access.
  • merx-mcp has no recorded license; confirm reuse terms in its repository.

Related MCP servers