Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Brazil Cvm Financials

NPM · @PIPEWORX/MCP-BRAZIL-CVM-FINANCIALS · 2 COMPONENTS

brazil-cvm-financials -- annual financial statements (DFP) of Brazilian listed companies, from CVM…

+3 this week 81 Trust /100

Last scanned (3 hours ago)

Scores higher than 69% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-brazil-cvm-financials). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 924 tokens (~308/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 78

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-brazil-cvm-financials@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-brazil-cvm-financials
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-brazil-cvm-financials/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3606579453
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:4d29f299879f3a8ed77272b5dd26101ab19565b4e3eaa97257974622e7dbab818e6b3cbc58b8a2de6c090659bb08d7c541eb6387b3e06804cdce91289

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~863 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
br_financial_series ~296

One CVM account across fiscal years for a Brazilian listed company -- e.g. account_code "3.01" for the income-statement top line, "1" for total assets, "2.03" for equity -- in full BRL with the account label, scope and filing version of each year. Pass cnpj or name. Account codes follow the CVM chart (1 assets, 2 liabilities and equity, 3 income statement, 6 cash flow, 7 value added); labels and meaning differ between banks/insurers and industrials, and the label is returned per year so a change is visible. Years the company did not file the account are listed in missing_years rather than dropped. A code the company never reported returns found:false with data_as_of.

NameTypeReqDescription
account_codestringyesCVM account code, e.g. "3.01", "1", "2.03", "6.01".
cnpjstring–Company CNPJ, formatted or 14 digits. Pass cnpj or name.
from_yearnumber–First fiscal year (default: the earliest this company filed).
namestring–Company name instead of cnpj.
scopestring–Default: consolidated where filed, else individual (each row says which).
to_yearnumber–Last fiscal year (default: the latest this company filed).

No output schema declared.

No examples provided.

br_financials ~438

Annual financial statements (DFP) of a Brazilian listed company from CVM open data: balance sheet, income statement, cash flow and value added, as account lines with CVM account codes and Portuguese labels, in full BRL. Identify the company by cnpj (e.g. "00.000.000/0001-91" or 14 digits) or by name (e.g. "Petrobras"; an ambiguous name returns candidates instead of a guess). year is the fiscal reference year (default: latest loaded). scope is "consolidated" or "individual" (default: consolidated when the company filed one, else individual -- the response says which). Only the latest filing version is kept; the response states it. statement narrows to one of BPA (assets), BPP (liabilities and equity), DRE (income), DFC_MI / DFC_MD (cash flow indirect / direct), DVA (value added). max_depth (default 2) limits account-code depth so a default call returns the headline lines; raise it for sub-accounts. Results page with limit/offset and report truncated/total_matching. A company or year not in the data returns found:false with data_as_of, never an empty success.

NameTypeReqDescription
cnpjstring–Company CNPJ, formatted or 14 digits. Pass cnpj or name.
limitnumber–Lines per page, 1-500 (default 100).
max_depthnumber–Account-code depth, 1-6 (default 2: e.g. "3.01" but not "3.01.01").
namestring–Company name, e.g. "Petrobras", "Itau Unibanco". Accents optional.
offsetnumber–Lines to skip (default 0).
scopestring–Default consolidated if filed, else individual.
statementstring–One statement only. Default: all.
yearnumber–Fiscal reference year, e.g. 2024. Default: latest loaded for that company.

No output schema declared.

No examples provided.

br_financials_search ~129

Search Brazilian listed companies in the CVM annual-statements data by name (every word must appear; accents ignored), returning cnpj, name, CVM code and the fiscal years available. Use it to find the cnpj to pass to br_financials or br_financial_series. A query matching nothing returns found:false with data_as_of, never an empty list.

NameTypeReqDescription
limitnumber–Max companies, 1-100 (default 25).
namestringyesCompany name or part of it, e.g. "vale", "banco do brasil".

No output schema declared.

No examples provided.

Install

How do I install the Brazil Cvm Financials MCP server?

Brazil Cvm Financials runs locally as an npm package, launched with npx -y @pipeworx/mcp-brazil-cvm-financials. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-brazil-cvm-financials

# add to Claude Code
claude mcp add pipeworx-io-brazil-cvm-financials -- npx -y @pipeworx/mcp-brazil-cvm-financials
Common questions

What is the Brazil Cvm Financials MCP server?

Brazil Cvm Financials is an MCP server listed in the public MCP registry as io.github.pipeworx-io/brazil-cvm-financials. brazil-cvm-financials -- annual financial statements (DFP) of Brazilian listed companies, from CVM… This page covers its npm package (@pipeworx/mcp-brazil-cvm-financials).

Is the Brazil Cvm Financials MCP server safe to use?

Brazil Cvm Financials scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Brazil Cvm Financials MCP server expose?

Brazil Cvm Financials exposes 3 tools: br_financials, br_financials_search, br_financial_series. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.

Is the Brazil Cvm Financials MCP server still maintained?

Brazil Cvm Financials is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Brazil Cvm Financials MCP server under?

Brazil Cvm Financials declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.