Seiche Market Atlas Corpus
REMOTE · AGENTS.SEICHE.INFO
Read-only corpus catalogs and bounded observations with source dates and rights metadata.
Available components
Last scanned (19 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Data and Analytics
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 Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 388 tokens (~43/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 4% 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 9 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
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 4 Nov 2026 · Probed https://agents.seiche.info/products/seiche-market-corpus/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=seiche.info | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | bfd8d8f81d623d3a0e1e2003c71ad25e |
| SANs: seiche.info, agents.seiche.info, *.agents.seiche.info | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of agents.seiche.info. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| info. | present | 9986 | 8 | Verified |
| seiche.info. | present | 2371 | 13 | Verified |
| agents.seiche.info. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; script-src 'self'; style-src 'self'; connect-src 'self'; img-src 'self' data:; base-uri 'self'; frame-ancestors 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agents.seiche.info/products/seiche-market-corpus/mcp | Verified | 200 | |
| http (plaintext) | http://agents.seiche.info/products/seiche-market-corpus/mcp | HTTPS enforced | 301 | https://agents.seiche.info/products/seiche-market-corpus/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 →
bis_flow_manifest ~33
Discover the complete content-addressed BIS shard inventory; binary shards remain REST downloads
| Name | Type | Req | Description |
|---|---|---|---|
| flow_id | string | yes | – |
No output schema declared.
No examples provided.
bis_observations ~33
Read bounded, revision-aware BIS observations
| Name | Type | Req | Description |
|---|---|---|---|
| flow_id | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
bis_records ~49
Browse bounded full-fidelity BIS records; use the flow manifest and shard URLs for complete transfer
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| flow_id | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
corpus_catalog ~18
Summarize every registered corpus and evidence class
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
corpus_health ~16
Check the corpus service and storage roots
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inspect_dataset ~27
Inspect one canonical public-index dataset without reading raw storage
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
No output schema declared.
No examples provided.
list_datasets ~79
List versioned datasets with rights and product eligibility
| Name | Type | Req | Description |
|---|---|---|---|
| acquisition_review | string | – | – |
| collection_kind | string | – | – |
| cursor | string | – | – |
| data_class | string | – | – |
| engine | string | – | – |
| group | string | – | – |
| limit | integer | – | – |
| publication_state | string | – | – |
No output schema declared.
No examples provided.
seiche_markets ~18
List normalized Seiche money-market coverage
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
seiche_observations ~115
Read bounded canonical Seiche rows after source-wide redistribution validation
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| event_from | string | – | – |
| event_to | string | – | – |
| instrument_id | string | – | – |
| knowledge_at | string | – | – |
| limit | integer | – | – |
| market | string | yes | – |
| quality | string | – | – |
| semantic_role | string | – | – |
| source | string | yes | Exact Seiche source-adapter partition id |
| staleness | string | – | – |
No output schema declared.
No examples provided.
How do I install the Seiche Market Atlas Corpus MCP server?
Seiche Market Atlas Corpus is a hosted endpoint at https://agents.seiche.info/products/seiche-market-corpus/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 · agents.seiche.info
claude mcp add --transport http beepboop2025-seiche-market-corpus 'https://agents.seiche.info/products/seiche-market-corpus/mcp'
What is the Seiche Market Atlas Corpus MCP server?
Seiche Market Atlas Corpus is an MCP server listed in the public MCP registry as io.github.beepboop2025/seiche-market-corpus. Read-only corpus catalogs and bounded observations with source dates and rights metadata. This page covers its hosted endpoint (https://agents.seiche.info/products/seiche-market-corpus/mcp).
Is the Seiche Market Atlas Corpus MCP server safe to use?
Seiche Market Atlas Corpus scores 78 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 Market Atlas Corpus MCP server expose?
Seiche Market Atlas Corpus exposes 9 tools: corpus_catalog, list_datasets, inspect_dataset, bis_observations, bis_records, and 4 more. Their descriptions and schemas cost roughly 388 tokens of context every time the server is loaded.
Does the Seiche Market Atlas Corpus MCP server require authentication?
Yes. Seiche Market Atlas Corpus asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Seiche Market Atlas Corpus MCP server still maintained?
Seiche Market Atlas Corpus is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.