Other · Local MCP server

Veriko

Valida y consulta transferencias SPEI mediante la API oficial de Veriko.

Visit Veriko's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.veriko-mx-labs/veriko
Version
0.1.9
Status
Active
Category
other
Transport
stdio (local process)
Package
npm
Published
2026-10-02
Updated
2026-10-02
Publisher
veriko-mx-labs (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/veriko-mx-labs) · how
Website
docs.veriko.mx
Repository
github.com/veriko-mx-labs/veriko-mcp
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npm@veriko-mx/mcp0.1.9stdioVERIKO_API_KEY (secret), VERIKO_MCP_PROFILE, VERIKO_MCP_MAX_RISK

How to connect Veriko

Veriko runs locally from a Node.js package published to the npm registry: @veriko-mx/mcp version 0.1.9. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @veriko-mx/mcp@0.1.9. It reads these environment variables: VERIKO_API_KEY (secret), VERIKO_MCP_PROFILE and VERIKO_MCP_MAX_RISK; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "veriko": {
      "command": "npx",
      "args": [
        "-y",
        "@veriko-mx/mcp@0.1.9"
      ],
      "env": {
        "VERIKO_API_KEY": "<secret>",
        "VERIKO_MCP_PROFILE": "<value>",
        "VERIKO_MCP_MAX_RISK": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
VerifyAPI - fact-check with signed receiptsFact-check any claim with live web sources. Ed25519-signed receipts. Catches hallucinations.Local · stdionpm: @verify-api/mcp
VerifyAXEvaluate, benchmark, and simulate AI agents on the VerifyAX agent-evaluation platform.Remote & Local · HTTP, stdioLive check: sign-in requiredmcp.verifyax.com
verifyfirstLook up what your verification method cannot see: 48 failures that report success.Local · stdioPyPI: verifyfirst-mcp
VerifyMCPIndependent trust scores, tool surfaces and change history for MCP servers.Remote · HTTPLive check: ✓ handshakemcp.verifymcp.io
VeritapCheck whether a real-world fact can be verified before an agent acts on it. Free, no auth.Remote & Local · HTTP, stdioLive check: ✓ handshakeveritap.dev
Veritasacta VerifyOffline receipt verifier. Ed25519 signature verification without contacting any server.Local · stdionpm: @veritasacta/verify
VerityReal-time fact-checking MCP. Verifies claims against live sources with structured verdicts.Local · stdionpm: verity-mcp
VerityCited product-compliance ground truth for AI agents. Never generates; always cites.Remote · HTTPLive check: ✓ handshakeverity-mcp-243195959173.us-central1.run.app