mx.veriko/veriko
Veriko
Is the Veriko MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Verifica transferencias SPEI contra el CEP de Banxico y opera la API pública de Veriko.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","message":"Envía tu clave de API o un token de acceso OAuth como Authorization: Bearer- Endpoint
- https://api.veriko.mx/mcp (streamable-http)
- Host
- api.veriko.mx
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.veriko.mx/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server api.veriko.mx, PKCE S256, grants client_credentials, authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes account.notifications.read account.notifications.update account.profile.read account.profile.update beneficiaries.records.create beneficiaries.records.delete beneficiaries.records.read beneficiaries.records.update billing.subscriptions.read billing.usage.read docs.portal.read finance.ceps.export finance.reports.create insights.reports.read validations.cep.read validations.ocr.create validations.records.create validations.records.delete validations.records.read validations.retries.manage.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/veriko-mx-labs/veriko-mcp
- Website
- https://docs.veriko.mx/es/mcp
- Registry
- active, updated 2026-11-15 · registry entry
Compare this server with others.
More servers
Servers that mention veriko or transferencias or verifica.
- Veriko io.github.veriko-mx-labs/veriko · error
- ai.atlasverified/atlas-mcp · needs auth
- DeployIt Product Expert ai.deployit/product-expert · alive
- ai.facesign/facesign-mcp · alive
- Human4AI Human Task Network ai.human4ai/collaboration · alive
- Licensy ai.licensy/mcp-server · needs auth
- RobinLawyer.ai ai.robinlawyer/robinlawyer · needs auth
- ScamVerify Threat Verification ai.scamverify/mcp · no DNS
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.