MERX - TRON Resource Exchange

NPM · MERX-MCP · 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

+15 this week 68 68 Trust /100

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

Supply Chain Security91

No malware found by supply-chain analysis.Pass
CVE check failed: a known high-severity CVE affects ws 8.17.1, reached via tronweb > ethers > ws. A fixed version is available. View diagnostics → Fail
No install/post-install scripts declared.Pass
7 of 53 dependencies flagged as unhealthy. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 116 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability82

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 3537 tokens (~52/item across 68 items; 54 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.

npm · merx-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add exchange-merx-mcp -- npx -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"]

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

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.
2 Aug 26 +62
- CVE-2026-48779 affects this package: high ▼ security
- CVE-2026-45736 affects this package: high ▼ security
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Schema quality: unverified → good ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → 0.95 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
1 Aug 26 −21
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
31 Jul 26 +17
- 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 −15
- Malware scan: pass → unverified ▼ security
- Dependency health: unverified → partial ▲ functional
28 Jul 26 −29
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
27 Jul 26 53

First indexed and scored.

Show 4 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 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 2 findings

ID	CVE	Severity	Vector	Fix available
GHSA-58qx-3vcg-4xpx	CVE-2026-45736	medium	CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N	yes
GHSA-96hv-2xvq-fx4p	CVE-2026-48779	high	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H	yes

Dependencies 53 packages

53 packages in the resolved dependency tree · 7 stale.

MCP tools — 54 exposed · ~3,321 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

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.

withdraw ~87

Withdraw TRX or USDT from your Merx account to an external TRON address. Requires MERX_API_KEY.

Input Output Examples

Name	Type	Req	Description
address	string	yes	Destination TRON address (starts with T).
amount_trx	string	yes	Amount to withdraw in TRX (e.g. "100"). Converted to SUN internally.
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

27 Jul 3 Aug