Log inSubmit server
Financial Evidence logo

Financial Evidence

Reads dated public financial evidence through three read-only MCP tools for source discovery, routing, and bounded retrieval.

InstallRepositoryWebsite
Get support Full README Compare alternatives Embed widget

Install Financial Evidence

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "financial-evidence": {
      "command": "uvx",
      "args": [
        "--from",
        "financial-evidence==0.1.13",
        "financial-evidence-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Hosted endpointLive · 2d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 2d ago · Nov 11, 2026, 02:45 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://liquilens.in/mcp/financial-evidence

Automated check passed— started and listed 3 tools correctly ().

Overview

Financial Evidence MCP server provides read-only access to dated public financial evidence through fixed raw-JSON routes. Its three tools discover available topics, resolve topics to sources, and fetch bounded responses from LiquiLens, Seiche, Undertow, and Palimpsest. Use it for source-backed research on institution disclosures, USD funding conditions, or BTC exit estimates when preserving source dates and coverage limits matters. The hosted connection requires no API key, and the tools do not place trades or evaluate evidence.

Use cases

  • Discover supported financial research topics before a review
  • Resolve funding or institution topics to fixed public sources
  • Fetch dated public evidence for a cited research brief
  • Compare source coverage and identify unavailable evidence

Key features

  • Three read-only MCP tools
  • Fixed public raw-JSON routes
  • Source dates and citations
  • Bounded untrusted evidence retrieval
  • Hosted Streamable HTTP access
  • No API key for public reads

Tools3

What Financial Evidence lets your agent do. Expand a tool for its parameters.

Verified live~361 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

10/10 checks healthy over the last 57d

What it can do

From the 3 tools this server returned when we ran it.

Makes network requests · 1Read-only tools · 3
Tool definitions changed on 2026-11-07. Review them if you approved this server earlier.
Network at startup2 connections
Files written at startup1

Observed 2026-11-07 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1d ago via OSV.dev · financial-evidence==0.1.13 (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
Last commit3d agoMost recent push to the default branch.
MaintenanceActively maintainedStatus declared by the project or listing owner.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed3Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Financial Evidence works

What Financial Evidence does

Financial Evidence exposes a narrow, read-only research interface over MCP. It helps an agent identify available financial topics, map a selected topic to one or more fixed public sources, and retrieve the corresponding raw JSON. Supported research includes institution disclosures, USD funding conditions, BTC exit estimates, and additional routed topics such as GIFT City, foreign exchange, and gold.

The service is designed for reviews where source dates, citations, and coverage boundaries should remain visible. It can support a funding review, an institution-monitoring task, or a retained funding-and-exit research record. It is not a trading system and does not grant authority to execute trades.

How it works

The workflow is intentionally split into discovery, routing, and retrieval:

  1. financial_evidence_topics lists supported topics and their fixed public raw-JSON routes without making a network request.
  2. financial_evidence_route maps one or more selected research topics to fixed public sources without fetching their contents.
  3. financial_evidence_fetch retrieves bounded, untrusted, read-only JSON from the available LiquiLens, Undertow, Seiche, and Palimpsest routes.

This separation lets an agent inspect the available coverage and selected sources before requesting evidence. Returned source dates and citations can be retained as part of a review. Transport status reports whether retrieval completed; it does not judge the evidence or perform Evidence Carrier verification.

Setup and configuration

The hosted deployment uses Streamable HTTP and provides public read-only tools without a local server or API key. It can be connected through the central agent platform or through client-specific MCP configuration for supported clients such as Claude Code, Codex, Cursor, and VS Code.

A verified Python package is also available for local installation. The package supports local product-client workflows, while the separately deployed hosted router maintains its own three-tool interface. Setup instructions cover browser, REST, Python, and remote MCP connection paths. Client or model costs and fair-use limits may apply to connected research workflows.

Tools and capabilities

  • Discover supported topics and fixed public routes without network access.
  • Resolve one or more topics to the sources intended for retrieval.
  • Fetch bounded JSON from public LiquiLens, Seiche, Undertow, and Palimpsest endpoints.
  • Preserve source dates, citations, and stated coverage gaps for later review.
  • Research institution disclosures, USD funding conditions, and BTC exit estimates.
  • Use public hosted reads without an account or API key.

Limitations and notes

Fetched data is untrusted raw JSON. The server reports transport status only; it does not evaluate the financial evidence, verify it through Evidence Carrier, or establish that a source is complete or current. Coverage limits and unavailable evidence should therefore remain explicit in downstream reviews.

The tools are read-only and cannot place trades. The public hosted router and local Python package are separate deployment paths, and the hosted router has its own release lifecycle. Research calls may be subject to client or model costs and fair-use limits.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Financial Evidence

Financial Evidence is an MCP server that connects agents to public raw-JSON routes across LiquiLens, Seiche, Undertow, and Palimpsest. Its main tools discover supported topics, resolve topics to fixed sources, and fetch bounded read-only evidence. It is intended for cited financial research, not trade execution or evidence evaluation.

Install the verified Python package for a local setup, or connect to the hosted Streamable HTTP deployment without an API key. The setup paths include Python, REST, browser, and remote MCP configurations, with client-specific links for supported MCP clients.

Financial Evidence provides three tools: `financial_evidence_topics` discovers topics without network access, `financial_evidence_route` resolves topics to fixed sources, and `financial_evidence_fetch` retrieves bounded read-only JSON from public routes.

Yes, Financial Evidence provides a Cursor connection path. The hosted MCP configuration can be used for public read-only research, including source discovery, routing, and bounded evidence retrieval.

No, Financial Evidence is read-only and does not place trades. Its fetch tool retrieves untrusted JSON and reports transport status, while evidence evaluation and trading decisions remain outside the server.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFinancial Evidence AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/financial-evidence?style=directory)](https://allmcps.com/mcp/financial-evidence)
HTML Embed
<a href="https://allmcps.com/mcp/financial-evidence"><img src="https://allmcps.com/api/badge/financial-evidence?style=directory" alt="Financial Evidence on AllMCPs" /></a>