MCP servers
MCP server for CVM fund data (Brazilian funds)
CVM publishes a remarkable amount about Brazilian funds, and publishes it as zipped archives organized by competência, in Portuguese, with encodings that predate most of the tooling people try to read them with. The information is public; the access is not casual.
This MCP server turns those archives into tool calls. An agent asks for a fund's portfolio by CNPJ for a given month and receives positions with weights and asset classes, or asks for daily NAV and flows and receives a clean series. The unzipping, the encoding, the schema drift between years and the reporting lag are handled server-side.
The lag deserves emphasis: portfolios describe a month that closed before the file was published. The tools return both dates, so an agent reasoning about what was knowable does not accidentally treat a disclosure as if it were available in real time.
hindcast — session
previewhindcast> what did this fund hold at the end of the quarter?
→ tool: cvm_fund_portfolio { cnpj:"...", competencia:"..." }
✓ positions with weights, asset classes and the disclosure date
source: CVM CDA archives, normalized server-side
What's covered
- Tool: fund portfolio by CNPJ and competência (CVM CDA)
- Tool: daily NAV, flows and shareholder counts (informe diário)
- Portuguese source fields preserved as aliases beside English names
- Disclosure date returned with every portfolio, not just the period
- CNPJ resolved to the wider entity graph for cross-market questions
- Archive unpacking, encoding and schema drift handled server-side
Join the waitlist — this page's dataset is already selected.
Questions
Do I need to read Portuguese to use this?
No. Fields carry English names with the regulator's original terms kept as aliases, so both vocabularies work and nothing is lost in translation for someone who does read the source.
How far back do fund portfolios go?
As far as CVM's own archives allow, with older schema variations normalized rather than dropped. Where a year genuinely cannot be reconciled to the current schema, it is exposed as-is instead of being quietly excluded.
Related
Join the waitlist. Vote the roadmap. First in, first served.