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 Pncp

NPM · @PIPEWORX/MCP-BRAZIL-PNCP · 2 COMPONENTS

Brazil PNCP MCP — Brazilian government procurement (keyless).

+3 this week 81 Trust /100

Last scanned (7 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-pncp). 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 576 tokens (~288/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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 0
    • Security disclosure: unverified → fail ▼ functional
  • 31 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 0.2.0 → 0.2.1 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-pncp@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-pncp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-brazil-pncp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3606580116
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:9d15cc7388022128dd13d6542926bb609d644ee5ea8615b8c4c31a6ff5a1901021ec44a800f2def5b907ad44bb542e1ad8490e8d8d3e5de9e3cdffdba

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 · 2 exposed · ~519 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
brazil_search_contracts ~205

Search signed Brazilian government contracts (contratos) from the official PNCP portal (Portal Nacional de Contratações Públicas). Covers federal, state, and municipal agencies under Lei 14.133/2021. Returns each contract with its PNCP control id, object (Portuguese), global value in BRL, supplier name and tax id (CNPJ/CPF), contracting agency, state/municipality, and signing/validity dates. Dates are YYYYMMDD and filter by PNCP publication date; omit them to get roughly the last 30 days.

NameTypeReqDescription
date_fromstring–Start date (PNCP publication) as YYYYMMDD, e.g. "20260501". Defaults to ~30 days ago.
date_tostring–End date (PNCP publication) as YYYYMMDD, e.g. "20260601". Defaults to today.
pagenumber|string–Page number (1-based). Default 1.

No output schema declared.

No examples provided.

brazil_search_tenders ~314

Search published Brazilian government tenders / bidding notices (contratações / editais) from the official PNCP portal (Portal Nacional de Contratações Públicas). These are open or recently published procurement opportunities under Lei 14.133/2021. Returns each tender with its PNCP control id, object (Portuguese), estimated value in BRL, procurement modality, agency, state/municipality, proposal open/close dates, and a link to the source system. Dates are YYYYMMDD filtering by PNCP publication date; omit for roughly the last 30 days. The modality defaults to 6 (Pregão Eletrônico), the most common; pass another code to filter differently.

NameTypeReqDescription
date_fromstring–Start date (PNCP publication) as YYYYMMDD, e.g. "20260501". Defaults to ~30 days ago.
date_tostring–End date (PNCP publication) as YYYYMMDD, e.g. "20260601". Defaults to today.
modalitynumber|string–Procurement modality code (codigoModalidadeContratacao). REQUIRED by the API; defaults to 6 (Pregão Eletrônico). Others: 4=Concorrência Eletrônica, 8=Dispensa, 9=Inexigibilidade, 12=Credenciamento, 3…
pagenumber|string–Page number (1-based). Default 1.

No output schema declared.

No examples provided.

Install

How do I install the Brazil Pncp MCP server?

Brazil Pncp runs locally as an npm package, launched with npx -y @pipeworx/mcp-brazil-pncp. 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-pncp

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

What is the Brazil Pncp MCP server?

Brazil Pncp is an MCP server listed in the public MCP registry as io.github.pipeworx-io/brazil-pncp. Brazil PNCP MCP, Brazilian government procurement (keyless). This page covers its npm package (@pipeworx/mcp-brazil-pncp).

Is the Brazil Pncp MCP server safe to use?

Brazil Pncp 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 Pncp MCP server expose?

Brazil Pncp exposes 2 tools: brazil_search_contracts, brazil_search_tenders. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.

Is the Brazil Pncp MCP server still maintained?

Brazil Pncp 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 Pncp MCP server under?

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