Trade Router MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to TradeRouter locally signed Solana swaps and orders: Do signing and spend limits remain local, and are trading-risk caveats preserved without repeating the publisher's blanket safety claim?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Non-custodial Solana swap/order execution for agents with local signing and dry-run support.

What we know

TradeRouter MCP is a thin client over its REST/WebSocket engine for swaps, holdings, market data, limit/TWAP/trailing/combo orders and MEV-protected transaction submission. Wallet keys remain local to the MCP process.

Maintenance / activity evidence

@traderouter/trade-router-mcp 1.0.13 published 2026-04-27T08:24:16.201Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Wallet read plus real swap/order execution within wallet balance. Writes: Sign/submit swaps; Create/cancel limit/TWAP/trailing/combo orders.
Local Solana private key.
Sensitive access: Wallet private key, Wallet balances, Trading strategy

Direct financial execution. Use a dedicated wallet, dry-run first, explicit slippage/amount limits.
Write actions move real assets and can be irreversible.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do signing and spend limits remain local, and are trading-risk caveats preserved without repeating the publisher's blanket safety claim?

The bounded review of the publisher's documented TradeRouter locally signed Solana swaps and orders and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Direct financial execution. Use a dedicated wallet, dry-run first, explicit slippage/amount limits.
Wallet read plus real swap/order execution within wallet balance.
Local Solana private key.
Wallet key stays local; unsigned/signed transaction data and orders are sent to TradeRouter/DEX infrastructure.
Reviewed write actions: Sign/submit swaps; Create/cancel limit/TWAP/trailing/combo orders
Sensitive access: Wallet private key, Wallet balances, Trading strategy
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
The publisher's blanket safe claim was not adopted. Local private-key signing and DeFi execution carry material operational risk; public tracking is not trading advice.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Requires a Solana wallet private key for write tools.
Write actions move real assets and can be irreversible.
Server builds unsigned transactions; client signs locally, but signed transactions are then submitted.
DEX liquidity/slippage/MEV and token risk remain external market risks.

Original activity observations

@traderouter/trade-router-mcp 1.0.13 published 2026-04-27T08:24:16.201Z

Technical identity

npm/@traderouter/trade-router-mcp

Exact implementation source: https://www.npmjs.com/package/@traderouter/trade-router-mcp ↗
Reviewed resource type: Gateway
Repository identity: TradeRouter/trade-router-mcp
Package identity: npm:@traderouter/trade-router-mcp
Service endpoint: https://api.traderouter.ai / wss://api.traderouter.ai/ws

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@traderouter/trade-router-mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
traderouter.ai/
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
traderouter.ai/integrations
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect gateway
Publisher instructions
Trade router may prepare or initiate financial transactions; inspect security and permission setup.
publisher documented install or connect · Publisher instructions
npx -y @traderouter/trade-router-mcp
Configure / authenticate
MCP100 setup guide
TradeRouter handles wallet/trade-order information; do not create orders, sign, or execute transactions as connection check. Prefer public read-only quote/holdings queries.
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

TradeRouter MCP is a thin client over its REST/WebSocket engine for swaps, holdings, market data, limit/TWAP/trailing/combo orders and MEV-protected transaction submission. Wallet keys remain local to the MCP process.

Capability: Finance & Payments
Resource type: Gateway
Industry: Financial Services & Investing
Best fit: Non-custodial Solana swap/order execution for agents with local signing and dry-run support.

Representative uses

Read holdings/market cap/price data
Build/execute Solana swaps
Create/cancel limit or TWAP/trailing orders
Use dry-run mode before mainnet writes

Limitations

Requires a Solana wallet private key for write tools.
Write actions move real assets and can be irreversible.
Server builds unsigned transactions; client signs locally, but signed transactions are then submitted.
DEX liquidity/slippage/MEV and token risk remain external market risks.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Local Solana private key.
Permissions: Wallet read plus real swap/order execution within wallet balance.
Data handling: Wallet key stays local; unsigned/signed transaction data and orders are sent to TradeRouter/DEX infrastructure.
Cost: transactional
Risk and cautions: Direct financial execution. Use a dedicated wallet, dry-run first, explicit slippage/amount limits.

Access scope and cautions

Write actions: Sign/submit swaps Create/cancel limit/TWAP/trailing/combo orders
Sensitive access: Wallet private key Wallet balances Trading strategy
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Read holdings/market cap/price data; Build/execute Solana swaps; Create/cancel limit or TWAP/trailing orders; Use dry-run mode before mainnet writes.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @traderouter/trade-router-mcp. Recorded transport: stdio. Recorded environment-variable notes: TRADEROUTER_PRIVATE_KEY; TRADEROUTER_DRY_RUN (recommended initially). No configuration values are supplied here. Prerequisites: Node.js >=20.18; dedicated Solana trading wallet recommended. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No API key; wallet private key is used locally for signing.

Can it modify data or perform write operations?

Documented write actions include: Sign/submit swaps; Create/cancel limit/TWAP/trailing/combo orders. Recorded permission boundary: Wallet read plus real swap/order execution within wallet balance.

What data-handling boundary should I consider?

Wallet key stays local; unsigned/signed transaction data and orders are sent to TradeRouter/DEX infrastructure. Recorded sensitive-access context: Wallet private key; Wallet balances; Trading strategy.

What limitations and risks should I check before use?

Direct financial execution. Use a dedicated wallet, dry-run first, explicit slippage/amount limits. Requires a Solana wallet private key for write tools. Write actions move real assets and can be irreversible. Server builds unsigned transactions; client signs locally, but signed transactions are then submitted. DEX liquidity/slippage/MEV and token risk remain external market risks. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use. The publisher's blanket safe claim was not adopted. Local private-key signing and DeFi execution carry material operational risk; public tracking is not trading advice.

What cost model is recorded?

The reviewed cost model is transactional. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.