Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Dated exit evidence, depth, tiers and gold cash scenarios. No executable quotes or trade authority.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.seiche.info/undertow/mcpRun this in your terminal
claude mcp add --transport http undertow https://api.seiche.info/undertow/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"undertow": {
"url": "https://api.seiche.info/undertow/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"undertow": {
"type": "http",
"url": "https://api.seiche.info/undertow/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.seiche.info/undertow/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account beepboop2025, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.13.0) reached the registry 35 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, alalanet — check before you pay
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Check packages, MCP servers and x402 endpoints before agents install or pay. Signed.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Hosted Streamable HTTP MCP; no local server or API key for public read-only tools. Add the products you need to Claude Code:
claude mcp add --transport http undertow https://api.seiche.info/undertow/mcp
claude mcp add --transport http liquilens https://api.liquilens.in/mcp claude mcp add --transport http seiche https://api.seiche.info/mcp
Try this first: What is the estimated exit cost for a $100,000 BTC sell? Compare available venues, snapshot times and excluded costs.
Try it in your browser · Cursor configuration · Codex commands · Free three-product starter kit and skill
For a connected review, ask for institution evidence → funding context → BTC exit estimates, with each source date, coverage gap and limitation kept separate. Client/model costs and fair-use limits may apply. Research calls do not execute trades.
Endpoint: https://api.seiche.info/undertow/mcp (streamable HTTP, no install)
Undertow is the market-liquidity product of LIQUILENS PRIVATE LIMITED, a registered company in India (CIN U62011RJ2026PTC116792). One company, three connected financial-evidence products: LiquiLens investigates institutions, Seiche explains funding conditions, and Undertow examines market exit evidence. Together they support a review of an exposure from institution to funding to liquidity, with each source date, coverage gap and research limit retained.
Built for people and AI agents working internationally. Access is global; coverage is market-specific. Read the company and investor story or inspect the shared company profile.
Start with a question: Open the crypto workbench. Choose a dollar size and click to read the current published venue estimates, snapshot date and method. No account, key, wallet or client installation is needed for this example. The result is a depth-based estimate, not an executable quote. The same page provides Codex, Claude Code, Cursor and VS Code setup.
Try it live: liquilens-undertow.com/developers · API catalog: api.seiche.info/undertow
Undertow exposes estimated exit cost by position size and venue, the concentration of quoted depth, realized depth-collapse episodes, and liquidity tiers across market segments. This MCP 1.13.0 endpoint exposes 24 read-only tools, split into 16 public and 8 subscriber tools, plus 3 guided prompts. Its capability inventory is pinned to liquilens-undertow commit f103a9929a438f92964e7254edd7553c5a4dfe3a, the hosted implementation at deploy/hetzner/undertow-mcp. The stdio discovery server in undertow_mm/mcp_server.py is a separate discovery surface; it is neither this registry listing nor the public stdio adapter provided here.
The liquidity_tiers result includes public measure counts, replay eligibility and the published reason a score is withheld. A PARTIAL tier can remain even when every measure qualifies. Settlement histories and source receipts are available through the separate source-data MCP.
Claude Code:
claude mcp add --transport http undertow https://api.seiche.info/undertow/mcp
Claude.ai / ChatGPT / Cursor: add a custom connector or MCP server with the URL above. No key and no wallet for the free surface.
The free agent starter kit connects Undertow exit estimates and venue concentration with Seiche funding context and LiquiLens bank evidence. Follow the Hermes or OpenClaw guide for the shared setup. It uses public tools under fair-use limits; model-provider costs remain separate.
For a recurring research workflow, use the shared infrastructure setup guide and current interface catalog. They distinguish the public research MCPs, the eight-tool Research Desk and optional private runtimes. Private paper assessment is a separate integration; Undertow's public tools do not submit orders. Source observation dates, data rights and eligibility remain explicit even when hosting and backups are healthy.
This repository contains the discovery manifest, documentation and an optional anonymous stdio adapter for the hosted service. The official registry serves io.github.beepboop2025/undertow version 1.13.0.
The direct hosted URL above remains the simplest connection. For clients that require stdio, clone this repository at a reviewed commit and use Python 3.12+ and uv:
uv sync --locked
uv run --locked undertow-mcp
A Claude Desktop configuration can use uv as its command and ["run", "--directory", "/absolute/path/to/undertow-mcp", "--locked", "undertow-mcp"] as its arguments. The stdio adapter exposes only the 16 anonymous tools and three prompts; subscriber access uses the direct hosted URL instead.
For Docker and Glama's container build:
docker build -t undertow-mcp .
docker run --rm -i undertow-mcp
The root Dockerfile runs as an unprivileged user and starts stdio directly. No API key, bearer token, wallet, port, volume or environment setting is needed. Outbound HTTPS access to the fixed api.seiche.info endpoint is required. Redirects, environment proxies and arbitrary upstream URLs are disabled. Requests are capped at 64 KiB, responses at 2 MiB, and each upstream operation at 10 seconds including queue wait. No automatic retries or response cache can hide outages or spend a quota twice. Upstream version/catalog drift fails closed. Tool results, native isError values and rights refusals are preserved.
A Glama maintainer can configure the root Dockerfile, complete its build test, and publish a Glama release from the listing's admin page. A GitHub commit or release does not create a Glama release. This repository does not claim a grade until Glama has actually rescanned and inspected it. See Glama's release guide.
2026-07-28: stateless requests use server/discover, per-request _meta, MCP-Protocol-Version, and mirrored Mcp-Method / Mcp-Name routing headers.2025-11-25, 2025-06-18, and 2025-03-26: retained legacy initialization, tools, prompts, notifications, batching, and ping behavior.tools/list returns only the public inventory; entitlement is checked fresh on every subscriber request.resources/list and resources/templates/list return explicit empty catalogs. resources/read returns a not-found error and never invents a resource.In the snapshot generated at 2026-08-08T15:01:22Z, selling $1,000,000 of BTC at the selected $1,000,000 published size rung cost 2.386 bp on Binance and 13.623 bp on Bitfinex: about $238.60 against $1,362.30. Gemini was the dearest observed venue in that same snapshot at 25.852 bp, or about $2,585.20.
Venue rankings can change during the day, and those differences are not visible in a single consolidated price. Undertow publishes the observation time and venue inputs with the estimate.
The browser workbench combines published BTC exit comparisons with funding and portfolio scenarios. The scenario forms run locally in the browser.
The crypto agent kit contains three installable skills, a standard-library Python client, offline scenario calculators and a repeatable brief connecting Undertow, Seiche and optional LiquiLens institution evidence. Exact file digests accompany the download. Nothing runs or installs automatically.
| Tool | What it serves | Surface |
|---|---|---|
agent_access_status | Your current tier, daily meter, grants, and the exact route to Agent or Desk access | free |
board_full | Every measure with its stress percentile or ACCRUING label, limits and analyst note | subscriber |
corporate_transmission | Whether funding stress is reaching nonfinancial firms | subscriber |
crypto_exit_check | Compare up to four requested BTC sell sizes across published rungs, with observation clocks and explicit stale/depth gaps; never interpolate a requested size | free |
crypto_funding_cost | Calculate funding, round-trip fees and linear break-even from caller-supplied inputs | free |
crypto_portfolio_stress | Apply caller-supplied price shocks and costs to linear exposures; show equity and gross asset/venue concentration | free |
depth_episodes | Realized depth-collapse episodes with onset, trough, drawdown and recovery, against thresholds declared before any episode accrued | free |
divergence_status | Compact comparison of corporate and household transmission regimes | subscriber |
exit_cost | Per-venue sell cost in basis points at the nearest published size rung, cheapest and dearest venue with approximate dollar cost, and the venue spread | free |
exit_desk_full | BTC and ETH at every published rung, plus the venue-failure withdrawal scenario | subscriber |
exit_schedule | Position-sized hour-by-hour liquidation schedule beside immediate and TWAP baselines | subscriber |
gold_cash_realisation | Caller-input gold sale and FX scenario with separate quote, settlement, access and pledge gates; no verified balance or executable quote | free |
household_credit | Whether funding stress is reaching household balance sheets | subscriber |
latest_article | The exact reviewed daily market-liquidity editorial with its evidence clock and publication authority | free |
liquidity_tiers | A liquidity tier per market segment (UST, IG, HY, equities, ETF, FX, China basin, crypto) with the funding-stress overlay | free |
market_corpus_context | Seiche corpus counts, rights and clocks, with bounded metadata pages; retrieval is not source-observation freshness | free |
research_network | Bounded Palimpsest and Seiche research discovery with source clocks, availability and no blended score | free |
sealed_record | The sealed forward-calls record, hash-chained and signed before outcomes, misses kept | free |
tide_clock | Clock-phase liquidity map and exit-cost-by-phase for BTC or ETH perpetuals | subscriber |
trade_safety_exit_context | Exact-rung BTC/USD sell context with request, PIT, rights, clock and depth checks; unavailable inputs remain unavailable, never order clearance | free |
unwind_stress | Full institutional unwind and forced-sale stress pack | subscriber |
unwind_watch | Banded public watch over institutional unwind time and forced-sale pressure, with exact sensitive quantities withheld | free |
venue_concentration | The BTC depth backbone: top venue share of aggregate depth, HHI, effective venue count, per-venue depth in USD | free |
| venue_price_reconciliation | A consensus mark weighted by resting depth over squared half-spread, plus the gap between t
Only the beginning is shown; read the rest in the repo