@veriko-mx/mcp

MCPattested
v0.1.9io.github.veriko-mx-labsMITUpdated 3d agonpmGitHub

Servidor MCP oficial de Veriko para validar y consultar transferencias SPEI

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
1kDownloads/wk
3d agoLast update
Reads these credentials
  • VERIKO_API_KEYAPI keyoptional

    Clave de API del integrador de Veriko. Puede omitirse para las herramientas públicas de planes.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.veriko-mx-labs
LicenseMIT
Version0.1.9
Sourcenpm+mcp-registry
npm@veriko-mx/mcp
GitHubveriko-mx-labs/veriko-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · c4a03de
Dependencies✓ 3 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv0.1.3 · 9d agoHow well does this scan work?
EvalsNone
IndexedSep 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source9d ago

Forge read 56 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Servidor MCP oficial de Veriko para validar y consultar transferencias SPEI

Keywords
mcpmodel-context-protocolmcp-serverbanxicocepspeimexicofintechtypescript
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-26 — observed resolution, not a publisher declaration.

3 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

Declared but not resolved

1 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.