Financial Evidence Skills MCP Server

Financial Evidence Agent Skills

Verified release 0.1.7: the published package and public MCP router support gift-city, forex and gold alongside the five existing research topics. GIFT City serves gold and treasury desks, investors/fund managers, and banks/IFSC institutions. The helper reads fixed public context; gold/FX calculations remain explicit user-input steps. See topic routing and the release verification record.

Use your existing tools: the research tool hub provides a complete capture client, notebook, flat Excel/Power BI query and MCP project defaults for LiquiLens, Seiche and Undertow. Download the kit or connect the hosted OpenBB desk. Institutional vendor acceptance remains separate.

OpenBB Research Desk, hosted Workspace 1.1.1. Seven cited datasets, a seven-tab Workspace app, an archived USD funding review, benchmark history charts, typed REST responses and an eight-tool MCP server connect all four projects. The hosted service is https://api.seiche.info/openbb. Install .[openbb,workspace] from this checkout, then run openbb-build and financial-evidence-api. The optional modules are included in the v0.1.7 wheel; the public router retains its separate three-tool contract. The hosted Workspace release identifies its exact source commit independently at /api/v1/release.

Check a captured USD funding review: the funding review checks compare required inputs, units, publication clocks and own-series observations across Seiche surfaces. The dated SOFR-IORB review exposes newer individual source dates; it does not claim the latest print for every instrument. Missing, overdue or contradictory evidence requires attention. Passing these checks is not an institutional-readiness certification.

Run recurring research: install the durable runtime for fixed policies, bounded scheduling, retained receipts, private MCP and backup recovery across LiquiLens, Seiche and Undertow.

Automate funding research: versioned packets, captured changes, Python, OpenBB and a local agent tool. Public access requires no account; optional application keys use explicit measurement consent. The hosted packet API and downloadable templates are versioned separately from the v0.1.7 wheel.

Three concrete jobs: funding review, Cosmos Bank NPAs and a $100k BTC exit with native n8n workflows and optional Slack/Telegram delivery. The Cursor task plugin bundles the same three focused skills and public MCP connections. Marketplace acceptance is separate.

Put it into a recurring workflow: the funding and counterparty workflow pack retains source documents, a spreadsheet index and a local integrity manifest. It includes a reviewed Python runner, an opt-in scheduling template and a ten-day integration scorecard. These examples use the existing 0.1.5 package; they do not change its release or evidence semantics.

Try the underlying evidence first: Open three browser research questions for bank NPA disclosures, dollar funding and BTC exit estimates. Each example calls its named public MCP after a click and displays the returned sources, dates and limits. No key or installation is needed. The page also has setup and starter questions for Financial Evidence and eight other hosted MCPs. The browser examples call individual services; they do not verify an Evidence Carrier or evaluate a combined Financial Evidence packet.

Public documentation includes a crawlable integration matrix plus agent-readable llms.txt, pricing, integration metadata, and a dated third-party marketplace ledger. The v0.1.5 semantic contract defines transport-only status, source-reported adapter metadata, and the explicit non-Carrier boundary. Version 0.1.7 is a signed, independently verified release. Its versioned Agent Skill, terminal, Codex, Gemini, editor, and bundle installs use the same release, with published artifacts, container, Registry record, and a separately verified Homebrew formula. The Claude self-hosted marketplace command follows the repository's mutable default branch; review the checked-out commit before enabling it.

Open, read-only Agent Skills for routing financial research to bounded public evidence. The first skill connects four complementary products without turning them into one score:

• Seiche — money markets, repo, reserves, Treasury cash and system funding.
• LiquiLens — covered bank and lender evidence.
• Undertow — market depth, provider concentration and position-sized exit liquidity.
• Palimpsest — revision-safe China economy evidence and information-state history.

For a daily research workflow, Market Brief provides free, source-cited funding, capital-market and liquidity briefs with local change comparisons. This separately versioned browser companion and agent skill uses the existing public evidence sources.

