# Latam Validate (npm · @pipeworx/mcp-latam-validate)

LatAm Validate MCP — validate Latin-American banking and tax identifiers.

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 86/100, [markdown](https://verifymcp.io/servers/pipeworx-io-latam-validate/latam-validate-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-latam-validate/latam-validate-mcp)
- npm · `@pipeworx/mcp-latam-validate`: 85/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-latam-validate/pipeworx-mcp-latam-validate.md), [page](https://verifymcp.io/servers/pipeworx-io-latam-validate/pipeworx-mcp-latam-validate)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-latam-validate`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-latam-validate).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-latam-validate -- npx -y @pipeworx/mcp-latam-validate
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-latam-validate": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-latam-validate"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-latam-validate": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-latam-validate"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-latam-validate -- npx -y @pipeworx/mcp-latam-validate
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-latam-validate": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-latam-validate"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-latam-validate --command npx --arg -y --arg @pipeworx/mcp-latam-validate
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-latam-validate:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-latam-validate"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-latam-validate": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-latam-validate"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-latam-validate -t stdio -c npx -a -y @pipeworx/mcp-latam-validate
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-latam-validate": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-latam-validate"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 85, +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.

### 2026-11-03 (score 84, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 68, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (5)

### `validate_clabe` (~141 tokens)

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.

Input parameters:

- `clabe` (string, required): The 18-digit CLABE, e.g. "002010077777777771". Spaces and dashes are allowed.

### `validate_cnpj` (~173 tokens)

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.

Input parameters:

- `cnpj` (string, required): 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.

### `validate_cpf` (~92 tokens)

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.

Input parameters:

- `cpf` (string, required): The CPF, e.g. "123.456.789-09" or "12345678909".

### `brasil_cep` (~84 tokens)

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.

Input parameters:

- `cep` (string, required): The 8-digit CEP, e.g. "01310-100" or "01310100".

### `brasil_banks` (~141 tokens)

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.

Input parameters:

- `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".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-latam-validate/pipeworx-mcp-latam-validate#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 68
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-latam-validate
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-latam-validate
- Repository: https://github.com/pipeworx-io/mcp-latam-validate
- Website: https://pipeworx.io/packs/latam-validate
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-latam-validate/pipeworx-mcp-latam-validate.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-latam-validate/pipeworx-mcp-latam-validate.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-latam-validate/pipeworx-mcp-latam-validate