MCP server for MEV-relevant on-chain data: gas price percentiles and bounded mempool watching for pending swaps.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mev-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mev-mcp An MCP server for inspecting MEV-relevant activity on Polygon — pending mempool traffic, confirmed swap history, and gas pricing — exposed as tools an AI agent (or you, via Claude Desktop) can call directly. This is a diagnostic and research tool, not a production MEV detector. It's built to be honest about what it sees and what it misses, rather than to look more capable than it is. ## What it does | Tool | What it tells you | Source | |---|---|---| | `check_pending_swaps_on_pool` | Pending transactions touching a given Uniswap v3 pool, broken down by route type, plus a self-check against confirmed history | Public mempool (`eth_subscribe`) | | `check_confirmed_swaps_on_pool` | Ground-truth swap count and originating contracts for a pool over a recent block range | Finalized chain state (`eth_getLogs`) | | `get_gas_price_percentiles` | Gas price distribution over recent blocks | `eth_feeHistory` | | `hello` | Connectivity check | — | Polygon only. Arbitrum uses a centralized sequencer with no public mempool, so pending-transaction tools aren't meaningful there. ## The honest part: mempool coverage is partial, and the tool tells you so Swaps on a given pool can be routed through many different contracts — Uniswap's own `SwapRouter`, `SwapRouter02`, `UniversalRouter`, or any of a long list of aggregators (1inch, Odos, Paraswap, and others). `check_pending_swaps_on_pool` currently decodes: - Direct calls to the pool contract - `SwapRouter` / `SwapRouter02` single-hop swaps (`exactInputSingle`, `exactOutputSingle`) and multi-hop swaps (`exactInput`, `exactOutput`, via packed-path decoding) - `UniversalRouter` `V3_SWAP_EXACT_IN` / `V3_SWAP_EXACT_OUT` commands - `1inch AggregationRouter v6` swaps That's a meaningful slice of mempool traffic, but it is **not exhaustive**. In testing on a moderately active Polygon pool, well over half of confirmed swap volume routed through contracts outside this list — other aggregators, smart-contract wallets, and rou…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.