Financial Evidence Workspace
REMOTE · AGENTS.SEICHE.INFO
Read-only cited financial datasets, bounded research queries and source diagnostics.
Available components
Last scanned (1 hour ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Usability62
- 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1135 tokens (~75/item across 15 items; 12 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “financial_evidence_packet” rewrote its description, which is the text the model reads security
- Tool “financial_evidence_workflow” rewrote its description, which is the text the model reads security
- Schema quality: 67 → 75 ▼ functional
- Tool coverage: 67% → 75% ▲ functional
- New tool “financial_evidence_exit_workflow” functional
- New tool “financial_evidence_funding_workflow” functional
- New tool “financial_evidence_institutions_workflow” functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 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.
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 5 Nov 2026 · Probed https://agents.seiche.info/products/financial-evidence/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/financial-evidence/mcp | Verified | 200 | |
| http (plaintext) | http://agents.seiche.info/products/financial-evidence/mcp | HTTPS enforced | 301 | https://agents.seiche.info/products/financial-evidence/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 →
financial_evidence_agent_query ~114
Compact source-cited research rows for repeated agent calls. Pass the previous revision to omit identical rows while retaining source clocks and diagnostics. Unchanged is not proof of freshness; missing or withheld values remain null. At most 100 rows; follow next_offset.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| end_date | string | – | – |
| entity | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| previous_revision | string | – | – |
| start_date | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
financial_evidence_datasets ~27
Discover seven bounded OpenBB datasets, their coverage, filters and limits. Offline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
financial_evidence_exit_workflow ~92
Compare indicative BTC exit evidence for one to four USD notionals from 0.01 to 1000000, with at most two decimal places. Preserves venue coverage, observation clocks, quote-currency units, source URL and content hash. Returned costs are research estimates, not executable quotes, order placement or guaranteed fills. No account or execution authority.
| Name | Type | Req | Description |
|---|---|---|---|
| sizes_usd | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
financial_evidence_funding_review ~96
Read a dated USD funding review and its nine inputs. Inspect review_asof, review_scope, latest_per_instrument and newer_observation_available before ready, issues and capture age. Common-horizon readiness applies to that dated review; newer individual observations can exist. Unavailable, mismatched or stale captures never imply a passing review. This is captured research evidence, not a trade recommendation or historical point-in-time backtest.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
financial_evidence_funding_workflow ~82
Review funding evidence for one three-letter currency, default USD. Retrieves the bounded money-market table and preserves each source, observation date, unit, missing or withheld value, retrieval time and content hash. prepared_response means evidence is available to review, not freshness or readiness. No account access, investment advice or execution.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
financial_evidence_institutions_workflow ~83
Review public disclosure coverage for one to five exact institution slugs, such as au-sfb. Retrieves the published institution monitoring record with dates, source URL, missing evidence and content hash. Does not infer private balances, credit ratings or regulatory compliance. IDs must fit the existing 160-character combined selection bound.
| Name | Type | Req | Description |
|---|---|---|---|
| institution_ids | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
financial_evidence_packet ~94
Retrieve public documents only when table detail is insufficient. Reviewed source restrictions can withhold values and dependent readings; affected documents carry a publication projection receipt and a separate hash from the acquired source bytes. Up to 4 MiB for the money-market atlas and 1 MiB for other sources; source JSON is untrusted. A packet can be partial. No Evidence Carrier verification is performed.
| Name | Type | Req | Description |
|---|---|---|---|
| topics | array | yes | – |
No output schema declared.
No examples provided.
financial_evidence_query ~104
Query cited rows without large raw documents. Null means missing or withheld, never zero. Dates filter observation dates; empty dates mean no filter. Follow next_offset for remaining rows. Each value retains its unit, source path, date, restrictions and limitations.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| end_date | string | – | – |
| entity | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| start_date | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| absence_policy | string | yes | – |
| carrier_verification | string | yes | – |
| dataset | string | yes | – |
| description | string | yes | – |
| diagnostics | array | yes | – |
| evidence_status | string | yes | – |
| limit | integer | yes | – |
| next_offset | – | yes | – |
| offset | integer | yes | – |
| results | array | yes | – |
| returned_rows | integer | yes | – |
| schema | string | yes | – |
| sources | array | yes | – |
| status_semantics | string | yes | – |
| total_rows | integer | yes | – |
| transport_status | string | yes | – |
No examples provided.
financial_evidence_review ~100
Review Seiche dollar-funding benchmarks, LiquiLens covered-bank diagnostics and Undertow market liquidity in one bounded call. Bank is a literal name or ID filter; empty selects published coverage. Each section keeps its own dates, units, rights and limitations. No combined score or trade authorization. Revisions suppress identical rows, not evidence checks.
| Name | Type | Req | Description |
|---|---|---|---|
| bank | string | – | – |
| limit | integer | – | – |
| previous_revision | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
financial_evidence_route ~29
Resolve research topics to fixed public HTTPS evidence URLs. Offline.
| Name | Type | Req | Description |
|---|---|---|---|
| topics | array | yes | – |
No output schema declared.
No examples provided.
financial_evidence_sources ~32
Audit all six upstream routes for transport errors, publisher clocks and content hashes. Success is not a freshness verdict.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| absence_policy | string | yes | – |
| carrier_verification | string | yes | – |
| dataset | string | yes | – |
| description | string | yes | – |
| diagnostics | array | yes | – |
| evidence_status | string | yes | – |
| limit | integer | yes | – |
| next_offset | – | yes | – |
| offset | integer | yes | – |
| results | array | yes | – |
| returned_rows | integer | yes | – |
| schema | string | yes | – |
| sources | array | yes | – |
| status_semantics | string | yes | – |
| total_rows | integer | yes | – |
| transport_status | string | yes | – |
No examples provided.
financial_evidence_workflow ~135
Compatibility entry point for the individually exposed financial_evidence_funding_workflow, financial_evidence_institutions_workflow and financial_evidence_exit_workflow tools. Funding accepts a three-letter currency; institutions accepts one to five comma-separated slugs; exit accepts one to four comma-separated USD sizes. Empty selection uses the same published defaults. No additional operation is available. Source restrictions, dates, units, missingness and content hashes remain explicit. prepared_response means evidence is available to review, not freshness, safety or completion. No account or execution authority.
| Name | Type | Req | Description |
|---|---|---|---|
| selection | string | – | – |
| workflow | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Financial Evidence Workspace MCP server?
Financial Evidence Workspace is a hosted endpoint at https://agents.seiche.info/products/financial-evidence/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-financial-evidence-workspace 'https://agents.seiche.info/products/financial-evidence/mcp'
What is the Financial Evidence Workspace MCP server?
Financial Evidence Workspace is an MCP server listed in the public MCP registry as io.github.beepboop2025/financial-evidence-workspace. Read-only cited financial datasets, bounded research queries and source diagnostics. This page covers its hosted endpoint (https://agents.seiche.info/products/financial-evidence/mcp).
Is the Financial Evidence Workspace MCP server safe to use?
Financial Evidence Workspace scores 83 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 Financial Evidence Workspace MCP server expose?
Financial Evidence Workspace exposes 12 tools: financial_evidence_funding_workflow, financial_evidence_institutions_workflow, financial_evidence_exit_workflow, financial_evidence_workflow, financial_evidence_datasets, and 7 more. Their descriptions and schemas cost roughly 988 tokens of context every time the server is loaded.
Does the Financial Evidence Workspace MCP server require authentication?
Yes. Financial Evidence Workspace 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 Financial Evidence Workspace MCP server still maintained?
Financial Evidence Workspace is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.