DarkRoute MCP

Ask what a token costs to get out of, from any MCP client.

npx darkroute-mcp

No key. No wallet. Nothing here can sign or spend.

Running that command by hand will look like it has frozen. It has not. An MCP server talks over stdin and stdout, so it starts, prints nothing, and waits for a client to speak to it. That is the correct behaviour and there is nothing to see. Give the command to your MCP client and let the client do the talking.

Why this exists

Somebody pastes a contract address and asks whether it is safe to buy. A price feed cannot answer that. It quotes the pool the token's own site links to, and on a chain where anyone can open a pool for any token, that is the pool the token chose to show you.

So this answers the other question. Every Uniswap v4 pool we have indexed for that token, the cheapest measured cost of selling out of it, and a plain verdict when that cost is absurd.

Measured matters. A pool can advertise a 0% fee and sit behind a hook that takes 90%, and the fee column cannot see that. These numbers come from asking the quoter what a sale would actually pay, so a hook's cut is already inside them.

On Robinhood Chain, 73,499 of the 265,345 tokens with a pool have no pool that charges under 50% to leave (measured 17 September 2026). More than a quarter. That is the fact a chart hides.

Tools

Tool	What it answers
token_exit_cost	The cheapest measured cost of selling out, and a verdict: ok, costly, trap, unknown
token_pools	The pools behind that verdict, and where to see them all
swap_quote	A live buy or sell quote, naming the pool and printing the fee

Chains: rh (Robinhood Chain, 4663) and arc (Arc, 5042).

Install

Claude Desktop, in claude_desktop_config.json:

{
  "mcpServers": {
    "darkroute": { "command": "npx", "args": ["-y", "darkroute-mcp"] }
  }
}

Claude Code:

claude mcp add darkroute -- npx -y darkroute-mcp

Then ask it something: "is 0x… safe to buy?"

From a clone instead

If you would rather read the code before running it, which is the better instinct for anything that prices your money:

git clone https://github.com/darkrouteRH/mcp darkroute-mcp
cd darkroute-mcp && npm install
node test/smoke.mjs          # 9 checks, end to end against the live API
claude mcp add darkroute -- node $PWD/src/index.js

test/ ships with the repository and not with the npm package, so node test/smoke.mjs works from a clone and not from an install. The published tarball is four files: the server, the README, the licence and package.json.

Point it somewhere else with DARKROUTE_API, which defaults to https://app.darkroute.exchange/api/v1.

What it will not do

It will not call a token a trap on a partial index. We are still walking backwards through Arc, and "every pool charges 90%" would really mean "every pool we have read so far". In that case the verdict is unknown and says which. A token is not a trap for being old.

It judges the cheapest pool, never the worst. One predatory pool beside one honest pool is an ordinary token on these chains. The question is whether a way out exists at all.

It will not invent an answer when our own request fails. A timeout returns an error saying nothing was read, rather than a reassuring number. The failure mode of a tool a model quotes from has to be silence.

It cannot trade. Read-only everywhere. Where DarkRoute itself cannot send a fill, the tool says whose limitation that is: on Arc a UniversalRouter is deployed and carries most of the chain's v4 swaps, and it is our own swap path that is not wired to that chain yet.

Where the numbers come from

The public API at app.darkroute.exchange/api/v1, documented at darkrouteRH/api. Uniswap v4 publishes no registry of pools, so we index every Initialize event on both chains and read the pools ourselves. The same numbers are on the web pages, at app.darkroute.exchange/token/<address>.

MIT.