MCP Server for Official Mexican Data
Connect your AI assistant (Claude, ChatGPT, or any MCP client) straight to Mexico's official registries: CURP, RFC, postal codes, phone numbers, SPEI receipts, and the Federal Official Gazette (DOF). One connection, pay-per-call via SPEI, no card, no subscription.
A tlmx_ API key is required to use the MCP server. Connecting is free — you only pay for the tool calls your agent makes.
What is MCP?
The Model Context Protocol (MCP) is the open standard that lets an AI assistant use external tools. Tlaloc's MCP server publishes our official-data services as tools your agent can invoke on its own — no per-API integration code on your side.
As far as we know, it is the first MCP server for official Mexican data: purely official registries, direct tool-by-tool access, billed per call — not a platform that happens to ship an MCP wrapper.
How to connect
From Claude Code it is a single command:
claude mcp add --transport http tlaloc https://api.tlaloc.sh/mx/mcp \
--header "Authorization: Bearer tlmx_YOUR_API_KEY"
- Endpoint:
https://api.tlaloc.sh/mx/mcp - Transport: HTTP (StreamableHTTP)
- Auth: your
tlmx_API key (OAuth also supported) - Works with Claude (Desktop and Code), ChatGPT, and any MCP client
Client-by-client walkthrough: How to set up the Tlaloc MCP server in your AI assistant.
Tools by service
Identity & tax
consultar_curp validates a CURP against RENAPO; validar_rfc checks an RFC with SAT (individuals and companies).
Location
consultar_codigo_postal looks up SEPOMEX postal codes; consultar_telefono resolves carrier and line type from the IFT registry.
Payments
descargar_cep, consultar_cep, and listar_instituciones_cep handle Banxico's electronic SPEI payment receipts.
Regulatory
buscar_dof, buscar_entidades_dof, obtener_documento_dof, and more: semantic search over the Federal Official Gazette, 2002 to the present.
Every tool costs the same as its REST endpoint — see pricing. The full tool list lives in the documentation.
Why Tlaloc instead of a KYC platform?
| Tlaloc MCP | KYC platforms with an MCP | |
|---|---|---|
| What it is | Direct, tool-by-tool access to official data | An identity/risk platform; the MCP drives their flow |
| Model | Prepaid, pay-per-call via SPEI, no card, no contract | Subscription/enterprise, KYC account onboarding |
| Coverage | 6 official sources: RENAPO, SAT, SEPOMEX, IFT, Banxico, DOF | Identity/AML only — no geographic data, no Official Gazette |
| Lock-in | None — it's the MCP plus the REST API; you orchestrate | The agent lives inside their platform |
| Transparency | Public repo + the official MCP registry | Closed |
Verifiable trust
- Public repo: github.com/tlaloc-sh/tlaloc-mcp
- Listed in the official MCP registry (registry.modelcontextprotocol.io) and on PulseMCP
- As far as we know, the first MCP server for official Mexican data
Frequently Asked Questions
What is the Tlaloc MCP server?
A remote MCP (Model Context Protocol) server at https://api.tlaloc.sh/mx/mcp that exposes Tlaloc's official Mexican data services — CURP (RENAPO), RFC (SAT), postal codes (SEPOMEX), phone numbers (IFT), SPEI payment receipts (Banxico), and the Federal Official Gazette (DOF) — as tools your AI assistant can call directly.
Which assistants does it work with?
Claude (Desktop and Claude Code), ChatGPT, and any MCP-compatible client. It is a remote HTTP server (StreamableHTTP): nothing to install — add the URL with your API key and the tools appear.
How much does it cost?
Connecting is free. Each tool call is billed at the same price as the equivalent REST endpoint (e.g. postal-code lookup 0.01 u, RFC validation 0.10 u; 1 u = $1 MXN, VAT included). No monthly fee, no connection charge. See pricing.
Do I need a card?
No. Accounts are prepaid via SPEI bank transfer: sign up, top up from your bank, and your calls draw from that balance. No card, no subscription, no contract.
What data can my agent query?
Six official sources: CURP against RENAPO, RFC against SAT, SEPOMEX postal codes, phone numbers from the IFT registry, Banxico SPEI payment receipts (CEP), and semantic search over the Federal Official Gazette (DOF), 2002 to the present.
Is it safe?
Access is scoped to your tlmx_ API key (or OAuth): the agent can only spend your calls and your balance. All data comes from official registries queried legitimately — no scraping, no gray sources — and you can revoke the key from the console at any time.