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.

io.github.infiniteezverse/mcp-ezpath

NPM · MCP-EZPATH · SCANNED SEP 21

Base DEX meta-router. Races 0x, ParaSwap, Aerodrome & Uniswap V3. Best quote. X402 pay-per-use.

Available components

0 this week 75 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 Security98
  • 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
  • 31 of 110 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 450 tokens (~225/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.infiniteezverse/mcp-ezpath server?

io.github.infiniteezverse/mcp-ezpath runs locally as an npm package, launched with npx -y mcp-ezpath. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-ezpath

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

  • 21 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.

  • 19 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.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 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.

  • 12 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.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
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 21 Sept 2026 · Analysed npm/mcp-ezpath@0.1.1

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 110 packages
Packages resolved 110
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~450 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. 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 →

Tool Tokens
ezpath_probe ~163

Check EZ-Path pricing without paying. Returns the toll address, per-request USDC cost, and available execution tiers. Use this first to inform the agent about costs before calling ezpath_quote.

NameTypeReqDescription
buyTokenstringyesERC-20 address to buy on Base mainnet. WETH=0x4200000000000000000000000000000000000006
sellAmountstringyesAmount to sell in base decimals (e.g. 1000000 = 1 USDC)
sellTokenstringyesERC-20 address to sell on Base mainnet. USDC=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

No output schema declared.

No examples provided.

ezpath_quote ~287

Get the best DEX swap quote on Base mainnet by racing 0x, ParaSwap, Aerodrome, and Uniswap V3. Automatically pays USDC per request via X402 EIP-3009 from the configured wallet. Requires EZPATH_WALLET_KEY env var set to a Base wallet private key with USDC balance.

NameTypeReqDescription
buyTokenstringyesERC-20 address to buy on Base
sellAmountstringyesAmount to sell in base decimals. For USDC (6 decimals): 1000000 = 1 USDC. For WETH (18 decimals): 1000000000000000000 = 1 WETH.
sellTokenstringyesERC-20 address to sell on Base. USDC=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, WETH=0x4200000000000000000000000000000000000006
slippagePercentagenumberMax acceptable slippage as decimal. 0.01 = 1%. Optional.
tierstringExecution tier. basic=$0.03 direct 0x | resilient=$0.10 dual-lane race | institutional=$0.50 race + Uniswap V3 safety net. Defaults to basic.

No output schema declared.

No examples provided.

Common questions

What is the io.github.infiniteezverse/mcp-ezpath server?

io.github.infiniteezverse/mcp-ezpath is listed in the public MCP registry as io.github.infiniteezverse/mcp-ezpath. Base DEX meta-router. Races 0x, ParaSwap, Aerodrome & Uniswap V3. Best quote. X402 pay-per-use. This page covers its npm package (mcp-ezpath).

Is the io.github.infiniteezverse/mcp-ezpath server safe to use?

io.github.infiniteezverse/mcp-ezpath scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 io.github.infiniteezverse/mcp-ezpath server expose?

io.github.infiniteezverse/mcp-ezpath exposes 2 tools: ezpath_probe, ezpath_quote. Their descriptions and schemas cost roughly 450 tokens of context every time the server is loaded.

Is the io.github.infiniteezverse/mcp-ezpath server still maintained?

io.github.infiniteezverse/mcp-ezpath is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.