Undertow — market liquidity map

What Undertow — market liquidity map does

Undertow provides market-liquidity and exit-cost evidence through MCP. Its tools cover per-venue selling costs, quoted-depth concentration, observed depth-collapse episodes, market-segment liquidity tiers, and selected funding or exposure scenarios. Results are read-only and are intended for analysis rather than order execution.

The public surface includes tools such as exit_cost, crypto_exit_check, venue_concentration, depth_episodes, liquidity_tiers, unwind_watch, trade_safety_exit_context, sealed_record, and agent_access_status. Subscriber tools add broader views including exit_desk_full, exit_schedule, board_full, corporate_transmission, household_credit, divergence_status, tide_clock, and unwind_stress. Access rights are checked for subscriber requests.

How it works

The hosted endpoint is https://api.seiche.info/undertow/mcp and uses streamable HTTP. Public requests do not require an API key or wallet. The service publishes observation times, venue inputs, size rungs, coverage gaps, and method details with relevant results.

Exit estimates are based on published size rungs. exit_cost reports a nearest-rung per-venue cost in basis points, approximate dollar impact, the cheapest and most expensive observed venues, and the spread between them. crypto_exit_check compares up to four requested BTC sell sizes against published rungs and does not interpolate between them. These figures are estimates, not executable quotes, and venue rankings can change during the day.

Other tools calculate caller-supplied funding costs or portfolio shocks, summarize venue concentration, identify realized depth-collapse episodes, and assign liquidity tiers to segments including U.S. Treasuries, investment-grade and high-yield credit, equities, ETFs, FX, China-related markets, and crypto. The tier response can include measure counts, replay eligibility, and a stated reason when a score is withheld.

Setup and configuration

The simplest connection uses the hosted URL directly. Claude Code can add it with:

claude mcp add --transport http undertow https://api.seiche.info/undertow/mcp

Claude Desktop can use the repository’s stdio adapter. Local setup requires Python 3.12 or newer and uv:

uv sync --locked
uv run --locked undertow-mcp

Docker is also supported through the repository’s root Dockerfile. The adapter requires outbound HTTPS access to api.seiche.info; it does not need a key, bearer token, wallet, port, volume, or environment setting. The hosted service is the route to subscriber tools, while the stdio adapter exposes the anonymous public surface and guided prompts.

Limitations and notes

Undertow — market liquidity map does not provide executable prices, trading, wallet access, or order placement. Published estimates can be stale or affected by depth and coverage gaps, so the observation clock and venue inputs should be reviewed before using a result.

The adapter disables redirects, environment proxies, and arbitrary upstream URLs. Requests are limited to 64 KiB, responses to 2 MiB, and each upstream operation to 10 seconds including queue wait. It does not automatically retry requests or cache responses. Upstream version or catalog drift fails closed, while tool results, errors, and entitlement refusals are preserved.

The hosted protocol supports several MCP revisions, including the 2025-03-26, 2025-06-18, 2025-11-25, and 2026-07-28 behavior described by the project. The service exposes no MCP resources or resource templates. Settlement histories and source receipts are provided through a separate source-data MCP rather than this listing.