Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Veriko

by veriko-mx-labsversion 0.2.0i★ 0iRuns on your computerOfficial site ↗
Registry nameio.github.veriko-mx-labs/veriko

How to install

What it does

Verify Mexican SPEI transfers against the Banxico CEP and operate the Veriko public API.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score12/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Veriko. Follow https://mcp.popnx.com/i/veriko-mx-labs-veriko.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Veriko for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "veriko": { "command": "npx", "args": [ "-y", "@veriko-mx/mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Veriko tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "veriko": {
          "command": "npx",
          "args": [
            "-y",
            "@veriko-mx/mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use Veriko and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Veriko or shows a Veriko tool in the answer, you are connected

8 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • VERIKO_API_KEY Integrator API key (veriko_ followed by 64 hexadecimal characters). Optional for the tools that read public data.
  • VERIKO_MCP_PROFILE Tool profile: core, all or families separated by commas. · default core
  • VERIKO_MCP_MAX_RISK Highest risk advertised: read, write or destructive. · default write
  • VERIKO_BASE_URL API base URL. HTTPS only, except localhost.
  • VERIKO_TIMEOUT_MS Timeout per request in milliseconds, from 1000 to 300000. · default 60000
  • VERIKO_MAX_RETRIES Automatic retries of transient failures, from 0 to 5. · default 2
  • VERIKO_ACCEPT_LANGUAGE Language of the API error text: en or es. · default en
  • VERIKO_MCP_FILE_ROOTS Absolute directories, separated by the platform path delimiter, that image_path and file_path may read from. Without it those arguments are not advertised.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Veriko yet

Veriko runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Veriko

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Veriko for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user veriko -- npx -y @veriko-mx/mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Veriko tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user veriko -- npx -y @veriko-mx/mcp
  4. Type /mcp in Claude Code

    You should see Veriko listed as connected

  5. Try it

    Use Veriko and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Veriko or shows a Veriko tool in the answer, you are connected

8 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • VERIKO_API_KEY Integrator API key (veriko_ followed by 64 hexadecimal characters). Optional for the tools that read public data.
  • VERIKO_MCP_PROFILE Tool profile: core, all or families separated by commas. · default core
  • VERIKO_MCP_MAX_RISK Highest risk advertised: read, write or destructive. · default write
  • VERIKO_BASE_URL API base URL. HTTPS only, except localhost.
  • VERIKO_TIMEOUT_MS Timeout per request in milliseconds, from 1000 to 300000. · default 60000
  • VERIKO_MAX_RETRIES Automatic retries of transient failures, from 0 to 5. · default 2
  • VERIKO_ACCEPT_LANGUAGE Language of the API error text: en or es. · default en
  • VERIKO_MCP_FILE_ROOTS Absolute directories, separated by the platform path delimiter, that image_path and file_path may read from. Without it those arguments are not advertised.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Veriko for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "veriko": { "command": "npx", "args": [ "-y", "@veriko-mx/mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Veriko tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use Veriko and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Veriko or shows a Veriko tool in the answer, you are connected

8 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • VERIKO_API_KEY Integrator API key (veriko_ followed by 64 hexadecimal characters). Optional for the tools that read public data.
  • VERIKO_MCP_PROFILE Tool profile: core, all or families separated by commas. · default core
  • VERIKO_MCP_MAX_RISK Highest risk advertised: read, write or destructive. · default write
  • VERIKO_BASE_URL API base URL. HTTPS only, except localhost.
  • VERIKO_TIMEOUT_MS Timeout per request in milliseconds, from 1000 to 300000. · default 60000
  • VERIKO_MAX_RETRIES Automatic retries of transient failures, from 0 to 5. · default 2
  • VERIKO_ACCEPT_LANGUAGE Language of the API error text: en or es. · default en
  • VERIKO_MCP_FILE_ROOTS Absolute directories, separated by the platform path delimiter, that image_path and file_path may read from. Without it those arguments are not advertised.

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Veriko for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "veriko": { "type": "stdio", "command": "npx", "args": [ "-y", "@veriko-mx/mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Veriko tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use Veriko and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Veriko or shows a Veriko tool in the answer, you are connected

8 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • VERIKO_API_KEY Integrator API key (veriko_ followed by 64 hexadecimal characters). Optional for the tools that read public data.
  • VERIKO_MCP_PROFILE Tool profile: core, all or families separated by commas. · default core
  • VERIKO_MCP_MAX_RISK Highest risk advertised: read, write or destructive. · default write
  • VERIKO_BASE_URL API base URL. HTTPS only, except localhost.
  • VERIKO_TIMEOUT_MS Timeout per request in milliseconds, from 1000 to 300000. · default 60000
  • VERIKO_MAX_RETRIES Automatic retries of transient failures, from 0 to 5. · default 2
  • VERIKO_ACCEPT_LANGUAGE Language of the API error text: en or es. · default en
  • VERIKO_MCP_FILE_ROOTS Absolute directories, separated by the platform path delimiter, that image_path and file_path may read from. Without it those arguments are not advertised.

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Veriko💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user veriko -- npx -y @veriko-mx/mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "veriko": {
      "command": "npx",
      "args": [
        "-y",
        "@veriko-mx/mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "veriko": {
      "command": "npx",
      "args": [
        "-y",
        "@veriko-mx/mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "veriko": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@veriko-mx/mcp"
      ]
    }
  }
}

Values you fill in

  • VERIKO_API_KEY secret env
    Integrator API key (veriko_ followed by 64 hexadecimal characters). Optional for the tools that read public data.
  • VERIKO_MCP_PROFILE env
    Tool profile: core, all or families separated by commas.
  • VERIKO_MCP_MAX_RISK env
    Highest risk advertised: read, write or destructive.
  • VERIKO_BASE_URL env
    API base URL. HTTPS only, except localhost.
  • VERIKO_TIMEOUT_MS env
    Timeout per request in milliseconds, from 1000 to 300000.
  • VERIKO_MAX_RETRIES env
    Automatic retries of transient failures, from 0 to 5.
  • VERIKO_ACCEPT_LANGUAGE env
    Language of the API error text: en or es.
  • VERIKO_MCP_FILE_ROOTS env
    Absolute directories, separated by the platform path delimiter, that image_path and file_path may read from. Without it those arguments are not advertised.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
123/wk
Connection
Runs on your computer
Latest versioni
0.2.0
Categoryi
Other
Published to registryi
Nov 14, 2026
Code last changedi
Nov 18, 2026
Maker
veriko-mx-labs
Packages
npm: @veriko-mx/mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account veriko-mx-labs, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed yesterday

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @veriko-mx/mcp@0.2.0

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/veriko-mx-labs-veriko.svg)](https://mcp.popnx.com/en/servers/veriko-mx-labs-veriko)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20653 servers in this category
  • Published to the registry more recently than 90% of the other 20653 servers in this category
  • Basic checks equal to or better than 99% of the other 20653 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Veriko safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed yesterday, and the latest version (0.2.0) reached the registry 5 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Veriko
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Veriko MCP

El servidor MCP de Veriko conecta Veriko con Cursor u otro cliente compatible con MCP. Le pides al asistente que compruebe un pago en el CEP de Banxico, que te diga en qué quedó una validación anterior o que descargue el comprobante.

El servidor cubre como herramientas 73 de las 75 operaciones públicas de máquina a máquina. Deja fuera las dos operaciones de purga (prepare y execute), porque un borrado definitivo no se puede deshacer. Otras tres herramientas esperan un resultado asíncrono: veriko_wait_for_validation, veriko_wait_for_cep_export y veriko_wait_for_beneficiary_import. Con eso son 76 herramientas en el perfil all.

Instalación

Hay dos formas de conectar el servidor. Con la local, tu cliente arranca el paquete en tu computadora. Con la remota, se conecta al servidor que Veriko mantiene en https://api.veriko.mx/mcp, sin instalar nada.

Local, con npx

Requiere Node.js 20 o posterior. Sin clonar nada, el cliente arranca el servidor con npx:

npx -y @veriko-mx/mcp

En Cursor y en otros editores compatibles con MCP que leen mcpServers en su archivo de configuración de MCP:

{

"mcpServers": { "veriko": { "command": "npx", "args": ["-y", "@veriko-mx/mcp"], "env": { "VERIKO_API_KEY": "veriko_..." } } } }

En VS Code (.vscode/mcp.json), que pide la clave al arrancar en lugar de guardarla en el archivo:

{

"inputs": [ { "type": "promptString", "id": "veriko-api-key", "description": "Clave de API de Veriko", "password": true } ], "servers": { "veriko": { "command": "npx", "args": ["-y", "@veriko-mx/mcp"], "env": { "VERIKO_API_KEY": "${input:veriko-api-key}" } } } }

Remota

El servidor remoto usa Streamable HTTP en https://api.veriko.mx/mcp. En Claude, ChatGPT y otros clientes que conectan con OAuth basta con la URL: el cliente te lleva a Veriko para iniciar sesión y elegir los permisos. En los demás, cada petición lleva tu clave de API en el encabezado Authorization: Bearer. Es el mismo servidor del paquete, con las mismas herramientas, pero no lee archivos de tu computadora: para image_path y file_path usa la instalación local.

En Cursor, con la clave en una variable de entorno:

{

"mcpServers": { "veriko": { "url": "https://api.veriko.mx/mcp", "headers": { "Authorization": "Bearer ${env:VERIKO_API_KEY}" } } } }

En VS Code:

{

"inputs": [ { "type": "promptString", "id": "veriko-api-key", "description": "Clave de API de Veriko", "password": true } ], "servers": { "veriko": { "type": "http", "url": "https://api.veriko.mx/mcp", "headers": { "Authorization": "Bearer ${input:veriko-api-key}" } } } }

Otros editores compatibles con MCP aceptan una URL remota y encabezados personalizados: usa la misma URL y el mismo encabezado Authorization. La clave nunca se escribe en un archivo que subas al repositorio.

Probarlo desde el código fuente

git clone https://github.com/veriko-mx-labs/veriko-mcp.git

cd veriko-mcp npm ci npm run build

Queda un servidor ejecutable en dist/index.js. Para verlo responder sin clave de API, el perfil de planes públicos no necesita credenciales:

VERIKO_MCP_PROFILE=plans VERIKO_MCP_MAX_RISK=read node dist/index.js

El proceso se queda esperando mensajes MCP por stdin; lo normal es que lo arranque tu cliente. Esta es la configuración del host, con la ruta absoluta a la copia que acabas de construir:

{

"mcpServers": { "veriko": { "command": "node", "args": ["/ruta/a/veriko-mcp/dist/index.js"], "env": { "VERIKO_API_KEY": "veriko_...", "VERIKO_MCP_PROFILE": "core", "VERIKO_MCP_MAX_RISK": "write" } } } }

La clave se obtiene en app.veriko.mx. Nunca es un argumento de una herramienta: el servidor sólo la lee de VERIKO_API_KEY, de modo que un texto inyectado en una página que el modelo esté leyendo no puede pedírsela. Las herramientas que leen datos públicos (perfil plans, estado de Banxico, catálogo de bancos) funcionan sin clave.

Variables de entorno

VariableDescripciónPredeterminado
VERIKO_API_KEYClave de API del integrador (veriko_ seguido de 64 caracteres hexadecimales)ninguno
VERIKO_MCP_PROFILEcore, all, una familia o varias familias separadas por comacore
VERIKO_MCP_MAX_RISKRiesgo máximo que se anuncia: read, write o destructivewrite
VERIKO_BASE_URLURL base de la API (HTTPS; HTTP sólo para localhost)API de producción
VERIKO_TIMEOUT_MSTiempo límite por petición, de 1,000 a 300,00060,000
VERIKO_MAX_RETRIESReintentos automáticos de fallas transitorias, de 0 a 52
VERIKO_ACCEPT_LANGUAGEIdioma del texto de los errores de la API: en o esen
VERIKO_MCP_FILE_ROOTSDirectorios absolutos, separados por el delimitador de rutas de la plataforma, de los que pueden leer image_path y file_path (sólo stdio)ninguno

Lo que consume cuota

veriko_validate_direct y veriko_validate_ocr consumen cuota del plan, que se descuenta cuando la API acepta la petición. Cada descripción lo dice, porque un ciclo de un agente puede vaciar una cuota mensual en minutos. El resultado informa el saldo restante, y el texto avisa cuando queda poco. El resto del catálogo consulta, exporta o descarga sin consumir validaciones.

Consulta antes el saldo con veriko_get_usage_limits, que pertenece al perfil core.

Perfiles

VERIKO_MCP_PROFILE acepta core, all, una familia o varias familias separadas por coma.

PerfilHerramientas anunciadas
corevalidar, validar una cuenta, listar, consultar, esperar y descargar un CEP, límites de uso
validationsciclo completo de validaciones
webhooksendpoints, entregas y secretos
catalogbancos, calendario SPEI, BIN y estado de Banxico
beneficiarieslista e importación masiva
usageconsumo, límites y exportación
accountperfil y política de reintentos
dashboardresumen operativo
plansplanes públicos
insightsmétricas agregadas
financeresúmenes, vistas previas, descargas y exportaciones de CEP
billingsuscripción activa
alllas 76 herramientas

El perfil decide qué familias ve el modelo. El riesgo se controla de forma independiente con VERIKO_MCP_MAX_RISK:

  • read: sólo consultas y descargas;
  • write (predeterminado): agrega validaciones y cambios normales;
  • destructive: agrega eliminaciones, cancelaciones, rotación de secretos y la confirmación de importaciones.
Lo que cuesta anunciar cada perfil

Anunciar una herramienta gasta contexto antes de que el modelo llame a ninguna. Estas cifras salen del propio servidor: bytes de la respuesta tools/list, con npm run measure:catalog. Los tokens son una estimación a 3.6 bytes por token, no una tokenización real, y sirven para comparar perfiles entre sí. Las cifras incluyen el esquema de salida de cada herramienta.

PerfilHerramientasBytes de tools/listTokens estimados
core826,952~7,487
validations1545,822~12,728
webhooks1029,850~8,292
catalog56,898~1,916
beneficiaries1627,784~7,718
usage79,055~2,515
account34,957~1,377
dashboard11,253~348
plans22,207~613
insights45,094~1,415
finance1221,221~5,895
billing11,087~302
all76155,218~43,116

Medido con Node 22 y riesgo destructive, para no ocultar herramientas. all cuesta 5.7 veces lo que core; por eso el perfil predeterminado es core y se amplía por familia cuando hace falta. test/tools-list-size.test.ts falla cuando un perfil rebasa su presupuesto.

Comportamiento de las herramientas

  • Nombres y entradas. Las herramientas se llaman veriko_ . El prefijo mantiene únicos los nombres en un host que conecta varios servidores, y los nombres no cambian entre versiones. Los campos de entrada usan los nombres de la API en snake_case, cada uno con su descripción, y los enums, mínimos y máximos del contrato público.
  • Salida estructurada. Cada herramienta declara un outputSchema y devuelve structuredContent más el mismo JSON como texto. Un objeto _call lleva el id de la petición, la marca Idempotent-Replayed, la cuota, la ventana de límite de frecuencia, retry_after_seconds y, cuando la API lo anuncia, deprecation y sunset. El texto se recorta a 64 KiB; structuredContent nunca se recorta.
  • Idempotencia. Cada escritura envía un Idempotency-Key aleatorio por llamada. Para reintentar sin riesgo tras una respuesta perdida, repite la llamada con la misma idempotency_key; idempotent_replayed: true significa que la API devolvió la respuesta guardada.
  • Resultados asíncronos. Una validación puede responder queued o processing. veriko_wait_for_validation, veriko_wait_for_cep_export y veriko_wait_for_beneficiary_import consultan hasta que el recurso llega a un estado terminal o termina la espera (25 segundos por omisión, hasta 40). Respetan next_poll_after_seconds y Retry-After, y responden terminal: false con el intervalo cuando se acaba el tiempo. Las lecturas condicionales que devuelven 304 llegan como { "not_modified": true, "etag": ... }, no como errores.
  • Errores. Una llamada fallida devuelve isError con code, status, retryable, retry_after_seconds, request_id y la lista completa errors (code, title, detail, hint, docs_url, pointer, meta). Un 429 por cuota agotada (kind: quota) y uno por límite de frecuencia (kind: rate_limit) regresan de inmediato, con retry_after_seconds; el servidor no espera dormido a que pasen.
  • Confirmación. Cuando el cliente declara la capacidad elicitation, el servidor pregunta antes de veriko_delete_validation, veriko_delete_webhook, veriko_regenerate_webhook_secret, veriko_delete_beneficiary, veriko_delete_beneficiary_import_row, veriko_commit_beneficiary_import, veriko_update_validation_retry_policy y veriko_update_my_retry_policy. Una pregunta rechazada o cerrada devuelve executed: false con el reason, y no se envía nada a la API. Un cliente sin la capacidad ejecuta la operación, y VERIKO_MCP_MAX_RISK sigue siendo la compuerta.
  • Avance y cancelación. Cuando la petición trae un progressToken, las herramientas de espera envían una notifications/progress por consulta, y las descargas envían una al empezar la petición y otra cuando llega el archivo. Cancelar la petición aborta la llamada en curso, sus reintentos y la pausa entre consultas; el resultado es cancelled.
  • Descargas. Los archivos regresan como recursos incrustados hasta 256 KiB, y como enlaces veriko://artifact/... por encima de eso (stdio), con el tipo MIME correcto. El servidor infiere el tipo de una descarga application/octet-stream por la extensión y los primeros bytes.
  • Límites. El servidor valida base64 canónico y los límites públicos antes de llamar al SDK: 12 MB para comprobantes OCR (imagen o PDF) y 20 MB para importaciones de beneficiarios. El transporte stdio admite completa una importación máxima.
  • Archivos locales. Por stdio, define VERIKO_MCP_FILE_ROOTS y veriko_validate_ocr acepta image_path, y veriko_create_beneficiary_import acepta file_path, en lugar de base64. La ruta debe ser absoluta y, una vez resueltos los enlaces, estar dentro de una de las raíces. El servidor revisa los límites de tamaño anteriores, los pr

Only the beginning is shown; read the rest in the repo