mcp server
AgentData - Executable Liquidity / Exit-Cost
Size-aware exit cost, depeg risk & liquidity fragility for a Base token (x402, testnet).
Description as published by the maintainer. Source
- version 0.1.0
- active
- retrieval
active — Registry entry last updated 2026-06-18. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
1 function, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
liquidity_exit_cost(pool, size, tier, token)- Size-aware exit cost, depeg risk, and liquidity fragility for a token on Base. Given a token and a sell size, returns the realized cost of exiting (price impact + fee, in bps and units), the best route across venues, an aggregated fragility score, and — for pegged assets — a depeg-risk score. Computed deterministically from on-chain AMM state, so the result is reproducible and auditable. Three tiers by compute depth (default 'risk'): 'quote' = best-route exit cost for one size; 'risk' = exit cost + fragility (+ depeg for pegged tokens); 'deep' = adds a multi-size exit-cost curve, max-size-before-cost thresholds, and an internal cross-check. Pricing per call (USDC): quote = $0, risk = $0, deep = $0. Status: testnet/preview — payment runs over the x402 HTTP surface, not this tool. Required: token, size.
Last successful function declaration observed on . Source: https://agentdata-liquidity-exit-cost.onrender.com/mcp/. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://agentdata-liquidity-exit-cost.onrender.com/mcp/.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-18 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-18 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 1 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | agentdata-liquidity-exit-cost.onrender.com | |
| mcp endpoint status | ok | The server listed 1 function when asked. | as of probe | agentdata-liquidity-exit-cost.onrender.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json