DeFi Intelligence & MEV Router (x402)
https://server.smithery.ai/stubby76/mcp-defi-router/mcpAutonomous multi-chain DeFi execution engine providing real-time liquidity routing, MEV sandwich risk analysis, smart contract security scoring, and ready-to-sign execution payloads. ### Core Capabilities & Synthesized Compute * **dex_liquidity_router**: Simulates swap executions across decentralized exchanges (Aerodrome, Uniswap, etc.), estimates dynamic price impact for customized trade sizes, and computes MEV/sandwich attack risk scores (0–100) with private RPC mitigation directives. * **contract_security_screener**: Audits EVM token contracts for honeypots, transfer traps, blacklist bytecode, and dynamic taxes. Generates a composite vulnerability score and maximum safe position ceiling. * **cross_chain_bridge_optimizer**: Identifies lowest-slippage cross-chain routes across EVM and Solana (LI.FI engine), factoring in gas overhead, bridge fees, and returning ready-to-sign transaction calldata (`to`, `data`, `value`, `gasLimit`). ### Micro-Payment & Settlement * **Protocol**: x402 HTTP 402 Micropayment standard * **Rate**: 0.01 USDC per tool execution * **Network**: Base (mainnet) * **Settlement Token**: USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) * **Transport**: Streamable HTTP / SSE Discovery endpoints (`initialize`, `tools/list`, and server cards) are free to query.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 79.6/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1374 ms). |
| Protocol revision | 5/10 | Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 3 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 75% of peers
- This listing 84 · peer median 81
- Latency
- Faster than 26% of peers
- This listing 543 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Protocol revision −5
— Support the current protocol revision.
Now: Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/stubby76/mcp-defi-router/mcp
curl -X POST https://server.smithery.ai/stubby76/mcp-defi-router/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'