Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MERX - TRON Resource Exchange

NPM · MERX-MCP · 2 COMPONENTS · SCANNED SEP 23

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

Available components

remote · merx.exchange 80 npm · merx-mcp 51
0 this week 51 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 6 of 51 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package declared that it provides tools, but our sandbox run could not list them, so the captured schema is incomplete.Unverified
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Tool Safety0
  • Tool safety not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 3 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the MERX - TRON Resource Exchange MCP server?

MERX - TRON Resource Exchange runs locally as an npm package, launched with npx -y merx-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · merx-mcp

# add to Claude Code
claude mcp add exchange-merx-mcp -- npx -y merx-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "exchange-merx-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "merx-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "exchange-merx-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "merx-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add exchange-merx-mcp -- npx -y merx-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "exchange-merx-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "merx-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add exchange-merx-mcp --command npx --arg -y --arg merx-mcp
# ~/.hermes/config.yaml
mcp_servers:
  exchange-merx-mcp:
    command: "npx"
    args: ["-y", "merx-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "exchange-merx-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "merx-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add exchange-merx-mcp -t stdio -c npx -a -y merx-mcp
// mcp.json
{
  "mcpServers": {
    "exchange-merx-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "merx-mcp"
      ]
    }
  }
}
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.

  • 23 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 18 Sept 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

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 23 Sept 2026 · Analysed npm/merx-mcp@1.0.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 51 packages
Packages resolved 51
Stale 6
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

The sandbox run completed and this package exposed no tools.

Common questions

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 npm package (merx-mcp).

Is the MERX - TRON Resource Exchange MCP server safe to use?

MERX - TRON Resource Exchange scores 51 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. It declares no install or post-install scripts. 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 no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

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.

What licence is the MERX - TRON Resource Exchange MCP server under?

MERX - TRON Resource Exchange declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.