# Financial Evidence (remote · liquilens.in)

Read-only public financial evidence from LiquiLens, Undertow, Seiche and Palimpsest.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `liquilens.in`: 84/100 (this document), [markdown](https://verifymcp.io/servers/beepboop2025-financial-evidence/mcp-financial-evidence.md), [page](https://verifymcp.io/servers/beepboop2025-financial-evidence/mcp-financial-evidence)
- oci · `ghcr.io/beepboop2025/financial-evidence-skills:0.1.5`: 44/100, [markdown](https://verifymcp.io/servers/beepboop2025-financial-evidence/ghcr-io-beepboop2025-financial-evidence-skills-0-1-5.md), [page](https://verifymcp.io/servers/beepboop2025-financial-evidence/ghcr-io-beepboop2025-financial-evidence-skills-0-1-5)

## Channel facts

- Endpoint: `https://liquilens.in/mcp/financial-evidence`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.5`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 135 tokens (~45/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http beepboop2025-financial-evidence 'https://liquilens.in/mcp/financial-evidence'
```

### Cursor

```json
{
  "mcpServers": {
    "beepboop2025-financial-evidence": {
      "url": "https://liquilens.in/mcp/financial-evidence"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "beepboop2025-financial-evidence": {
      "type": "http",
      "url": "https://liquilens.in/mcp/financial-evidence"
    }
  }
}
```

### Codex

```toml
[mcp_servers.beepboop2025-financial-evidence]
url = "https://liquilens.in/mcp/financial-evidence"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "beepboop2025-financial-evidence": {
      "type": "remote",
      "url": "https://liquilens.in/mcp/financial-evidence",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add beepboop2025-financial-evidence --url 'https://liquilens.in/mcp/financial-evidence' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  beepboop2025-financial-evidence:
    url: "https://liquilens.in/mcp/financial-evidence"
```

### Netclaw

```json
{
  "McpServers": {
    "beepboop2025-financial-evidence": {
      "Transport": "http",
      "Url": "https://liquilens.in/mcp/financial-evidence"
    }
  }
}
```

### Vellum

```bash
assistant mcp add beepboop2025-financial-evidence -t streamable-http -u 'https://liquilens.in/mcp/financial-evidence'
```

### Other

```json
{
  "mcpServers": {
    "beepboop2025-financial-evidence": {
      "type": "http",
      "url": "https://liquilens.in/mcp/financial-evidence"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 84, +1)

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

### 2026-09-17 (score 83, +1)

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

### 2026-09-15 (score 82, +1)

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

### 2026-09-13 (score 81, +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.

### 2026-09-10 (score 80, +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.

### 2026-09-08 (score 79, +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.

### 2026-09-06 (score 78, +1)

- [security] 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
- [functional regression] Schema quality: 40 → 45
- [functional] Server version: 0.1.4 → 0.1.5

### 2026-09-05 (score 77, +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.

## MCP tools (3)

### `financial_evidence_topics` (~25 tokens)

List Financial Evidence Topics

List supported topics and their fixed public raw-JSON routes without network access.

### `financial_evidence_route` (~35 tokens)

Route Financial Research

Resolve one or more financial research topics to fixed public raw-JSON sources without fetching them.

Input parameters:

- `topics` (array, required)

### `financial_evidence_fetch` (~75 tokens)

Fetch Financial Evidence

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.

Input parameters:

- `max_bytes` (integer)
- `timeout` (number)
- `topics` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/beepboop2025-financial-evidence/mcp-financial-evidence#diagnostics

## Score history

- 2026-09-20: 84
- 2026-09-19: 84
- 2026-09-18: 83
- 2026-09-17: 83
- 2026-09-16: 82
- 2026-09-15: 82
- 2026-09-14: 81
- 2026-09-13: 81
- 2026-09-12: 80
- 2026-09-11: 80
- 2026-09-10: 80
- 2026-09-09: 79
- 2026-09-08: 79
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 77
- 2026-09-04: 76
- 2026-09-03: 76
- 2026-09-02: 75
- 2026-09-01: 75
- 2026-08-31: 74
- 2026-08-30: 74
- 2026-08-29: 73
- 2026-08-28: 73
- 2026-08-27: 72
- 2026-08-26: 72
- 2026-08-25: 69
- 2026-08-24: 69

## Common questions

### 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 84 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://liquilens.in/mcp/financial-evidence
- Repository: https://github.com/beepboop2025/financial-evidence-skills
- Changelog RSS feed: https://verifymcp.io/servers/beepboop2025-financial-evidence/mcp-financial-evidence.xml
- Changelog JSON feed: https://verifymcp.io/servers/beepboop2025-financial-evidence/mcp-financial-evidence.json
- HTML version of this page: https://verifymcp.io/servers/beepboop2025-financial-evidence/mcp-financial-evidence