Yolfi Agent vs Undertow — market liquidity map
A side-by-side look at the Yolfi Agent and Undertow — market liquidity map MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Yolfi Agent for finance & fintech work as a local process; choose Undertow — market liquidity map for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Yolfi Agent when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
YOLFI_API_KEY, YOLFI_CONFIG_HOME, YOLFI_REGISTRATION_IDEMPOTENCY_KEY.
Choose Undertow — market liquidity map when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
agent_access_status, crypto_exit_check, crypto_funding_cost.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 56/100 · Good | 79/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Freemium |
| Required env vars | YOLFI_API_KEYYOLFI_CONFIG_HOMEYOLFI_REGISTRATION_IDEMPOTENCY_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 178 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 16 |
| Full listing | View Yolfi Agent | View Undertow — market liquidity map |
Tools & capabilities
Yolfi Agent tools
No tool names declared yet. Check the project README from the listing page.
Undertow — market liquidity map tools 16
agent_access_statusIdentity, current entitlement, daily usage and access instructions; explains missing/refused subscriber tools.crypto_exit_checkCompare four BTC sell sizes by rung/bracket. Withholds stale/future, uncovered or unconverted venues. Fees excluded; no trade clearance.crypto_funding_costCaller-input perpetual funding, fees, net carry and linear break-even. Positive funding: longs pay shorts. Constant-rate scenario, not forecast.crypto_portfolio_stressCaller-input linear shocks for 20 exposures: P&L, equity, asset/venue concentration. Symbols are scenario labels. No liquidation/probability model.depth_episodesRealized BTC depth-collapse onset, trough, recovery under preregistered rules. Zero is distinct from missing. Subscriber exit_desk_full adds ETH.exit_costBTC nearest-rung sell estimates, interpolated bid-depth bands; fees excluded, not executable. crypto_exit_check compares sizes/freshness.gold_cash_realisationCalculate gold sale proceeds and cash gates from caller inputs. Decimal strings: kg, fineness (0,1], USD/troy-oz bid, USD fees, currency/USD FX (USD=1). Use aware ISO clocks. Returns arithmetic and withheld-cash reasons; no fetch, storage, execution or verified balance.latest_articleRead the latest published editorial: title, full text, URL, clock and quality receipt. No arguments. Missing text or failed receipt returns an error; no generated prose. Use liquidity_tiers for board data.liquidity_tiersNine segment tiers, Seiche funding, measure counts and replay/withholding reasons. PARTIAL means missing history or unpassed replay, never calm.market_corpus_contextInspect corpus coverage, rights and clocks. Summary takes no pagination; other views return records/total/next_offset. Retrieval age is not observation freshness. Use liquidity_tiers for market readings.research_networkFind cross-product source metadata, clocks, rights and next steps. Follow next_offset; unavailable flags retrieval, contract or size failure. Use market_corpus_context for local corpus counts. No shared score or authority.sealed_recordForward calls sealed/signed before outcomes: hits, misses, decided counts, ledger root. Report hits and misses together.- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Yolfi Agent
{
"mcpServers": {
"yolfinance-yolfi-agent": {
"command": "npx",
"args": [
"-y",
"@yolfi/agent"
],
"env": {
"YOLFI_API_KEY": "YOUR_YOLFI_API_KEY_HERE",
"YOLFI_CONFIG_HOME": "YOUR_YOLFI_CONFIG_HOME_HERE",
"YOLFI_REGISTRATION_IDEMPOTENCY_KEY": "YOUR_YOLFI_REGISTRATION_IDEMPOTENCY_KEY_HERE"
}
}
}
}
Undertow — market liquidity map
{
"mcpServers": {
"undertow-market-liquidity-map-2": {
"url": "https://api.seiche.info/undertow/mcp"
}
}
}
Frequently asked questions
Yolfi Agent is categorized under Finance & Fintech and uses a local stdio subprocess. Undertow — market liquidity map belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Yolfi Agent for finance & fintech work and Undertow — market liquidity map for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Yolfi Agent is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Undertow — market liquidity map is listed as freemium — a free tier with paid plans. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add yolfinance-yolfi-agent and undertow-market-liquidity-map-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Yolfi Agent has a quality signal of 56/100 (Good) with 2 views, 0 installs and 178 GitHub stars. Undertow — market liquidity map has 79/100 (Great) with 2 views, 0 installs and 0 GitHub stars.