Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Seiche, LiquiLens and Undertow source data

REMOTE · API.SEICHE.INFO

Funding histories, bank filings and settlement data with source receipts, units and capture clocks.

Available components

0 this week 85 Trust /100

Last scanned (23 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 495 tokens (~61/item across 8 items; 8 tools + 0 resources), lean.Pass
  • 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Server version: 1.2.0 → 1.3.0 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Oct 26 0
    • Schema quality: 375 → 495 ▼ functional
    • Server version: 1.1.0 → 1.2.0 functional
    • New tool “research_series_summary” functional
    • New tool “research_workspace” functional
  • 28 Sept 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
Diagnostics

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 21 Nov 2026 · Probed https://api.seiche.info/api/v2/research-data/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 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA384 589870bcfa2f6044445f1acc36ca8cced6d
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. DS published 9986 8 Verified
seiche.info. DS published 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
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/api/v2/research-data/mcp Verified 200
http (plaintext) http://api.seiche.info/api/v2/research-data/mcp HTTPS enforced 308 https://api.seiche.info/api/v2/research-data/mcp
MCP tools · 8 exposed · ~434 tokens

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 →

Tool Tokens
research_analysis ~30

Read descriptive funding, institution concentration and settlement analysis with input references and limits.

NameTypeReqDescription
productstring––

No output schema declared.

No examples provided.

research_catalog ~30

Discover scoped funding, institution and chain-settlement datasets with coverage and rights.

NameTypeReqDescription
productstring––

No output schema declared.

No examples provided.

research_entities ~51

Find regulator identifiers for institutions; names are not fuzzy-joined across regimes.

NameTypeReqDescription
datasetstringyes–
limitinteger––
offsetinteger––
qstring––

No output schema declared.

No examples provided.

research_observations ~86

Read cited observations or a captured historical vintage. Earlier point-in-time availability is not assumed.

NameTypeReqDescription
as_known_atstring––
datasetstringyes–
endstring––
entitystring––
limitinteger––
offsetinteger––
seriesstringyes–
startstring––

No output schema declared.

No examples provided.

research_series ~48

Search the metric catalog and native unit definitions in a dataset.

NameTypeReqDescription
datasetstringyes–
limitinteger––
offsetinteger––
qstring––

No output schema declared.

No examples provided.

research_series_summary ~75

Analyze the latest captured series for one exact entity, with adjacent change, trailing-window missingness, native units and source receipts. Current analytics are withheld for stale, unavailable or unverified inputs.

NameTypeReqDescription
datasetstringyes–
entitystring––
seriesstringyes–
windowinteger––

No output schema declared.

No examples provided.

research_tracked_institutions ~69

Search the existing Indian dossier and RBI registry populations, retaining financial-evidence gaps and source clocks. Populations overlap and are not a global census.

NameTypeReqDescription
limitinteger––
offsetinteger––
qstring––
scopestring––

No output schema declared.

No examples provided.

research_workspace ~45

Read the same coverage, source freshness, gaps and descriptive overview as the website. Compare snapshot_id across REST/MCP; independent source clocks remain explicit.

NameTypeReqDescription
productstring––

No output schema declared.

No examples provided.

Install

How do I install the Seiche, LiquiLens and Undertow source data MCP server?

Seiche, LiquiLens and Undertow source data is a hosted endpoint at https://api.seiche.info/api/v2/research-data/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

# add to Claude Code
claude mcp add --transport http beepboop2025-financial-source-data 'https://api.seiche.info/api/v2/research-data/mcp'
Common questions

What is the Seiche, LiquiLens and Undertow source data MCP server?

Seiche, LiquiLens and Undertow source data is an MCP server listed in the public MCP registry as io.github.beepboop2025/financial-source-data. Funding histories, bank filings and settlement data with source receipts, units and capture clocks. This page covers its hosted endpoint (https://api.seiche.info/api/v2/research-data/mcp).

Is the Seiche, LiquiLens and Undertow source data MCP server safe to use?

Seiche, LiquiLens and Undertow source data scores 85 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 Seiche, LiquiLens and Undertow source data MCP server expose?

Seiche, LiquiLens and Undertow source data exposes 8 tools: research_workspace, research_series_summary, research_tracked_institutions, research_catalog, research_series, and 3 more. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.

Does the Seiche, LiquiLens and Undertow source data MCP server require authentication?

No. We connected to Seiche, LiquiLens and Undertow source data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Seiche, LiquiLens and Undertow source data MCP server still maintained?

Seiche, LiquiLens and Undertow source data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Seiche, LiquiLens and Undertow source data MCP server?

VerifyMCP ran 13 checks on Seiche, LiquiLens and Undertow source data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.