Latam Validate
NPM · @PIPEWORX/MCP-LATAM-VALIDATE · 2 COMPONENTS
LatAm Validate MCP — validate Latin-American banking and tax identifiers.
Available components
Last scanned (10 hours ago)
Scores higher than 87% of npm servers
Category Finance and Payments
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-latam-validate). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 688 tokens (~137/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 81
First indexed and scored.
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-latam-validate@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-latam-validate |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-latam-validate/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649625185 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4a1eefb493102221f115ccc9e3e2a6784f84ca05d7f91ce62c710f16dae861c623e3abfc790693998a3409b6a2652de41e3ccb52454b6e3867e56e34e |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
brasil_banks ~141
List Brazilian banks (COMPE code, ISPB, and name) from the central-bank registry, optionally filtered by name or code. Use to resolve a bank code from a boleto or PIX/TED transfer to the institution name, e.g. code 1 → Banco do Brasil, 260 → Nubank.
| Name | Type | Req | Description |
|---|---|---|---|
| code | number | – | Exact COMPE bank code to look up, e.g. 341 for Itaú. |
| limit | number | – | Max results when listing/filtering (default 25). |
| search | string | – | Filter by bank name substring (case-insensitive), e.g. "nubank" or "itau". |
No output schema declared.
No examples provided.
brasil_cep ~84
Look up a Brazilian CEP (postal code) and return the address: street, neighborhood, city, and state, with coordinates when available. Example: CEP 01310-100 → Avenida Paulista, Bela Vista, São Paulo, SP.
| Name | Type | Req | Description |
|---|---|---|---|
| cep | string | yes | The 8-digit CEP, e.g. "01310-100" or "01310100". |
No output schema declared.
No examples provided.
validate_clabe ~141
Validate a Mexican CLABE (Clave Bancaria Estandarizada, the 18-digit interbank account number used for SPEI transfers). Checks the control-digit checksum and decodes the bank code, plaza (branch city) code, and account number. Resolves the bank name for major Mexican banks (BBVA, Banorte, Santander, Banamex, Banco Azteca, STP, Nu, Mercado Pago, ...). Pure computation — accepts spaces or dashes in the input.
| Name | Type | Req | Description |
|---|---|---|---|
| clabe | string | yes | The 18-digit CLABE, e.g. "002010077777777771". Spaces and dashes are allowed. |
No output schema declared.
No examples provided.
validate_cnpj ~173
Validate a Brazilian CNPJ (Cadastro Nacional da Pessoa Jurídica, the 14-character company tax ID) and look up the company registration: legal name (razão social), trade name, CNAE activity, address, registration status (situação cadastral), and partners (QSA). Checksum supports both the classic numeric format and the alphanumeric CNPJ introduced in 2026. Punctuation (12.345.678/0001-95) is accepted. Set skip_lookup to validate the checksum only.
| Name | Type | Req | Description |
|---|---|---|---|
| cnpj | string | yes | The CNPJ, e.g. "33.000.167/0001-01" or "33000167000101". |
| skip_lookup | boolean | – | If true, only run the checksum and skip the BrasilAPI company-registration lookup. Default false. |
No output schema declared.
No examples provided.
validate_cpf ~92
Validate a Brazilian CPF (Cadastro de Pessoas Físicas, the 11-digit personal tax ID) checksum. Pure computation, no lookup — returns whether the two check digits are correct and the formatted form. Punctuation (123.456.789-09) is accepted.
| Name | Type | Req | Description |
|---|---|---|---|
| cpf | string | yes | The CPF, e.g. "123.456.789-09" or "12345678909". |
No output schema declared.
No examples provided.
How do I install the Latam Validate MCP server?
Latam Validate runs locally as an npm package, launched with npx -y @pipeworx/mcp-latam-validate. 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-latam-validate
claude mcp add pipeworx-io-latam-validate -- npx -y @pipeworx/mcp-latam-validate
What is the Latam Validate MCP server?
Latam Validate is an MCP server listed in the public MCP registry as io.github.pipeworx-io/latam-validate. LatAm Validate MCP, validate Latin-American banking and tax identifiers. This page covers its npm package (@pipeworx/mcp-latam-validate).
Is the Latam Validate MCP server safe to use?
Latam Validate scores 85 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 Latam Validate MCP server expose?
Latam Validate exposes 5 tools: validate_clabe, validate_cnpj, validate_cpf, brasil_cep, brasil_banks. Their descriptions and schemas cost roughly 631 tokens of context every time the server is loaded.
Is the Latam Validate MCP server still maintained?
Latam Validate 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 Latam Validate MCP server under?
Latam Validate declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.