For direct calls to Seiche, LiquiLens and Undertow, the companion free agent starter kit includes Hermes and OpenClaw setup guides. That kit uses a separate trading-research skill; it does not install Financial Evidence or connect Palimpsest. Use the versioned install below for this four-product routing skill.

Install the agent skill

npx skills add https://github.com/beepboop2025/financial-evidence-skills/tree/v0.1.7/financial-evidence \
  --skill financial-evidence

Or copy financial-evidence/ into the Agent Skills directory supported by your agent. The folder follows the open Agent Skills specification.

The skill is also indexed in the public skills.sh directory.

Once installed, ask your agent to research a money-market, capital-market, bank-risk, market-liquidity, China-economy, GIFT City, forex or gold question. The skill's description lets compatible agents activate it when the work matches.

Use from any terminal

No account or API key is required. On macOS or Linux with Homebrew:

brew install beepboop2025/tap/financial-evidence
financial-evidence fetch --topic money-market --topic china-economy

The formula installs financial-evidence, financial-evidence-mcp, and native Bash, Zsh, and Fish completions for 0.1.7. Alternatively, run directly from GitHub without installing:

uvx --from git+https://github.com/beepboop2025/financial-evidence-skills.git@v0.1.7 \
  financial-evidence fetch --topic money-market --topic china-economy

Or install it as a persistent command:

uv tool install git+https://github.com/beepboop2025/financial-evidence-skills.git@v0.1.7
financial-evidence topics
financial-evidence route --topic capital-market --format table
financial-evidence fetch --topic bank-risk --format ndjson
financial-evidence doctor --format csv

Exit code 0 means every requested source was retrieved, 1 means transport was partial, and 2 means every requested source was unavailable. Legacy packet status is preserved and equals transport_status; both mean transport reachability only. Every packet says status_semantics: transport_only, evidence_status: not_evaluated, and carrier_verification: not_performed. That makes the client safe to compose in shell pipelines without mistaking an HTTP success for validated evidence or a verified Evidence Carrier. JSON, NDJSON, and CSV go to standard output; no result is silently replaced with a score.

Outside Homebrew, shell completions are emitted as inert text:

financial-evidence completion zsh > ~/.zfunc/_financial-evidence

Use as MCP infrastructure

The public Streamable HTTP endpoint requires no local install, account, or API key:

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

It exposes the same three read-only topics, route, and fetch tools for clients that support remote MCP. The root .mcp.json is the portable plugin configuration for that public remote:

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

The package also includes a dependency-free stdio server for local or offline-compatible client setups. Its pinned configuration is in integrations/mcp-config.json. Both transports accept the MCP 2025-11-25 initialization flow and the stateless 2026-07-28 discovery flow. Local stdio messages use newline-delimited JSON-RPC; nothing except protocol messages is written to standard output.

The official MCP Registry record publishes both the multi-architecture OCI package and the public Streamable HTTP endpoint. Remote clients do not need uv, Docker, a credential, or a local subprocess.

Install in Gemini CLI or Claude Code

Gemini CLI can install this repository as an extension. Its root gemini-extension.json connects only to the fixed public remote MCP endpoint and allowlists the three read-only tools; the mirrored skills/financial-evidence folder gives Gemini the domain routing instructions as well:

gemini extensions install https://github.com/beepboop2025/financial-evidence-skills \
  --ref v0.1.7

Claude Code can add this repository as a self-hosted marketplace and install the bundled plugin:

claude plugin marketplace add beepboop2025/financial-evidence-skills
claude plugin install financial-evidence@liquidity-lab

This Claude command follows the mutable default branch. Review the checked-out commit before enabling the plugin; the versioned install routes above remain pinned to the verified release.

The Claude plugin loads the same byte-identical Agent Skill plus the root .mcp.json public remote server. These are direct, self-hosted install routes; they do not imply inclusion in a vendor-operated marketplace or endorsement.

Install in Codex; prepare ChatGPT

Codex can add the repository's plugin marketplace and then install the plugin:

