What it does
filinglens is a local bridge to a hosted Finbolt MCP server. It holds no data of its own: it serves the upstream tool list locally and forwards each tool call upstream, returning the result unchanged. The 21 tools it serves are read-only. Its core is company financials from SEC filings, where each figure comes with its accession number, form, filing date and XBRL tag, and full income statement, balance sheet and cash-flow statements are returned newest period first. The rest covers quotes, daily, weekly and monthly time series, exchange rates, news sentiment, company overviews and EPS estimates against actuals, plus SMA, EMA, MACD, RSI and Bollinger Band indicators.
It suits lookups where the source of a number matters: retrieving one reported fact with its citation, pulling a statement for a company, comparing two to six stocks in a single table, or requesting a one-call brief that cites each filing. A figure the filings never report comes back as missing rather than estimated. The tools can be reached through a CLI, an MCP client configuration, or a Docker container that runs an stdio MCP server.
The bridge needs network access to the upstream endpoint, which defaults to the Finbolt URL and can be overridden through an environment variable. An optional API key, if set, is sent as a Bearer authorization header on every upstream request. The first call opens a streamable HTTP session that is reused for the life of the process. Upstream errors are returned as error results whose text begins with "filinglens error:", and the CLI exits with 0 on success, 1 on an error result and 2 on a usage error. The test suite runs against a stubbed upstream and makes no live network calls.
Limitations and requirements
Upstream descriptions mark the data "Personal research only". The bridge omits the two meta-dispatch tools, find_tool and run_tool, so it serves 21 of the 23 captured tools and not the roughly 113 data tools those reach. It depends on the hosted upstream endpoint being available. Configuration parts are labelled reconstructions in the source, and the original surface was captured without a key.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/filinglens
SEC-filed company financials with citations, plus market data and technical indicators.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it