Home / MCP registry index / io.github.beepboop2025/undertow
Undertow market liquidity and exit-cost tools
io.github.beepboop2025/undertow in the official MCP registry.
Endpoint https://api.seiche.info/undertow/mcp. Source: github.com/beepboop2025/undertow-mcp.
The registry describes it as: Dated exit evidence, depth, tiers and gold cash scenarios. No executable quotes or trade authority.
We read its 16 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
agent_access_status crypto_exit_check crypto_funding_cost crypto_portfolio_stress depth_episodes exit_cost gold_cash_realisation latest_article liquidity_tiers market_corpus_context research_network sealed_record trade_safety_exit_context unwind_watch venue_concentration venue_price_reconciliation
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-beepboop2025-undertow)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.