Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
MexicoAPI is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
16
downloads a day
local
runs on your machine
119
downloads in 30d
What it does
Official data from Mexico: FIX, UDIS, working days, UMA, ISR, municipalities, CLABE, RFC, CURP and NSS.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user mexicoapi-mcp '--' npx -y mexicoapi-mcp
# 2 — ask your agent for something these tools do
# validar_clabe, banco_por_codigo, dias_inhabiles and 9 more
MexicoAPI costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DAAll 1 server
Dagel4k1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts MexicoAPI as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user mexicoapi-mcp '--' npx -y mexicoapi-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take MEXICOAPI_BASE (Dirección de la API que se consulta; sin ella, la pública. Con http://, solo localhost, 127.0.0.1 o [::1].), MEXICOAPI_SIN_RED (Con true responde todo con los datos del paquete mexicoapi, sin usar la red.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Valida una CLABE interbancaria de 18 dígitos: dígito de control y código de banco contra el catálogo de bancos que trae el paquete. Acepta espacios y guiones entre los dígitos. No usa la red ni confirma que la cuenta exista. Devuelve el banco (activo: false si ya no aparece en el SPEI), la plaza y…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clabe | string | yes | La CLABE, con o sin espacios y guiones. |
Devuelve un banco o participante del SPEI por el código de 3 dígitos con el que empieza la CLABE: nombre corto, razón social, clave SPEI, si sigue activo y su historial de nombres. Sale del catálogo que trae el paquete, sin red.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| codigo | string | yes | Los 3 primeros dígitos de la CLABE. |
Días inhábiles de un año según una autoridad: lft, cnbv o sat. No lista los sábados y domingos por serlo, pero sí un día publicado que cae en fin de semana. Cada día trae su motivo, su tipo (descanso, o vacaciones del SAT, que en los plazos de declaraciones y pagos cuentan como hábiles) y su…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| autoridad | yes | — | |
| anio | integer | yes | Año de 4 cifras. |
Calcula la fecha que resulta de sumar días hábiles a la fecha desde según el calendario de una autoridad (lft, cnbv o sat), contando desde el día hábil siguiente. En un plazo que corre desde una notificación, desde es el día en que surte efectos, no el día en que se hizo. Con sat, tipo_plazo es…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| autoridad | yes | — | |
| desde | yes | Fecha de partida (AAAA-MM-DD), que no se cuenta: en un plazo que corre desde una notificación, el día en que surte efectos. | |
| dias | integer | yes | Días hábiles a sumar, de 1 a 3650. |
| tipo_plazo | string | no | Solo con autoridad sat, y ahí obligatorio. |
| permitir_incompleto | boolean | no | true para calcular fuera de la cobertura del calendario, con advertencia: el resultado puede cambiar cuando se publique lo que falta. |
Estado, municipio y asentamientos (colonias, fraccionamientos, pueblos) de un código postal, del catálogo de Correos de México que el usuario descargó en este equipo con npx mexicoapi sepomex sync. No usa la red. Si el catálogo no está descargado, responde con error y el comando para descargarlo.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cp | string | yes | Código postal de 5 dígitos, con ceros a la izquierda. |
UMA, salario mínimo y tarifas de ISR publicados en el DOF, cada uno con la publicación que lo respalda. tipo uma con anio (la UMA de ese año) o con fecha (la vigente ese día: cada UMA rige del 1 de febrero al 31 de enero siguiente); tipo salario_minimo con anio (zona general y Zona Libre de la…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tipo | string | yes | — |
| anio | integer | no | Año de 4 cifras. |
| fecha | no | Solo con tipo uma: día en que se busca la vigente. | |
| periodo | string | no | Solo con tipo isr. |
Busca municipios y alcaldías por nombre en el catálogo de INEGI que trae el paquete, sin red. No distingue mayúsculas, acentos ni signos: primero los de nombre igual al texto, luego los que empiezan con él y al final los que lo contienen. Devuelve de cada uno su clave geoestadística (cvegeo), la…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| texto | string | yes | Nombre o parte del nombre del municipio. |
| cve_ent | string | no | Clave INEGI del estado (2 dígitos) para buscar solo en él. |
| limite | integer | no | Máximo de resultados, de 1 a 50. |
Las 32 entidades federativas del catálogo de INEGI que trae el paquete, sin red: clave de 2 dígitos (cve_ent), nombre, abreviatura y cvegeo. Úsala para saber la clave de un estado, que piden municipios_de_estado y buscar_municipio.
No parameter schema on file.
Todos los municipios y alcaldías de un estado, con el total, del catálogo de INEGI que trae el paquete, sin red: de cada uno, su clave geoestadística (cvegeo) y su nombre; municipio da el registro completo. Úsala para preguntas como qué municipios tiene un estado o cuántos son: buscar_municipio…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cve_ent | string | no | Clave INEGI del estado (2 dígitos). |
| estado | string | no | Nombre o abreviatura del estado, como los da estados. |
Devuelve un municipio o alcaldía por su clave geoestadística de INEGI (cvegeo: los 2 dígitos del estado y los 3 del municipio), con el nombre de su estado. Sale del catálogo que trae el paquete, sin red.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cvegeo | string | yes | Clave geoestadística de 5 dígitos. |
Tipo de cambio FIX (pesos por dólar) publicado en el DOF. Con publicado, el valor que se publicó ese día; con operacion, el que aplica a una operación de ese día según el CFF, artículo 20 (el publicado el día anterior o, si ese día no hubo publicación, el último antes); sin ninguno de los dos, la…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| publicado | no | Fecha de publicación en el DOF (AAAA-MM-DD), día de America/Mexico_City. | |
| operacion | no | Fecha de la operación (AAAA-MM-DD), día de America/Mexico_City. |
Valor de la UDI (pesos por unidad de inversión) de un día, como se publica en el DOF. Hay un valor para cada día del calendario, fines de semana incluidos. … Sin red advierte en fechas a … días o menos del último valor del paquete.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fecha | yes | Día del valor (AAAA-MM-DD). |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MexicoAPI or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 0.2.0 · scanned 28 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digestb04adcfe78c0e0352ab8c9978b116029fd00de3ea07c5be1761de7a5f7916526
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestb04adcfe78c0e035
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.0. Pin a release below and the command asks for exactly that one.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish MexicoAPI can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.