MEV Intelligence
REMOTE · MEV.ADVALOREM.IO
Real-time Ethereum liquidation intelligence for AI agents and MEV bots.
Available components
Last scanned (16 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 13 Oct 2026.
Category Crypto and Web3
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
Recent critical change
TLS certificate (14 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS check failed: the certificate is expired or not yet valid (as of 2026-10-14). See how to fix → View diagnostics → Fail
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the TLS certificate failed verification. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 20 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 14 Oct 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Sept 26 +58
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Oct 2026 · Probed https://mev.advalorem.io/mcp
TLS invalid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
Chain error: expired
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mev.advalorem.io | CN=YR1,O=Let's Encrypt,C=US | 16 Jul 2026 | 14 Oct 2026 | RSA 2048 | SHA256-RSA | 535dee3703ca1d9f9b5b40dab97a01d494d |
| SANs: mev.advalorem.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mev.advalorem.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| advalorem.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mev.advalorem.io/mcp | TLS failed | ||
| http (plaintext) | http://mev.advalorem.io/mcp | HTTPS enforced | 301 | https://mev.advalorem.io/mcp |
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 →
build_liquidation_tx ~421
Build agent-ready calldata for a liquidation transaction. Returns the target protocol contract address, ABI-encoded calldata, suggested gas limit, value, and chain — everything an agent needs to sign and submit via submit_bundle. Supports Aave V3 (L1 + Base), Spark (L1), and Morpho Blue (L1). Returns calldata only — the agent signs and submits separately. This tool does NOT touch funds and does NOT submit anything; it is a calldata builder.
| Name | Type | Req | Description |
|---|---|---|---|
| borrower | string | yes | 0x-prefixed address of the borrower being liquidated. |
| chain | string | yes | Chain to build calldata for. base only supported for aave-v3. |
| collateral_asset | string | yes | 0x-prefixed address of the collateral token to seize. For Morpho, this field is ignored (market ID supplies it). |
| debt_asset | string | yes | 0x-prefixed address of the debt token to repay. For Morpho, this field is ignored. |
| debt_to_cover | string | yes | Amount of debt token to repay in wei (string to avoid precision loss). Use "max" or the uint256 max value 0xff..ff to liquidate as much as possible (Aave V3 close factor applies). |
| morpho_market_id | string | – | Morpho Blue market id (bytes32). Required when protocol=morpho. |
| morpho_repaid_shares | string | – | Morpho Blue only. Amount of debt shares to repay. Mutually exclusive with morpho_seized_assets. |
| morpho_seized_assets | string | – | Morpho Blue only. Amount of collateral to seize in wei. Mutually exclusive with morpho_repaid_shares. |
| protocol | string | yes | Lending protocol. aave-v3 supported on ethereum + base. spark and morpho on ethereum only. |
| receive_a_token | boolean | – | Aave V3 only. If true, receive collateral as aToken (saves gas, no unwrap). If false, receive underlying. Default false. |
No output schema declared.
No examples provided.
get_builder_recommendation ~69
Get the best Ethereum block builder for MEV bundle submission RIGHT NOW based on live relay acceptance rate and submission volume. Returns the top recommended builder name and acceptance percentage. Full ranked builder list with telemetry available at /intelligence/builder-recommendation with x402 payment ($0.25).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_daily_liquidation_report ~119
Get a daily intelligence report summarizing liquidation market activity: competitor count, positions we would have fired on, funnel metrics (PRE→SIM→HOTFIRE→SUBMIT→LANDED), and the top candidate right now. This is the "morning briefing" tool — call it once per session to understand market state before executing. Full accuracy archive with precision/recall metrics available at /intelligence/accuracy-archive.
| Name | Type | Req | Description |
|---|---|---|---|
| window_hours | integer | – | Lookback window in hours (default 24, max 48). |
No output schema declared.
No examples provided.
get_liquidation_waves ~126
Get near-liquidation borrowers ranked by health factor proximity across Aave V3, Spark, and Morpho on L1 and Base. Returns top 10 positions with full borrower addresses, health factor, debt USD, and collateral USD. Once you have a target, sign a liquidation transaction and call submit_bundle to execute atomically. For net profit estimates and the full borrower universe, call /intelligence/liquidation-waves with x402 USDC payment ($0.50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 10, preview max 10) |
No output schema declared.
No examples provided.
get_mev_feed ~88
Get a risk-enriched MEV opportunity stream. Returns 10 positions with chain, protocol, health factor, and risk tags. Full stream with borrower addresses and expected profit available at /intelligence/feed with x402 payment ($0.10). Use submit_bundle to act on opportunities directly from this feed.
| Name | Type | Req | Description |
|---|---|---|---|
| min_net_usd | number | – | Minimum estimated net USD profit to include |
No output schema declared.
No examples provided.
get_searcher_leaderboard ~75
Get top MEV searchers ranked by landed liquidation fires in the last 4 hours. Returns top 5 searchers with full addresses, landed count, total submissions, and land rate percentage. Full 25-entry leaderboard available at /intelligence/searcher-leaderboard with x402 payment ($0.25).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
monitor_crossing_candidates ~124
Get the highest-priority liquidation candidates sorted by cross probability — borrowers most likely to become liquidatable in the next price move. Each candidate includes health factor, cross probability (0–1), estimated net profit, and protocol. Use this to prioritize which positions to pre-build bundles for. Call submit_bundle when a candidate crosses HF=1.0.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max candidates to return (default 10, max 20). |
| min_cross_prob | number | – | Minimum cross probability (0–1) to include. Default 0.05. |
No output schema declared.
No examples provided.
predict_liquidation_probability ~180
Get a structured liquidation probability prediction for a specific borrower or the top candidates. Returns: health_factor, cross_probability (0–1), estimated_ev_usd, lead_time_estimate_s (how long until crossing at current oracle velocity), oracle_velocity (|Δprice|/min on collateral asset), and a human-readable verdict. This is the core moat tool — it exposes the prediction layer that drives bundle decisions. Call this before submit_bundle to confirm the opportunity is still live and to size your bribe correctly. Full probability model with confidence intervals available at /intelligence/liquidation-waves with x402 payment ($0.50).
| Name | Type | Req | Description |
|---|---|---|---|
| borrower | string | – | Borrower address to get prediction for. If omitted, returns top 5 candidates by cross probability. |
| protocol | string | – | Optional protocol filter when borrower is not specified. |
No output schema declared.
No examples provided.
recommend_bundle_submission ~88
Get an actionable bundle submission recommendation for a specific borrower or current market conditions. Returns the best builder to target, expected inclusion probability, and a human-readable reason based on live relay telemetry. Pair with monitor_crossing_candidates — identify a hot candidate, then call this to decide WHERE to submit your bundle.
| Name | Type | Req | Description |
|---|---|---|---|
| borrower | string | – | Optional. Borrower address to get a position-specific recommendation for. |
No output schema declared.
No examples provided.
submit_bundle ~269
Submit a signed Ethereum bundle directly to MEV SearcherNet rbuilder for inclusion. Use this after get_liquidation_waves or get_mev_feed to act on a liquidation opportunity. Bundles are forwarded to rbuilder and fanned out to Flashbots, Titan, Beaver, BuilderNet, and bloXroute relays. Free with API key attribution (X-Api-Key header). Inclusion rate, sim pass rate, and per-builder acceptance available at /orderflow/analytics with provenance. Returns a tracking_id you can use to check submission status at /orderflow/submissions/{tracking_id}. Tip: pair with get_liquidation_waves — identify a borrower near liquidation, construct the liquidation tx, sign it, then call this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional. API key for attribution and leaderboard tracking. Assign at mev.advalorem.io. |
| blockNumber | string | yes | Target block number as hex string (e.g. "0x1400000"). Bundle will only be included in this exact block. |
| revertingTxHashes | array | – | Optional. Tx hashes that are allowed to revert without invalidating the bundle. |
| txs | array | yes | Array of hex-encoded signed transactions (0x-prefixed RLP). Max 10 per bundle. |
No output schema declared.
No examples provided.
How do I install the MEV Intelligence MCP server?
MEV Intelligence is a hosted endpoint at https://mev.advalorem.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mev.advalorem.io
claude mcp add --transport http io-advalorem-mev-intelligence 'https://mev.advalorem.io/mcp'
What is the MEV Intelligence MCP server?
MEV Intelligence is an MCP server listed in the public MCP registry as io.advalorem.mev/intelligence. Real-time Ethereum liquidation intelligence for AI agents and MEV bots. This page covers its hosted endpoint (https://mev.advalorem.io/mcp).
What tools does the MEV Intelligence MCP server expose?
MEV Intelligence exposes 10 tools: get_liquidation_waves, get_searcher_leaderboard, get_builder_recommendation, get_mev_feed, submit_bundle, and 5 more. Their descriptions and schemas cost roughly 1,559 tokens of context every time the server is loaded.
Does the MEV Intelligence MCP server require authentication?
Its publisher declares no required credentials for MEV Intelligence. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the MEV Intelligence MCP server still maintained?
MEV Intelligence has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 13 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.