codex plugin marketplace add beepboop2025/financial-evidence-skills --ref v0.1.7
codex plugin add financial-evidence@liquidity-lab

The OpenAI plugin package combines the byte-identical Agent Skill with the public remote MCP endpoint. The Codex repository install route is public. A ChatGPT and Codex universal-directory submission is also prepared, but has not been submitted, approved, or published by OpenAI. The remaining review, publisher-identity, and domain-challenge steps belong to the OpenAI account owner. See OPENAI_PLUGIN_SUBMISSION.md for the listing copy and required positive and negative tests.

The root .mcp.json is the portable plugin form for the public remote MCP server. VS Code and Cursor retain separate workspace files for the pinned local stdio server, so plugin installs do not depend on a local Python process while editor workspaces can still use one.

Install in VS Code or Cursor

The repository also includes editor-specific workspace configuration: .vscode/mcp.json uses VS Code's top-level servers object, while .cursor/mcp.json uses Cursor's top-level mcpServers object. Public install links currently launch the verified v0.1.7 stdio server through uvx, matching the repository manifests.

VS Code can install the server through its protocol handler:

vscode:mcp/install?%7B%22name%22%3A%22financial-evidence%22%2C%22type%22%3A%22stdio%22%2C%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22--from%22%2C%22git%2Bhttps%3A%2F%2Fgithub.com%2Fbeepboop2025%2Ffinancial-evidence-skills.git%40v0.1.7%22%2C%22financial-evidence-mcp%22%5D%7D

Or add it to your VS Code user profile from a terminal:

code --add-mcp '{"name":"financial-evidence","type":"stdio","command":"uvx","args":["--from","git+https://github.com/beepboop2025/financial-evidence-skills.git@v0.1.7","financial-evidence-mcp"]}'

Cursor can install the same configuration through its base64-encoded deeplink:

cursor://anysphere.cursor-deeplink/mcp/install?name=financial-evidence&config=eyJ0eXBlIjoic3RkaW8iLCJjb21tYW5kIjoidXZ4IiwiYXJncyI6WyItLWZyb20iLCJnaXQraHR0cHM6Ly9naXRodWIuY29tL2JlZXBib29wMjAyNS9maW5hbmNpYWwtZXZpZGVuY2Utc2tpbGxzLmdpdEB2MC4xLjciLCJmaW5hbmNpYWwtZXZpZGVuY2UtbWNwIl19

Install uv first so uvx is on your path. Review the source and exact configuration before accepting an editor's install or trust prompt: uvx executes the pinned package locally, and the fetch tool can contact the fixed public HTTPS sources documented by this project. Cursor asks for tool approval by default. VS Code normally asks you to trust a server when it first starts, but starting directly from mcp.json can skip that prompt, so inspect the file before using its inline start action. These are self-installable compatibility artifacts, not claims of a VS Code or Cursor marketplace listing or endorsement.

For desktop clients that support one-click MCP Bundles, download financial-evidence-0.1.7.mcpb from the last verified GitHub release. The bundle uses the cross-platform uv runtime and requires no API key or configuration.

Finance-tool integrations

