Veriko
NPM · @VERIKO-MX/MCP · SCANNED OCT 3
Valida y consulta transferencias SPEI mediante la API oficial de Veriko.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to veriko-mx-labs/veriko-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 536 tokens (~107/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the Veriko MCP server?
Veriko runs locally as an npm package, launched with npx -y @veriko-mx/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @veriko-mx/mcp
claude mcp add veriko-mx-labs-veriko -- npx -y @veriko-mx/mcp
{
"mcpServers": {
"veriko-mx-labs-veriko": {
"command": "npx",
"args": [
"-y",
"@veriko-mx/mcp"
]
}
}
} {
"servers": {
"veriko-mx-labs-veriko": {
"command": "npx",
"args": [
"-y",
"@veriko-mx/mcp"
]
}
}
} codex mcp add veriko-mx-labs-veriko -- npx -y @veriko-mx/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"veriko-mx-labs-veriko": {
"type": "local",
"command": [
"npx",
"-y",
"@veriko-mx/mcp"
],
"enabled": true
}
}
} openclaw mcp add veriko-mx-labs-veriko --command npx --arg -y --arg @veriko-mx/mcp
mcp_servers:
veriko-mx-labs-veriko:
command: "npx"
args: ["-y", "@veriko-mx/mcp"] {
"McpServers": {
"veriko-mx-labs-veriko": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@veriko-mx/mcp"
]
}
}
} assistant mcp add veriko-mx-labs-veriko -t stdio -c npx -a -y @veriko-mx/mcp
{
"mcpServers": {
"veriko-mx-labs-veriko": {
"command": "npx",
"args": [
"-y",
"@veriko-mx/mcp"
]
}
}
} 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.
- 3 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.27 → fail ▼ security
- Schema quality: 96 → 107 ▼ functional
- Package version: 0.1.7 → 0.1.9 functional
- Package version: 0.1.7 → 0.1.8 functional
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 0
- Package version: 0.1.6 → 0.1.7 functional
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- Package version: 0.1.5 → 0.1.6 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.10 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.4 → 0.1.5 functional
- 26 Sept 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 0.1.3 → 0.1.4 functional
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 3 Oct 2026 · Analysed npm/@veriko-mx/mcp@0.1.9
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | veriko-mx-labs/veriko-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/veriko-mx-labs/veriko-mcp/.github/workflows/publish.yml@refs/tags/v0.1.9 |
| Rekor log index | 3051919208 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9b2c5907a9347bfed29841bbf87a6a6878d0142957e77b7bb0e1523956e031446f85568684025bd3e2ebd0fb361fc35ab1d826b7a4b9112010550c007 |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
veriko_download_cep Descargar el CEP ~43
Obtiene el comprobante oficial de Banxico en XML o PDF como recurso MCP.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| validationId | string | yes | – |
No output schema declared.
No examples provided.
veriko_get_validation Consultar una validación ~40
Obtiene una validación y su ETag por identificador.
| Name | Type | Req | Description |
|---|---|---|---|
| ifNoneMatch | string | – | – |
| validationId | string | yes | – |
No output schema declared.
No examples provided.
veriko_list_validations Listar validaciones ~131
Lista validaciones con filtros y paginación.
| Name | Type | Req | Description |
|---|---|---|---|
| amountMax | number | – | – |
| amountMin | number | – | – |
| bank | string | – | – |
| batchId | integer | – | – |
| clientRef | string | – | – |
| from | string | – | – |
| page | integer | – | – |
| perPage | integer | – | – |
| playground | boolean | – | – |
| retryState | string | – | – |
| search | string | – | – |
| status | – | – | – |
| to | string | – | – |
| type | string | – | – |
| withDeleted | boolean | – | – |
No output schema declared.
No examples provided.
veriko_validate_direct Validar una transferencia SPEI ~147
Valida datos de una transferencia contra el CEP de Banxico. Cada validación consume cuota del plan del usuario y se descuenta al aceptar la petición.
| Name | Type | Req | Description |
|---|---|---|---|
| async | boolean | – | – |
| claveRastreo | string | – | – |
| clientRef | string | – | – |
| cuentaBeneficiaria | string | – | – |
| cuentasCandidatas | array | – | – |
| emisor | string | – | – |
| fecha | string | yes | – |
| idempotencyKey | string | – | – |
| monto | – | yes | – |
| receptor | string | – | – |
| receptorParticipante | – | – | – |
| referenciaNumerica | string | – | – |
| retryPolicy | object | – | – |
No output schema declared.
No examples provided.
veriko_validate_ocr Validar un comprobante por OCR ~124
Extrae y valida una transferencia desde una imagen, un PDF o una URL HTTPS. Cada validación consume cuota del plan del usuario y se descuenta al aceptar la petición.
| Name | Type | Req | Description |
|---|---|---|---|
| async | boolean | – | – |
| clientRef | string | – | – |
| cuentaBeneficiaria | string | – | – |
| cuentasCandidatas | array | – | – |
| idempotencyKey | string | – | – |
| imageBase64 | string | – | – |
| imageUrl | string | – | – |
| retainImage | boolean | – | – |
| retryPolicy | object | – | – |
No output schema declared.
No examples provided.
What is the Veriko MCP server?
Veriko is an MCP server listed in the public MCP registry as io.github.veriko-mx-labs/veriko. Valida y consulta transferencias SPEI mediante la API oficial de Veriko. This page covers its npm package (@veriko-mx/mcp).
Is the Veriko MCP server safe to use?
Veriko scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 3 October 2026. It declares no install or post-install scripts. 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 Veriko MCP server expose?
Veriko exposes 5 tools: veriko_validate_direct, veriko_validate_ocr, veriko_list_validations, veriko_get_validation, veriko_download_cep. Their descriptions and schemas cost roughly 485 tokens of context every time the server is loaded.
Is the Veriko MCP server still maintained?
Veriko is still listed as active in the MCP registry. We last reached this channel on 3 October 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 Veriko MCP server under?
Veriko declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.