Undertow market liquidity and exit-cost tools
REMOTE · API.SEICHE.INFO · SCANNED SEP 20
Daily exit context, depth, tiers, and sealed records. No commodity futures or execution authority.
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1657 tokens (~150/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Undertow market liquidity and exit-cost tools MCP server?
Undertow market liquidity and exit-cost tools is a hosted endpoint at https://api.seiche.info/undertow/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 · api.seiche.info
claude mcp add --transport http beepboop2025-undertow 'https://api.seiche.info/undertow/mcp'
{
"mcpServers": {
"beepboop2025-undertow": {
"url": "https://api.seiche.info/undertow/mcp"
}
}
} {
"servers": {
"beepboop2025-undertow": {
"type": "http",
"url": "https://api.seiche.info/undertow/mcp"
}
}
} [mcp_servers.beepboop2025-undertow] url = "https://api.seiche.info/undertow/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"beepboop2025-undertow": {
"type": "remote",
"url": "https://api.seiche.info/undertow/mcp",
"enabled": true
}
}
} openclaw mcp add beepboop2025-undertow --url 'https://api.seiche.info/undertow/mcp' --transport streamable-http
mcp_servers:
beepboop2025-undertow:
url: "https://api.seiche.info/undertow/mcp" {
"McpServers": {
"beepboop2025-undertow": {
"Transport": "http",
"Url": "https://api.seiche.info/undertow/mcp"
}
}
} assistant mcp add beepboop2025-undertow -t streamable-http -u 'https://api.seiche.info/undertow/mcp'
{
"mcpServers": {
"beepboop2025-undertow": {
"type": "http",
"url": "https://api.seiche.info/undertow/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 9 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 50% → 36% ▼ functional
- Schema quality: 190 → 150 ▲ functional
- New tool “research_network” functional
- 4 Sept 26 +7
- Judged manipulation: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- 3 Sept 26 −9
- Judged manipulation: pass → unverified ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 100% → 50% ▼ functional
- Schema quality: excellent → unverified ▼ functional
- Server version: 1.9.0 → 1.10.0 functional
- New tool “trade_safety_exit_context” functional
- 29 Aug 26 +1
- Stability: 0.97 → pass security
- 28 Aug 26 −1
- Stability: pass → 0.97 functional
- 27 Aug 26 +1
- Stability: 0.97 → pass security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 Sept 2026 · Probed https://api.seiche.info/undertow/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.seiche.info | CN=YE1,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 51c1896503dd693d96ce81ef09be5a03892 |
| SANs: api.seiche.info | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.seiche.info. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| info. | present | 5104 | 8 | Verified |
| seiche.info. | present | 2371 | 13 | Verified |
| api.seiche.info. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.seiche.info/undertow/mcp | Verified | 200 | |
| http (plaintext) | http://api.seiche.info/undertow/mcp | HTTPS enforced | 308 | https://api.seiche.info/undertow/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 →
agent_access_status Your access + meter ~65
Where this caller stands: whether the bearer token verified, the entitlement tier behind it (checked fresh, never trusted from the token), today's tool-call meter, and how to get full access. Call this first when a subscriber tool is missing from tools/list or a call is refused.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
depth_episodes Realized depth collapses ~85
Realized depth-collapse episodes in BTC ±1% aggregate depth: onset, trough, drawdown fraction and recovery time for each episode that crossed the pre-registered threshold. Detection rules were declared before any episode accrued. Use when asked whether crypto liquidity has actually broken lately, as opposed to how it looks right now. The subscriber exit_desk_full carries the ETH desk beside BTC.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
exit_cost Exit cost at your size, per venue ~123
What selling a position of a given USD size costs RIGHT NOW, venue by venue, from live public order books (BTC, six venues). Returns the per-venue cost in basis points at the nearest published size rung, the cheapest and dearest venue with approximate dollar cost, and the venue spread. Estimates interpolated from published quote depth — never a book walk, refreshed roughly hourly. Not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| size_usd | number | – | position size in USD (published rungs run $1,000 to $1,000,000; nearest rung is used) |
No output schema declared.
No examples provided.
latest_article ~43
The exact full-text Undertow editorial published today, with its evidence clock, generation mode and passing quality receipt. This returns the canonical revision verbatim and never rewrites facts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
liquidity_tiers Full board: tiers + funding ~110
The Undertow board's TIER ROW: one liquidity tier per market segment (UST, IG, HY, EQUITY, ETF, FX, CN, CRYPTO, BSTOCK) plus the funding-stress overlay regime. PARTIAL means insufficient scoring history, reported honestly instead of guessed. Use for 'how liquid are markets today' at one glance, then drill into crypto with the other tools; the FULL board (every measure with its stress percentile and analyst note) is the subscriber board_full tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
research_network ~71
Read Palimpsest source evidence alongside Seiche funding context, with explicit paths into institution research, global data and exit liquidity. Metadata, dates and source rights stay attached; no common score or order authority.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| topic | string | – | – |
No output schema declared.
No examples provided.
sealed_record Sealed calls record (misses kept) ~81
Undertow's own sealed forward-calls record: every call hash-chained and signed BEFORE its outcome, scored against the immutable point-in-time board for its horizon date, with misses kept published. Returns the full record with outcomes and the ledger root. Use when asked whether Undertow's judgements can be trusted, and quote the misses as prominently as the hits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trade_safety_exit_context PIT-bound exact-rung paper exit context ~122
Exact-rung BTC/USD sell evidence for observe/paper Trade Safety. Binds the opaque request, source pack and reviewed rights to PIT; rechecks USD/USDT conversion, required bid bands, six venue clocks and startup SHA. Context only: no nearest rung, live mode, execution or clearance authority.
| Name | Type | Req | Description |
|---|---|---|---|
| instrument | – | yes | – |
| mode | – | yes | – |
| request_hash | string | yes | Opaque complete-request hash |
| requested_size_usd | number | yes | Exact published USD rung |
| side | – | yes | – |
| venue | null | yes | – |
No output schema declared.
No examples provided.
unwind_watch Can the watched books exit? (free) ~235
Can a watched fund's book actually leave the building? Unwind stress for the watched 13F filers (incl. the Situational Awareness LP replay): effective position count, whole-book days-to-exit at 10% of a median day's volume (bracketed as-if median large / median small-mid name, and each count published as a band that contains it rather than as a point, because the exact count returns the basket's median dollar volume by one division), and the leverage x shock x maintenance margin grid with its three honest states (NO_CALL / CALL / EQUITY_EXHAUSTED). Default is the per-filer headline; pass cik for one filer's full free row. Display-only measure on frozen grids; 13F sees no shorts or options, so every number is a floor. Use when asked whether a fund's book could exit, or what the Aschenbrenner failure mode looks like in a current filing. Not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | integer | – | optional: SEC CIK of a watched filer (returns that filer's full FREE row instead of the all-filer headline) |
No output schema declared.
No examples provided.
venue_concentration Depth concentration today ~94
How concentrated the BTC depth backbone is today: which venue holds the largest share of ±1% aggregate depth, the HHI, the effective venue count (1/HHI), and per-venue depth in USD. Low effective venue count means an exit depends on one venue staying open. The subscriber exit_desk_full adds ETH and the venue-failure withdrawal scenario (what your exit costs if the top venue goes dark).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
venue_price_reconciliation Consensus price when venues disagree ~144
What the price IS when venues disagree: the cross-venue consensus mark for BTC and ETH, weighted by resting depth over squared half-spread (NOT a median of last prices), with the BLINDNESS GAP — how far the deepest venue sits from consensus, i.e. how wrong you would be pricing off the venue you would naturally trust — plus depth concentration (CR1/HHI) and the names of any dislocated venues. Use for 'what is BTC/ETH actually worth right now', 'is an exchange dislocated', or before trusting any single venue's price. Experimental until its accrual gates pass; the payload says so. Not investment advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Undertow market liquidity and exit-cost tools MCP server?
Undertow market liquidity and exit-cost tools is an MCP server listed in the public MCP registry as io.github.beepboop2025/undertow. Daily exit context, depth, tiers, and sealed records. No commodity futures or execution authority. This page covers its hosted endpoint (https://api.seiche.info/undertow/mcp).
Is the Undertow market liquidity and exit-cost tools MCP server safe to use?
Undertow market liquidity and exit-cost tools scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Undertow market liquidity and exit-cost tools MCP server expose?
Undertow market liquidity and exit-cost tools exposes 11 tools: agent_access_status, depth_episodes, exit_cost, latest_article, liquidity_tiers, and 6 more. Their descriptions and schemas cost roughly 1,173 tokens of context every time the server is loaded.
Does the Undertow market liquidity and exit-cost tools MCP server require authentication?
No. We connected to Undertow market liquidity and exit-cost tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Undertow market liquidity and exit-cost tools MCP server still maintained?
Undertow market liquidity and exit-cost tools is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.