LatAm Data
Latin American data for AI agents: tax-ID validation, indicators, FX, company lookups, holidays
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
latam-data-mcpclaude mcp add latam-data -- uvx latam-data-mcp==0.6.1
{
"mcpServers": {
"latam-data": {
"command": "uvx",
"args": [
"latam-data-mcp==0.6.1"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
LatAm Data MCP
An MCP server that gives agents reliable access to LatAm data that is otherwise scattered, undocumented, or Spanish-only: tax-ID validation for 12 countries, live economic indicators, exchange rates (including Argentina's blue rate and Colombia's legally binding TRM), Brazilian company lookups, holidays, and business-day math.
Tools (20)
Identity, banking & companies
| Tool | What it does |
|---|---|
validate_tax_id | Validates national tax IDs with real check-digit math for 15 countries: 🇨🇱 RUT, 🇦🇷 CUIT/CUIL, 🇲🇽 RFC, 🇧🇷 CPF/CNPJ (incl. 2026 alphanumeric CNPJs), 🇨🇴 NIT, 🇵🇪 RUC, 🇺🇾 RUT, 🇪🇨 cédula/RUC, 🇵🇾 RUC, 🇻🇪 RIF, 🇬🇹 NIT, 🇩🇴 RNC, 🇵🇦 RUC+DV, 🇨🇷 cédula, 🇧🇴 NIT. Returns canonical formatting and person/company/public-entity detection. |
validate_bank_account | Validates interbank account codes with check-digit math: 🇲🇽 CLABE (18-digit), 🇦🇷 CBU/CVU (22-digit, incl. Mercado Pago virtual accounts). Decodes bank, branch and account — verify a payout destination before sending money. |
validate_pix_key | Validates a 🇧🇷 PIX key (CPF, CNPJ, e-mail, +55 phone, or random UUID) and detects its type — CPF/CNPJ with full check-digit math. |
validate_phone_number | Validates & normalizes phone numbers for 15 countries → E.164, national format, mobile/landline detection. Handles Brazil's 9th digit, Mexico's 10-digit, Argentina's 9/15, Chile's 9-prefix. |
brazil_bank_lookup | Resolves a 🇧🇷 bank by COMPE code (name, ISPB). |
brazil_company_lookup | Full federal-registry data for any Brazilian company by CNPJ: legal name, status, size, main activity, capital, address, partners. |
costa_rica_company_lookup | 🇨🇷 taxpayer by cédula: name, regime, activities, and compliance status (moroso/omiso) from Hacienda — for KYC/AML. |
Money & markets
| Tool | What it does |
|---|---|
chile_indicators | UF, UTM, USD, EUR and more, in CLP. |
argentina_exchange_rates | Official vs blue rate for USD/EUR. |
brazil_market_rates | SELIC, CDI, IPCA. |
colombia_official_trm | The legally binding USD/COP rate with validity dates. |
brazil_historical_series | Historical SELIC/CDI/IPCA/USD over a date range, with min/max/avg/change — for trend analysis and backtesting. |
colombia_trm_history | Historical USD/COP (TRM) over a date range. |
costa_rica_exchange_rate | 🇨🇷 official USD/EUR colón rate. |
currency_convert | Convert any amount between two currencies at the live rate. |
latam_exchange_rates | All 18 LatAm currencies vs USD in one call. |
Time & calendars
| Tool | What it does |
|---|---|
public_holidays | Official holidays for 20 LatAm countries, any year. |
next_holidays | Upcoming holidays from today. |
long_weekends | Long weekends with bridge-day analysis. |
business_days | Working-day count between dates, holiday-aware — for SLA, payroll, logistics, settlement math. |
Install (free — runs on your machine)
No signup, no API keys. Two steps:
1. Install uv (the runner) if you don't already have it:
brew install uv # macOS
# or, any platform:
curl -LsSf https://astral.sh/uv/install.sh | sh
2. Add the server to your MCP client config (mcpServers block):
{
"mcpServers": {
"latam-data": {
"command": "uvx",
"args": ["latam-data-mcp"]
}
}
}
- Claude Desktop:
~/Library/Application Support/Claude/claude_desktop_config.json(macOS) — then quit and reopen the app. - Cursor / Claude Code / other clients: same
mcpServersblock, in their config.
Then just ask your agent "Is Chilean RUT 60.910.000-1 valid?" — done. Requires Python 3.10+ (uv handles it).
macOS gotcha: if the server doesn't show up, use the full path to uvx as the
command(runwhich uvx→ e.g./opt/homebrew/bin/uvx). GUI apps don't always inherit your shell's PATH. First launch takes a few seconds while uv fetches the package; instant after that.
See it work
Once connected, just ask your agent in plain language:
"Is the Mexican CLABE
646180110400000007valid, and which bank is it?" → ✅ valid · Banco STP · branch 180 · account …
"Validate Brazilian CNPJ
00.000.000/0001-91and tell me who it is." → ✅ Banco do Brasil S.A. · active · Brasília-DF
"What's the UF and the dollar today in Chile? And convert 2,500,000 CLP to BRL."
"How many business days between 2026-09-01 and 2026-09-30 in Chile?" → holiday-aware working-day count (skips Fiestas Patrias)
No glue code — the agent picks the right tool and calls it.
Pro — the compliance & data tier
The tools above are free forever. Pro adds the compliance and data features teams actually pay for — the stuff you can't get from a free public API:
- 🛡️ OFAC sanctions / watchlist screening — fuzzy name matching (catches aliases, reordered names, accents) for KYC/AML onboarding
- 🏢 Company lookup by tax ID — 🇨🇱 Chile today; 🇦🇷 Argentina, 🇵🇪 Peru, 🇲🇽 Mexico coming — name, status, activities, compliance flags
- 📋 Bulk validation — validate up to 10,000 IDs in one call, for onboarding pipelines and CRM cleanups
- coming: PEP screening, change-monitoring webhooks, extended historical data
Delivered as a managed, always-on hosted endpoint (no self-hosting), with higher rate limits and priority support.
💳 $19.99/mo — → Subscribe to Pro
Building for a team, or need a specific country/data source first? Open an issue — tell me your use case and I'll get you early access.
Develop
python3.11 -m venv .venv
.venv/bin/pip install -e ".[dev]"
.venv/bin/python server.py # stdio; set PORT=8000 for Streamable HTTP
Tests
.venv/bin/pytest # offline suite: validators + MCP protocol layer
.venv/bin/pytest -m live # integration tests against the real upstream APIs
Validators are verified against python-stdnum's reference algorithms and real IDs of public institutions (Banco do Brasil, SUNAT, DIAN, UTE, U. de Chile).
Data sources
All free public APIs, no keys: gael.cloud (Chile), Bluelytics (Argentina), BrasilAPI (Brazil), datos.gov.co (Colombia), open.er-api.com (regional FX), Nager.Date (holidays). Tax-ID validation is pure local math — zero dependencies, zero latency, nothing to break.
Roadmap
- [ ] Historical series (UF, USD, TRM)
- [ ] Deploy free tier + directory listings (Smithery, PulseMCP, mcp.so)
- [ ] Monetization via MCPize (85% rev share) once free tier has weekly active users
- [ ] Electronic invoicing requirements per country (static knowledge tool)
Frequently asked questions
What is LatAm Data?
Latin American data for AI agents: tax-ID validation, indicators, FX, company lookups, holidays
How do I install LatAm Data?
It runs on your machine. In Claude Code: claude mcp add latam-data -- uvx latam-data-mcp==0.6.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does LatAm Data need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is LatAm Data open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains LatAm Data?
It is published by svkbogislav. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.