Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

MERX - TRON Resource Exchange

by Hovstederversion 1.0.5i★ –iComputer or cloud
Registry nameexchange.merx/mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Search & AI memory
  • You need to fill in: MERX_API_KEY, TRON_PRIVATE_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: MERX_API_KEY, TRON_PRIVATE_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://merx.exchange/mcp/sse

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "merx": {
      "command": "npx",
      "args": [
        "-y",
        "merx-mcp"
      ],
      "env": {
        "MERX_API_KEY": "your-value",
        "TRON_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

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

Or run it on your computer

claude mcp add merx --env MERX_API_KEY=your-value --env TRON_PRIVATE_KEY=your-value -- npx -y merx-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "merx": {
      "url": "https://merx.exchange/mcp/sse"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "merx": {
      "command": "npx",
      "args": [
        "-y",
        "merx-mcp"
      ],
      "env": {
        "MERX_API_KEY": "your-value",
        "TRON_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "merx": {
      "type": "http",
      "url": "https://merx.exchange/mcp/sse"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "merx": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "merx-mcp"
      ],
      "env": {
        "MERX_API_KEY": "your-value",
        "TRON_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://merx.exchange/mcp/sse

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • MERX_API_KEY secret env
    API key from merx.exchange. Unlocks trading, balance, standing orders, and monitors.
  • TRON_PRIVATE_KEY secret env
    TRON wallet private key for signing transactions. Never sent to any server. Enables transfers, swaps, and contract calls.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain merx.exchange (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 5668 servers in this category
  • Published to the registry more recently than 8% of the other 5668 servers in this category
  • Basic checks equal to or better than 100% of the other 5668 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MERX - TRON Resource Exchange safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MERX_API_KEY, TRON_PRIVATE_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.5) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

MERX

https://MERX.exchange

TRON infrastructure for AI agents.

66 MCP tools. Energy market across 6 providers. USDT/USDC/USDD payments. x402 v2 facilitator on TRON mainnet.

Documentation | API Reference | MCP Server


Table of contents

  • What is MERX — TRON infrastructure for AI agents
  • The problem — why TRON had no agent layer until MERX
  • Platform overview — MCP, agent payment service, x402, GasFree, energy aggregator
  • Quick start — 4 paths (web, REST/SDK, Claude Code plugin, MCP)
  • What sets MERX apart — only complete agent stack on TRON
  • Architecture
  • API overview
  • MCP server
  • SDKs
  • Real-time data
  • Payment methods
  • Standing orders and monitors
  • Savings calculator
  • Error handling
  • Security
  • Tested on mainnet
  • Comparison with alternatives
  • Documentation
  • License

What is MERX

MERX is the infrastructure layer for AI agents and agentic networks on TRON. Where Stripe is infrastructure for web commerce and Cloudflare for the open web, MERX is the missing infrastructure layer that lets autonomous AI agents discover, transact, and operate on TRON without ever touching energy, bandwidth, or low-level blockchain mechanics.

The platform exposes one coherent stack: 66-tool MCP server, agent payment service for TRC-20 stablecoins, x402 v2 facilitator (the only TRON facilitator in the coinbase/x402 ecosystem registry), GasFree transfers via a MERX-deployed mainnet controller, dedicated TRON RPC node, A2A (Google, 7 skills) and ACP (BeeAI, 7 capabilities) protocol coverage, and a natural language Policy Engine powered by Anthropic Claude.

Underneath those agent surfaces sits an energy aggregator across 6 active providers (CatFee, Netts, TronSave, iTRX, PowerSun, TEM) that routes resource purchases to the cheapest source automatically -- so when an agent calls send(), MERX estimates the energy required, buys only the deficit, and broadcasts the transaction. The agent never holds TRX or thinks about energy.

Any AI agent running in Claude, LangChain, CrewAI, Vertex AI, AutoGen, or BeeAI can send payments and acquire resources on TRON through a single integration with MERX.

Three ways to plug an agent into MERX:

  • MCP server -- 66 tools for AI agents. Hosted SSE at https://merx.exchange/mcp/sse (zero install) or local stdio via npx merx-mcp. Works with Claude, GPT, Cursor, Windsurf, and any MCP-compatible client.
  • Claude Code plugin -- one-line install for Claude Code. Auto-registers the MCP server, ships 6 slash commands and a tron-agent-engineer sub-agent. See Hovsteder/merx-claude-plugin.
  • REST API + SDKs -- direct programmatic access for agents that aren't using MCP. JavaScript (merx-sdk v2.1 on npm), Python (merx-sdk v2.1 on PyPI), or raw HTTP against /api/v1/ (70+ versioned endpoints).

For human users, the web platform at merx.exchange remains available for manual energy trading, dashboard, deposits, and withdrawals -- but the platform is built primarily for agents.


The problem

AI agents will become the dominant transactional users of stablecoins, and TRON -- home to USDD, $86B+ USDT, USDC, and the dominant chain for retail USDT in Southeast Asia, Africa, and Latin America -- is already the largest USDT-native network in the world.

But TRON has no infrastructure designed for agents:

  • No agent-native payment service. Existing TRON wallets are built for human users with mouse clicks and seed-phrase backups, not for autonomous programs that need to register addresses, send TRC-20s, watch for incoming payments, and create invoices via REST.
  • Energy and bandwidth are a UX dead-end. Every smart contract call on TRON requires energy. Without energy, TRX tokens burn as fees -- a single USDT transfer burns 3-13 TRX (~$1-4) for cold receivers. Renting energy from a provider drops the cost to ~$0.10 -- a 94% reduction -- but every provider has a different price, different API, different duration tiers, and different failure modes. No agent can be expected to manage that.
  • No x402 facilitator on TRON before MERX. The x402 protocol has already processed $43.57M in agent-to-agent payments on Base, Solana, Stellar, and Ethereum. TRON was completely absent from the coinbase/x402 ecosystem registry until MERX. Agents that wanted to pay for TRON-hosted APIs in USDT had no standardized way to do it.
  • Three agent protocols, zero TRON integrations. MCP (Anthropic), A2A (Google), and ACP (BeeAI) are the three major agent communication protocols. Until MERX, none of them had a deployed, production-grade TRON server. AI agents in Claude, Vertex AI, or BeeAI literally could not see TRON.

MERX builds the missing layer. AI agents call one API, hold zero TRX, and get paid / pay / send / receive in USDT, USDC, or USDD on the world's largest USDT network.

Without MERXWith MERX
Agent has to manage energy + bandwidth manuallysend() estimates and provisions resources automatically
Agent has to hold TRX as gasGasFree transfers — agents send stablecoins from zero-TRX wallets
Agent has to integrate every energy provider's APIOne MERX API routes to the cheapest of 6 providers
No way to pay for TRON-hosted APIs in USDTx402 v2 facilitator with full USDT/USDC/USDD support
No A2A/ACP discovery on TRONAgent Card + Manifest live, 7 skills, 7 capabilities
Agent has to write its own MCP server for TRON66 tools, 30 prompts, 21 resources, hosted
Address watching means polling RPCwatch() with sub-3-second webhook delivery via ZMQ

Platform overview

ComponentDescription
MCP server66 tools, 30 prompts, 21 resources for AI agents. Hosted SSE at https://merx.exchange/mcp/sse (zero install) or local stdio. SEP-1649 server card. The largest TRON-native MCP server in production.
Claude Code pluginOne-line install: /plugin marketplace add Hovsteder/merx-claude-plugin. Auto-registers MCP, 6 slash commands, sub-agent.
Agent Payment Serviceagent.merx.exchange -- non-custodial REST API. register, send, receive, watch, invoice, batch, schedule, contacts. USDT live; USDD/USDC next sprint.
x402 v2 Facilitatorx402.merx.exchange -- only TRON facilitator in the coinbase/x402 ecosystem registry. Three settlement schemes (exact, exact_permit, exact_gasfree) for USDT, USDC, USDD on TRON mainnet plus USDC on Base.
GasFree Transfer ServiceMainnet controller TKjJ1r5XYqnLZmLakcP3knis7Lh6gm3qtR activated 2026-04-08. TIP-712 PermitTransfer for USDT/USDC/USDD. Agents send stablecoins from zero-TRX wallets.
A2A Protocol (Google)Agent Card at /.well-known/agent.json. 7 skills including compile_policy. Task-based execution with SSE streaming. Compatible with LangChain, CrewAI, Vertex AI, AutoGen, Mastra.
ACP Protocol (BeeAI)Manifest at /.well-known/agent-manifest.json. 7 capabilities matching A2A skills. Run-based execution with long-polling.
Policy EngineNatural language → standing orders, powered by Anthropic Claude Sonnet 4. Available as MCP tool, A2A skill, and REST endpoint.
Energy aggregatorReal-time price comparison across 6 active providers (CatFee, Netts, TronSave, iTRX, PowerSun, TEM). Routes orders to cheapest source. Underneath the agent surfaces.
Dedicated TRON RPC noderpc.merx.exchange, sub-5ms read latency, 13.7ms broadcast. Trial 1,000 free requests; paid tiers with energy-spend waiver.
REST API70+ versioned endpoints under /api/v1/. Idempotency-Key on POST. Standard error format.
WebSocketReal-time TRC-20 transfer stream and price updates at wss://merx.exchange/ws.
JavaScript SDKmerx-sdk v2.1 -- AgentModule + SwapModule + 4 base modules. TypeScript types included.
Python SDKmerx-sdk v2.1 -- same surface in snake_case.
x402 middlewaremerx-x402 v2.0.0 -- one-line Express integration for x402 v2.
Documentation38+ pages at merx.exchange/docs. API reference, MCP/A2A/ACP guides, x402 integration.

Quick start

Four paths depending on your use case. For AI agents, paths 3 and 4 are the primary surfaces. Path 1 (web) is for human operators; path 2 (REST/SDK) is for direct programmatic integration.

Path 1: Web platform (humans)

Go to merx.exchange. Sign in. Deposit TRX. Manage energy, agent API keys, and balance through the dashboard. No code required.

Path 2: REST API / SDK (programmatic)

Install the JavaScript SDK:

npm install merx-sdk

Use it in your application (replace merx_sk_your_key with your API key from merx.exchange):

import { MerxClient } from 'merx-sdk'

const merx = new MerxClient({ apiKey: 'merx_sk_your_key' })

// Get current prices from all providers const prices = await merx.prices.list() console.log(prices[0]) // { provider: "netts", price_sun: 22, available: 100000000 }

// Buy energy at best price const order = await merx.orders.create({ resource_type: 'ENERGY', amount: 65000, duration_sec: 300, target_address: 'TYourAddress...', }) console.log(order.status) // "FILLED" console.log(order.cost_trx) // 1.4311

Python:

from merx import MerxClient

merx = MerxClient(api_key="merx_sk_your_key")

prices = merx.prices.list() order = merx.orders.create( resource_type="ENERGY", amount=65000, duration_sec=300, target_address="TYourAddress..." )

curl (no SDK needed):

# Public -- no auth required

curl https://merx.exchange/api/v1/prices

Authenticated

curl -X POST https://merx.exchange/api/v1/orders \ -H "Authorization: Bearer merx_sk_your_key" \ -H "Content-Type: application/json" \ -d '{ "resource_type": "ENERGY", "amount": 65000, "duration_sec": 300, "target_address": "TYourAddress..." }'

Path 3: Claude Code plugin (one-line install)

If you're using Claude Code, this is the fastest path. The plugin auto-registers the hosted MCP server, ships 6 slash commands, and includes a tron-agent-engineer sub-agent specialized in agentic payment workflows on TRON.

/plugin marketplace add Hovsteder/merx-claude-plugin

/plugin install merx@merx

Then run /merx:setup to configure your MERX API key. Available commands:

CommandWhat it does
/merx:setupFirst-time setup: API key, connection test, capability tour
/merx:pricesLive TRON energy and bandwidth prices across all providers
/merx:buy-energyBuy energy via cheapest provider, delegated to a target address
/merx:balanceMERX prepaid balance, recent orders, free-tier usage

| /merx:tx | Look up a TRON transa

Only the beginning is shown; read the rest in the repo

Ask PopNx