Seiche — funding-stress terminal
REMOTE · API.SEICHE.INFO · 2 COMPONENTS · SCANNED AUG 3
Funding stress early warning for US money markets from free public data, with an honest backtest.
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 →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability85
- 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 1238 tokens (~112/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.seiche.info
claude mcp add --transport http beepboop2025-seiche https://api.seiche.info/mcp
[mcp_servers.beepboop2025-seiche] url = "https://api.seiche.info/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"beepboop2025-seiche": {
"type": "remote",
"url": "https://api.seiche.info/mcp",
"enabled": true
}
}
} openclaw mcp add beepboop2025-seiche --url https://api.seiche.info/mcp --transport streamable-http
mcp_servers:
beepboop2025-seiche:
url: "https://api.seiche.info/mcp" {
"mcpServers": {
"beepboop2025-seiche": {
"type": "http",
"url": "https://api.seiche.info/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.
- 3 Aug 26 0
- Schema quality: 1106 → 1238 ▼ functional
- New tool “institutional_flows” functional
- 2 Aug 26 +9
- Authorization: unverified → partial ▲ security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “is_now_dangerous” functional
- New prompt “funding_stress_briefing” functional
- New prompt “crisis_replay” functional
- Server version: 0.7.1 → 0.8.0 functional
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +2
- Tool “historical_analogs” rewrote its description, which is the text the model reads security
- Tool “funding_stress_forecast” rewrote its description, which is the text the model reads security
- Tool “positioning_book” rewrote its description, which is the text the model reads security
- Tool “ask_desk” rewrote its description, which is the text the model reads security
- Tool “replay_asof” rewrote its description, which is the text the model reads security
- Tool “desk_brief” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Schema quality: good → excellent functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
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 3 Aug 2026 · Probed https://api.seiche.info/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 | 9 Jul 2026 | 7 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5124ecbed078faee1a2903ca8d3b4470ad0 |
| 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 |
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=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.seiche.info/mcp | Verified | 200 | |
| http (plaintext) | http://api.seiche.info/mcp | HTTPS enforced | 308 | https://api.seiche.info/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.
ask_desk Ask the desk assistant (grounded) ~68
Ask a natural-language question about funding conditions, answered strictly from the live board with the grounding cited. Requires an LLM endpoint configured on the server; if none is configured the tool says so instead of guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | Your question about funding conditions (1-600 chars). |
No output schema declared.
No examples provided.
crypto_stress_record Wrecks: crypto episodes vs the funding board ~96
Labelled crypto stress episodes (Black Thursday 2020, Terra, FTX, the SVB/USDC weekend, the Oct-2025 liquidation cascade, the Ethena unwind) replayed point-in-time against the dollar-funding board. External wrecks show transmission; crypto-native wrecks show the board correctly staying quiet. Use for any 'does TradFi funding stress reach crypto' question, grounded in the record.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
data_health Data freshness & provenance ~46
Freshness, provenance, and fault status for every underlying series (FRED, NY Fed, OFR, Treasury). Call this to confirm the board is current before relying on a reading.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
desk_brief This morning's desk note (markdown) ~49
The full human-readable desk brief for today as markdown, a narrative summary of the whole board. Good when you want prose to quote or summarise rather than structured fields. Built from free public data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
funding_stress_forecast Forward odds of a funding-stress event ~99
Forward odds of a funding-stress event over the next 5/10/21 business days from six independent views: three P(event) models (term structure, first-passage physics, gradient boosting) and three stochastic scenarios on the index (regime-transition Markov, OU plus jump analytic marginal, Monte Carlo path fan). Agreement across views is the signal. Built from free public data. Use for any forward-looking liquidity-risk question.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
funding_stress_now Current funding-stress read ~82
The live money-market funding-stress reading: a 0-100 composite index, the regime (CALM/EROSION/STRAIN/STRESS), per-component decomposition, the market-stress 'Tell', and any data faults. Ask this whenever an analysis touches US dollar funding, repo, reserves, the Fed's balance sheet, or liquidity conditions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
historical_analogs Nearest historical analogs ~60
The historical days most similar to today's funding conditions, and how often those analogs led to a stress event, plus a novelty flag for whether today has any close precedent. Use to ground a 'what usually happens from here' question in real history.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
institutional_flows Institutional flows: who is positioned where ~132
Hedge-fund / pension / sovereign positioning nowcast from public prints: the Treasury basis-trade size proxy (CFTC leveraged-fund net short, with a funding-fragility flag), asset-manager duration demand, foreign-official custody flows (H.4.1), a mixed-frequency fused positioning index with uncertainty bands, and how self-exciting stress events currently are (Hawkes branching ratio). Weekly cadence, point-in-time. Ask this when a question involves hedge fund leverage, the basis trade, pension duration bids, or sovereigns buying/selling Treasuries. Built from free public data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
positioning_book The Book: implied stance & positions ~62
The stance (risk_on / risk_off / neutral) and positions implied by the stress read, with the walk-forward Sharpe, the live as-published record, and the ensemble event odds. Not investment advice, a codified reading. Built from free public data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
proof_backtest PROOF: the honest track record ~60
The backtest scoreboard, stated honestly: recall and precision with 95% confidence intervals over labelled funding events, an orthogonal robustness test, every named episode (hits and misses), and the caveats. Use to judge how much to trust the readings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
replay_asof Time Machine: the board on a past date ~108
Reconstruct the entire funding-stress board as it read on a historical date, point-in-time with no lookahead: the composite, the regime, the per-component decomposition and the crunch windows for that date. Use to test whether Seiche would have flagged a past liquidity episode, or to align a backtest with what was knowable then. Built from free public data.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Calendar date as YYYY-MM-DD (e.g. 2019-09-17). |
No output schema declared.
No examples provided.