• Remote MCP: connect any Streamable HTTP client to https://liquilens.in/mcp/financial-evidence; no local runtime, account, or API key is required.
• Gemini CLI: the root extension manifest bundles the Agent Skill and allowlists the three tools exposed by the public remote MCP endpoint.
• Claude Code: the self-hosted liquidity-lab marketplace installs the versioned plugin, Agent Skill, and MCP configuration from this repository.
• Codex: the repository marketplace installs the Agent Skill and public remote MCP package directly.
• ChatGPT: the universal-directory submission packet is prepared; public availability remains pending account-owned verification, submission, review, and publication.
• OpenBB: install .[openbb,workspace] from current repository source in a clean environment and run openbb-build. V4 and V5 compatibility is checked in CI. The released v0.1.7 dependency range remains V4-only. The router exposes datasets(), query(), sources(), routes() and fetch() under obb.financial_evidence. See the setup guide.
• DuckDB: run integrations/duckdb/financial_evidence.sql to create separate HTTP-backed views for all four products.
• Excel / Power Query: paste integrations/excel/FinancialEvidence.pq into Advanced Editor and invoke, for example, FinancialEvidence("money-market"). For flat research rows, use FinancialEvidenceRows from the research kit.
• FDC3: the public Financial Evidence Inspector receives and broadcasts declared standard contexts through window.fdc3. integrations/fdc3/appd-record.json is its FDC3 2.0 web-app record for self-hosted or enterprise directories. The same record is served as raw JSON for direct directory ingestion. The record and runtime do not imply FINOS review, directory acceptance, or vendor endorsement.
• Containers: tagged releases publish a multi-architecture image to ghcr.io/beepboop2025/financial-evidence-skills. The image runs stdio MCP by default; use --entrypoint financial-evidence for terminal commands.
• Official MCP Registry: tagged images are published under io.github.beepboop2025/financial-evidence using GitHub OIDC and the image's ownership annotation. No long-lived registry credential is stored.

Release integrity

Each tagged release rebuilds and retests the Python and JavaScript contracts from the exact signed main commit before publication. The release attaches a wheel, source archive, MCP bundle, CycloneDX SBOM, and SHA256SUMS; GitHub Sigstore build-provenance attestations bind every downloadable artifact to the release workflow. Consumers can verify an artifact with gh attestation verify against beepboop2025/financial-evidence-skills.

Optional bounded retrieval

The bundled helper uses only Python's standard library, accepts a fixed topic allowlist and fetches only fixed public HTTPS endpoints:

python3 financial-evidence/scripts/fetch_evidence.py \
  --topic money-market --topic china-economy

It returns one JSON packet with exact and resolved source URLs, canonical human scope URLs, retrieval clocks, byte counts, content SHA-256 values, separate product documents, and explicit errors. Successful responses also include only the endpoint-specific source state and clocks named by explicit adapters, with RFC 6901 paths and fetched-byte provenance; missing configured fields are not_reported. The router does not infer freshness, eligibility, or rights. Routes declare financial_authority: none and carrier_state: not_published, and therefore expose no carrier_url. Redirects are rejected before following. Returned JSON is untrusted evidence data, not executable instructions. Missing, restricted, or unavailable evidence is never converted to zero or “calm.”

Boundaries

This repository provides public research routing, not investment advice, security recommendations, execution quotes, credit ratings or guarantees. Source publishers retain their rights; an open-source helper does not relicense upstream data.

Support · Privacy · Terms

Development

python3 -m unittest discover -s tests -v
python3 -m py_compile financial-evidence/scripts/fetch_evidence.py src/financial_evidence/*.py

The code and skill instructions are MIT-licensed.

Quant and research agents

Native framework tools and cited quant datasets connect Seiche, LiquiLens and Undertow. Source-pinned agent release 1.0.0 adds compact queries, a three-product review and repeat-call revisions. See the source guide. These are integration recipes, not evidence of external adoption.

AI execution integration

Try the browser order-lifecycle simulator with synthetic prices, timeout recovery, STOP and an exportable journal. It contacts no broker.

The source-pinned integration guide covers the separate customer-operated paper REST/MCP host and a live-broker connector candidate. These are in the Evidence Carrier repository; the public Financial Evidence research router remains read-only. Broker activation requires eligible evidence, account controls and the customer's credentials. The 14-day scorecard measures useful independent use and repeat tasks without treating tests or downloads as customers.

Durable research workflows

The Financial Evidence Runtime adds owner-registered workflows, atomic run limits, offline replay, ordered change events and backup recovery through Python, CLI and private stdio MCP. It reuses the existing product clients and preserves source clocks and missingness. See the architecture and adoption measurements. These commands require the candidate source installation; they are not part of the published 0.1.7 artifact. Local run counts do not establish external users or paid adoption.