Open financial research infrastructure · v0.1.2
One read-only route into four evidence systems.
Financial Evidence connects terminal and agent workflows to LiquiLens, Undertow, Seiche, and Palimpsest. It routes each question to the relevant public evidence without inventing a universal score, hiding an unavailable source, or requiring an account or API key.
- Topics
- 5
- Products
- 4
- MCP tools
- 3
- Credentials
- 0
Deterministic topic routing
What should I use for each financial research question?
Use Seiche for money and capital markets, LiquiLens for covered bank and lender risk, Undertow for market liquidity, and Palimpsest plus Seiche for China-economy evidence. The router preserves separate documents, source URLs, retrieval clocks, byte counts, content hashes, and explicit error states.
| Question | Product route | Evidence boundary |
|---|
| Money markets and system funding | Seiche | Observed or unavailable |
| Capital markets | Seiche | Observed, derived, or unavailable |
| China economy | Palimpsest + Seiche | Revision-safe observations and bounded structural context |
| Covered bank and lender risk | LiquiLens | Observed, derived, or unavailable |
| Market depth and exit liquidity | Undertow | Observed, derived, or unavailable |
Terminal-first
How do I install Financial Evidence?
On macOS or Linux, install the checksum-pinned Homebrew formula. On any system with uv, run the signed Git tag directly. Both methods expose the same CLI and read-only stdio MCP server.
Homebrew
brew install beepboop2025/tap/financial-evidence
financial-evidence fetch --topic money-market --topic china-economy
Run without installing
uvx --from git+https://github.com/beepboop2025/financial-evidence-skills.git@v0.1.2 \
financial-evidence route --topic capital-market --format table
Shell-safe output is available as JSON, NDJSON, CSV, or a human-readable table. Exit code 0 means complete, 1 means partial, and 2 means unavailable.
Use it where financial work already happens
Which terminals and financial tools can use it?
Financial Evidence has native surfaces for shell automation, VS Code, Cursor, and MCP agents, plus compatibility layers for OpenBB, DuckDB, Excel Power Query, and FDC3 app directories. The compatibility files are open and self-hostable; they do not claim endorsement or marketplace listing by those vendors.
Terminal
Homebrew, uvx, persistent uv tools, completions for Bash, Zsh, and Fish, and stable pipeline exit codes.
MCP
Three read-only tools, an official registry record, multi-architecture container, root .mcp.json for Copilot Agent Host and compatible clients, and a one-click MCP Bundle.
VS Code
A workspace servers config, protocol install URL, and code --add-mcp command, all pinned to v0.1.2.
Cursor
A workspace mcpServers config and base64-encoded install deeplink pinned to the same stdio server.
OpenBB
Registered routes for Python, notebook, REST, and MCP surfaces after installing the optional extension.
DuckDB
Six HTTP-backed views that keep the four products separate and queryable with SQL.
Excel
A Power Query function that returns topic evidence to ordinary workbooks without a custom add-in.
FDC3
A public Evidence Inspector receives and broadcasts declared standard contexts through window.fdc3, with a matching FDC3 2.0 app-directory record.
Open the FDC3 Evidence Inspector
VS Code CLI
code --add-mcp '{"name":"financial-evidence","type":"stdio","command":"uvx","args":["--from","git+https://github.com/beepboop2025/financial-evidence-skills.git@v0.1.2","financial-evidence-mcp"]}'
Install uv first, then review the exact local command and source before accepting editor install, trust, or tool-use prompts. Cursor asks for tool approval by default. VS Code normally asks you to trust a server on first start, but its inline mcp.json start action can skip that prompt. These are self-install routes, not vendor marketplace listings. The FDC3 record likewise does not imply FINOS review or directory acceptance.
Machine-readable: integration manifest · llms.txt · pricing · MCP metadata
Evidence, not advice
What does Financial Evidence deliberately refuse to do?
It does not provide investment advice, security recommendations, execution quotes, credit ratings, or guarantees. It never converts missing, failed, restricted, or unavailable evidence into zero or calm. Source publishers retain their rights, and fetched JSON is treated as untrusted data rather than executable instructions.
- Fixed HTTPS source allowlist and redirect rejection.
- Bounded response size and explicit retrieval clocks.
- Separate product documents and content SHA-256 values.
- No account, API key, write action, trade action, or custody action.