AgentData - Executable Liquidity / Exit-Cost MCP server
online · 100% uptimeio.github.phenicea/agentdata-liquidity-exit-cost·v0.1.0Size-aware exit cost, depeg risk & liquidity fragility for a Base token (x402, testnet).
0 stars
Reviews
Write oneNobody has reviewed AgentData - Executable Liquidity / Exit-Cost yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
AgentData - Executable Liquidity / Exit-Cost tools (1)
write = sends, deletes, buys or postsliquidity_exit_costFreeSize-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.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 598ms20/20
- Tool poisoning1 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 100 days ago8/15
- Maintainer identityregistry namespace matches repository owner7/10
How AgentData - Executable Liquidity / Exit-Cost compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 80/100
- higher than 60% of 48,255 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 201 ms
- faster than 63% of 30,031 servers
What its tools let an agent do: 1 read
Install AgentData - Executable Liquidity / Exit-Cost in Claude Code, Cursor or VS Code
claude mcp add --transport http agentdata-liquidity-exit-cost https://agentdata-liquidity-exit-cost.onrender.com/mcp/
What the publisher says
From the AgentData - Executable Liquidity / Exit-Cost repository's README, as published. We do not edit it. Read it on GitHub
AgentData — Executable Liquidity (endpoint #1)
A pay-per-call data endpoint for AI agents: size-aware exit cost, depeg risk, and liquidity fragility for a token on Base. Not raw prices — computed, normalized, decision-grade intelligence an agent needs before it acts. Settled in USDC via x402 (Phase 2). Sourced on-chain, so the derived data is cleanly redistributable.
Strategy, values, and roadmap live in CLAUDE.md. Decisions are
logged in decisions/DECISION_LOG.md and
decisions/adr/.
What it answers
"If I try to exit this position right now, what does it actually cost me, how
much can I move before slippage blows past X bps, and how fragile is that
liquidity?"
Three priced tiers (single source of truth in agentdata/api/pricing.py):
Testnet forces every price to $0 (the 402 flow is still exercised end-to-end).
Layout
src/agentdata/
config.py # env-driven; NETWORK_MODE testnet|mainnet (testnet default)
compute/ # the value-add: pure, deterministic, unit-tested math
amm.py # constant-product + Solidly stable curve, exit cost
routing.py # cheapest-venue selection
depeg.py # depeg deviation / dispersion / score
fragility.py # depth + concentration + convexity -> fragility score
tiers.py # quote / risk / deep orchestration
chain/ # on-chain Base reads (Aerodrome / Uniswap), web3 lazy
provider.py # FixturePoolProvider (default) + factory
onchain.py # OnChainPoolProvider (env-gated, no guessed addresses)
api/ # FastAPI JSON layer + pricing + stable schema
monitoring/ # uptime, latency p50/p95, error rate, calls per tier
tests/ # unittest (stdlib for compute; fastapi for api)Run it (local, no funds, no network)
pip install -e . # or: pip install fastapi pydantic 'uvicorn[standard]'
uvicorn agentdata.api.app:app --reload
# then:
curl 'http://127.0.0.1:8000/v1/liquidity/exit-cost?token=WETH&size=10&tier=risk'
curl 'http://127.0.0.1:8000/pricing'
curl 'http://127.0.0.1:8000/metrics'Defaults: NETWORKMODE=testnet, POOLSOURCE=fixture (deterministic demo pools WETH, THIN, USDX). See .env.example.
Test
# compute core needs no dependencies:
PYTHONPATH=src python -m unittest discover -s testsStatus
tests green.
- Phase 1 (local endpoint): done. compute + chain seam + API + monitoring, 42
testnet facilitator on Base Sepolia. No real USDC; mainnet is an escalated human decision (CLAUDE.md §0/§14).
- Phase 2 (x402 testnet): next. Payment middleware in front of the API, free
refuses to run on guessed contract addresses rather than fake data.
- On-chain mode requires a verified pool registry before use (ADR-001) — the code
Nothing above is checked by us. What we check is on the safety report.
AgentData - Executable Liquidity / Exit-Cost: common questions
- Is AgentData - Executable Liquidity / Exit-Cost MCP server safe?
- Mostly: it is graded B (80/100). Read the AgentData - Executable Liquidity / Exit-Cost safety report
- How do I install AgentData - Executable Liquidity / Exit-Cost?
- It runs remotely at agentdata-liquidity-exit-cost.onrender.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does AgentData - Executable Liquidity / Exit-Cost need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is AgentData - Executable Liquidity / Exit-Cost maintained?
- The last commit was 139 days ago (2026-06-18). The latest release is v0.1.0.
- Is AgentData - Executable Liquidity / Exit-Cost up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does AgentData - Executable Liquidity / Exit-Cost compare with other MCP servers?
- safety score 80/100 (higher than 60% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.