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.

LatAm Data

PYPI · LATAM-DATA-MCP

Latin American data for AI agents: tax-ID validation, indicators, FX, company lookups, holidays

Available components

0 this week 76 Trust /100

Last scanned (2 hours ago)

Scores higher than 72% of PyPI 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 Security44
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to svkbogislav/latam-data-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 113 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2051 tokens (~102/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 30 Oct 26 +14
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 24 Oct 26 +1
    • Stability: 0.97 → pass security
  • 23 Oct 26 −1
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.97 functional
  • 22 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
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 pypi/latam-data-mcp@0.6.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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo svkbogislav/latam-data-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/svkbogislav/latam-data-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 2168119516
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:0fd6696a2ae266dda6ed45e3a9247984529964253c93709b70e90c2fc59da8a1

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_hook unreviewed legacy backend root module

Background: Why install scripts are a supply-chain risk →

Dependencies 22 packages
Packages resolved 22
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~1,955 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
argentina_exchange_rates ~51

Get current Argentine peso (ARS) exchange rates: official vs "blue". The gap between the official and informal (blue) rate is essential context for any pricing, invoicing or purchasing decision in Argentina.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

brazil_bank_lookup ~76

Look up a Brazilian bank by its COMPE code (e.g. 1 = Banco do Brasil, 341 = Itaú). Returns the COMPE code, ISPB, short and full name. Useful to resolve the institution behind a payment or a bank slip. Source: BrasilAPI.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

brazil_company_lookup ~84

Look up a Brazilian company by CNPJ in the federal registry. Returns legal name, trade name, registration status, size, main activity (CNAE), share capital, address, contact data, and partners (QSA). Data from Receita Federal via BrasilAPI. Accepts formatted or unformatted numeric CNPJs.

NameTypeReqDescription
cnpjstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

brazil_historical_series ~130

Get a historical time series of a Brazilian indicator over a date range. `series` is one of: SELIC (policy rate), CDI, IPCA (inflation), USD (PTAX BRL per USD). Dates are ISO (YYYY-MM-DD). Returns every data point plus a summary (min, max, average, first, last, change) — for trend analysis, indexation, and FX backtesting. Source: Banco Central do Brasil (SGS).

NameTypeReqDescription
end_datestringyes–
seriesstringyes–
start_datestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

brazil_market_rates ~41

Get Brazil's key market rates: SELIC (policy rate), CDI, and IPCA (inflation). Annual percentage values, as published via BrasilAPI.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

business_days ~111

Count business days between two dates in a Latin American country. Excludes weekends and that country's nationwide public holidays. Dates are ISO format (YYYY-MM-DD); the range is inclusive on both ends. Returns the count plus the nationwide holidays that fell on a weekday inside the range (i.e. those that actually reduced the count) — useful for SLA, payroll, logistics and settlement-date math.

NameTypeReqDescription
countrystringyes–
end_datestringyes–
start_datestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

chile_indicators ~81

Get current Chilean economic indicators and currency values in CLP. Includes UF (Unidad de Fomento), UTM (Unidad Tributaria Mensual), USD (observed dollar), EUR and other market-quoted currencies. Optionally filter with `codes`, e.g. ["UF", "USD"]. Values are CLP per unit.

NameTypeReqDescription
codes–––

Structured output declared, but exposes no named fields.

No examples provided.

colombia_official_trm ~60

Get Colombia's official TRM (Tasa Representativa del Mercado), USD to COP. The TRM is the legally binding exchange rate certified by the financial regulator — used for taxes, customs, and contracts. Includes validity dates.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

colombia_trm_history ~80

Get Colombia's official TRM (USD/COP) history over a date range. Dates are ISO (YYYY-MM-DD). Returns each daily TRM plus a summary (min, max, average, change). Source: datos.gov.co (Superfinanciera).

NameTypeReqDescription
end_datestringyes–
start_datestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

costa_rica_company_lookup ~120

Look up a Costa Rican taxpayer/company by cédula in the Hacienda registry. Accepts a cédula física (9 digits), jurídica (10 digits) or DIMEX. Returns legal name, tax regime, registered economic activities, and the tax-compliance situation — `delinquent` (moroso), `non_filer` (omiso) and registration `state` — which is valuable for KYC/AML and onboarding. Source: Ministerio de Hacienda (official, no key).

NameTypeReqDescription
cedulastringyes–

Structured output declared, but exposes no named fields.

No examples provided.

costa_rica_exchange_rate ~52

Get Costa Rica's official USD and EUR exchange rates (colón, CRC). Buy/sell for USD and the EUR reference, as certified by Hacienda — used for invoicing and accounting in Costa Rica.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

currency_convert ~114

Convert an amount between any two currencies at the current rate. Handy for pricing, invoicing and reporting across LatAm — e.g. convert a Brazilian price to Chilean pesos. Uses live USD-based rates (open.er-api.com); covers all LatAm currencies plus USD/EUR and most world currencies. Currency codes are ISO 4217 (e.g. CLP, BRL, USD).

NameTypeReqDescription
amountnumberyes–
from_currencystringyes–
to_currencystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

latam_exchange_rates ~99

Get current USD exchange rates for all Latin American currencies at once. Covers ARS, BOB, BRL, CLP, COP, CRC, CUP, DOP, GTQ, HNL, MXN, NIO, PAB, PEN, PYG, UYU, VES. Optionally filter with `currencies`. Rates are units of local currency per 1 USD, updated daily.

NameTypeReqDescription
currencies–––

Structured output declared, but exposes no named fields.

No examples provided.

long_weekends ~63

Get long weekends for a Latin American country and year. Returns each long weekend with start/end dates, day count, and any bridge day needed — useful for travel, staffing, and demand planning.

NameTypeReqDescription
countrystringyes–
yearintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

next_holidays ~29

Get the upcoming public holidays for a Latin American country from today.

NameTypeReqDescription
countrystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

public_holidays ~99

Get official public holidays for a Latin American country and year. `country` is an ISO 3166-1 alpha-2 code (CL, AR, MX, BR, CO, PE, UY, ...). Returns each holiday with date, local name, English name, and whether it is nationwide. Useful for scheduling, SLAs, logistics, and payroll.

NameTypeReqDescription
countrystringyes–
yearintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_bank_account ~128

Validate a Latin American bank account / interbank code, check digit included. Supported (ISO 3166-1 alpha-2): MX (CLABE, 18 digits), AR (CBU/CVU, 22 digits — CVU covers virtual accounts like Mercado Pago). Returns validity, canonical formatting, and the decoded structure — bank code and name, branch, and account number. Essential for fintech, payouts, and payment-collection agents that must confirm an account is well-formed before initiating a transfer.

NameTypeReqDescription
accountstringyes–
countrystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_phone_number ~168

Validate and normalize a Latin American phone number. `country` is an ISO 3166-1 alpha-2 code (15 supported: CL, AR, MX, BR, CO, PE, UY, EC, PY, VE, GT, DO, PA, CR, BO). Accepts input with or without country code, spaces, dashes or parentheses. Returns validity, E.164 form, a human-readable national format, and line type (mobile/landline) — handling the tricky cases (Brazil's 9th digit, Mexico's 10-digit, Argentina's mobile 9/15, Chile's 9-prefix). Ideal for WhatsApp, SMS/OTP and CRM hygiene.

NameTypeReqDescription
countrystringyes–
numberstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_pix_key ~102

Validate a Brazilian PIX key and detect its type. PIX is Brazil's instant-payment rail. A key is one of: CPF (11 digits), CNPJ (14 digits), e-mail, phone (E.164, +55…), or a random EVP (UUID v4). CPF/CNPJ keys are validated with full check-digit math. Lets a payments agent confirm a PIX key is well-formed before initiating a transfer.

NameTypeReqDescription
keystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_tax_id ~267

Validate a Latin American national tax ID, including its check digit. Supported countries (ISO 3166-1 alpha-2): CL (RUT), AR (CUIT/CUIL), MX (RFC), BR (CPF or CNPJ — auto-detected, including 2026 alphanumeric CNPJs), CO (NIT), PE (RUC), UY (RUT), EC (cédula or RUC — auto-detected), PY (RUC), VE (RIF), GT (NIT), DO (RNC), PA (RUC + DV), CR (cédula física/jurídica/DIMEX — format only), BO (NIT — format only). Verifies the country's check digit where one is algorithmically verifiable. Exception: Mexico's RFC — SAT-issued RFCs deviate from the published check-character algorithm, so for MX only the format and the embedded birth/incorporation date are validated (the result carries "check_digit_verified": false to make this explicit). Returns validity, canonical formatting, and — where the ID encodes it — whether it belongs to a person, company, or public entity.

NameTypeReqDescription
countrystringyes–
tax_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the LatAm Data MCP server?

LatAm Data runs locally as a PyPI package, launched with uvx latam-data-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · latam-data-mcp

# add to Claude Code
claude mcp add svkbogislav-latam-data-mcp -- uvx latam-data-mcp
Common questions

What is the LatAm Data MCP server?

LatAm Data is an MCP server listed in the public MCP registry as io.github.svkbogislav/latam-data-mcp. Latin American data for AI agents: tax-ID validation, indicators, FX, company lookups, holidays. This page covers its PyPI package (latam-data-mcp).

Is the LatAm Data MCP server safe to use?

LatAm Data scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Data MCP server expose?

LatAm Data exposes 20 tools: validate_tax_id, validate_bank_account, chile_indicators, argentina_exchange_rates, brazil_market_rates, and 15 more. Their descriptions and schemas cost roughly 1,955 tokens of context every time the server is loaded.

Is the LatAm Data MCP server still maintained?

LatAm Data 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 Data MCP server under?

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