Financial Evidence
REMOTE · LIQUILENS.IN · 3 COMPONENTS
Read-only public financial evidence from LiquiLens, Undertow, Seiche and Palimpsest.
Last scanned (9 hours ago)
Scores higher than 93% 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 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 135 tokens (~45/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 2 Nov 26 0
- Server version: 0.1.8 → 0.1.16 functional
- 13 Oct 26 0
- Server version: 0.1.7 → 0.1.8 functional
- 9 Oct 26 0
- Server version: 0.1.6 → 0.1.7 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
- 25 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
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 6 Sept 26 0
- Tool “financial_evidence_topics” rewrote its description, which is the text the model reads security
- Tool “financial_evidence_fetch” rewrote its description, which is the text the model reads security
- Tool “financial_evidence_route” rewrote its description, which is the text the model reads security
- Schema quality: 40 → 45 ▼ functional
- Server version: 0.1.4 → 0.1.5 functional
- 26 Aug 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
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://liquilens.in/mcp/financial-evidence
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=liquilens.in | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ee157c9196903fbb13fe35b54d50c539 |
| SANs: liquilens.in, demo.liquilens.in, *.demo.liquilens.in | ||||||
| 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 liquilens.in. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| liquilens.in. | present | 2371 | 13 | Verified |
| liquilens.in. | 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 |
| 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://liquilens.in/mcp/financial-evidence | Verified | 200 | |
| http (plaintext) | http://liquilens.in/mcp/financial-evidence | HTTPS enforced | 301 | https://liquilens.in/mcp/financial-evidence |
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_fetch Fetch Financial Evidence ~75
Fetch bounded untrusted read-only JSON from fixed LiquiLens, Undertow, Seiche, and Palimpsest routes. Status reports transport only; evidence is not evaluated and Evidence Carrier verification is not performed.
| Name | Type | Req | Description |
|---|---|---|---|
| max_bytes | integer | – | – |
| timeout | number | – | – |
| topics | array | yes | – |
No output schema declared.
No examples provided.
financial_evidence_route Route Financial Research ~35
Resolve one or more financial research topics to fixed public raw-JSON sources without fetching them.
| Name | Type | Req | Description |
|---|---|---|---|
| topics | array | yes | – |
No output schema declared.
No examples provided.
financial_evidence_topics List Financial Evidence Topics ~25
List supported topics and their fixed public raw-JSON routes without network access.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Financial Evidence MCP server?
Financial Evidence is a hosted endpoint at https://liquilens.in/mcp/financial-evidence, 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 · liquilens.in
claude mcp add --transport http beepboop2025-financial-evidence 'https://liquilens.in/mcp/financial-evidence'
What is the Financial Evidence MCP server?
Financial Evidence is an MCP server listed in the public MCP registry as io.github.beepboop2025/financial-evidence. Read-only public financial evidence from LiquiLens, Undertow, Seiche and Palimpsest. This page covers its hosted endpoint (https://liquilens.in/mcp/financial-evidence).
Is the Financial Evidence MCP server safe to use?
Financial Evidence scores 86 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 MCP server expose?
Financial Evidence exposes 3 tools: financial_evidence_topics, financial_evidence_route, financial_evidence_fetch. Their descriptions and schemas cost roughly 135 tokens of context every time the server is loaded.
Does the Financial Evidence MCP server require authentication?
No. We connected to Financial Evidence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Financial Evidence MCP server still maintained?
Financial Evidence 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.