io.github.rje1974/interbanking
NPM · INTERBANKING-MCP · SCANNED SEP 25
Saldos y movimientos bancarios de Interbanking (Argentina). Solo lectura.
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 Security98
- 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
- 34 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 369 tokens (~92/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.rje1974/interbanking MCP server?
io.github.rje1974/interbanking runs locally as an npm package, launched with npx -y interbanking-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 · interbanking-mcp
claude mcp add rje1974-interbanking -- npx -y interbanking-mcp
{
"mcpServers": {
"rje1974-interbanking": {
"command": "npx",
"args": [
"-y",
"interbanking-mcp"
]
}
}
} {
"servers": {
"rje1974-interbanking": {
"command": "npx",
"args": [
"-y",
"interbanking-mcp"
]
}
}
} codex mcp add rje1974-interbanking -- npx -y interbanking-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rje1974-interbanking": {
"type": "local",
"command": [
"npx",
"-y",
"interbanking-mcp"
],
"enabled": true
}
}
} openclaw mcp add rje1974-interbanking --command npx --arg -y --arg interbanking-mcp
mcp_servers:
rje1974-interbanking:
command: "npx"
args: ["-y", "interbanking-mcp"] {
"McpServers": {
"rje1974-interbanking": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"interbanking-mcp"
]
}
}
} assistant mcp add rje1974-interbanking -t stdio -c npx -a -y interbanking-mcp
{
"mcpServers": {
"rje1974-interbanking": {
"command": "npx",
"args": [
"-y",
"interbanking-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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 22 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 21 Sept 26 +36
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.30 ▲ functional
- Package version: 1.0.1 → 1.0.2 functional
- 20 Sept 26 −32
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.27 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 1.0.1 → 1.0.2 functional
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 55
First indexed and scored.
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 25 Sept 2026 · Analysed npm/interbanking-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 109 packages
| Packages resolved | 109 |
|---|---|
| Stale | 34 |
| 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 →
listar_cuentas Listar cuentas ~39
Lista las cuentas bancarias disponibles con su banco, tipo, moneda y numero. Util como primer paso para saber que cuentas existen antes de pedir movimientos.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
movimientos Consultar movimientos ~119
Movimientos de todas las cuentas en un rango de fechas. Descubre las cuentas solo. Por defecto devuelve un resumen (totales por cuenta y los 25 mas recientes); pedir detalle solo para rangos cortos, porque un rango largo son miles de registros.
| Name | Type | Req | Description |
|---|---|---|---|
| desde | string | yes | Fecha desde (YYYY-MM-DD) |
| detalle | boolean | – | Si es true, lista todos los movimientos en vez del resumen. |
| hasta | string | yes | Fecha hasta (YYYY-MM-DD) |
| tipo | string | – | Tipo de movimiento. Default: anteriores |
No output schema declared.
No examples provided.
saldos Consultar saldos ~95
Saldos actuales de todas las cuentas: contable, operativo y proyectado. Acepta un rango de fechas opcional de hasta 64 dias; para rangos mas largos usar saldos_historicos.
| Name | Type | Req | Description |
|---|---|---|---|
| desde | string | – | Fecha desde (YYYY-MM-DD), opcional |
| hasta | string | – | Fecha hasta (YYYY-MM-DD), opcional |
| moneda | string | – | Filtrar por moneda |
No output schema declared.
No examples provided.
saldos_historicos Saldos historicos ~116
Saldos diarios en un rango de fechas largo. Parte el rango automaticamente en tramos de 60 dias porque la API no acepta mas de 64 por consulta, y devuelve la serie unificada. Devuelve un resumen por cuenta; usar detalle para la serie dia por dia.
| Name | Type | Req | Description |
|---|---|---|---|
| desde | string | yes | Fecha desde (YYYY-MM-DD) |
| detalle | boolean | – | Si es true, devuelve el saldo de cada dia. Puede ser mucho texto. |
| hasta | string | yes | Fecha hasta (YYYY-MM-DD) |
No output schema declared.
No examples provided.
What is the io.github.rje1974/interbanking MCP server?
io.github.rje1974/interbanking is an MCP server listed in the public MCP registry as io.github.rje1974/interbanking. Saldos y movimientos bancarios de Interbanking (Argentina). Solo lectura. This page covers its npm package (interbanking-mcp).
Is the io.github.rje1974/interbanking MCP server safe to use?
io.github.rje1974/interbanking scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 io.github.rje1974/interbanking MCP server expose?
io.github.rje1974/interbanking exposes 4 tools: listar_cuentas, saldos, saldos_historicos, movimientos. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.
Is the io.github.rje1974/interbanking MCP server still maintained?
io.github.rje1974/interbanking is still listed as active in the MCP registry. We last reached this channel on 25 September 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 io.github.rje1974/interbanking MCP server under?
io.github.rje1974/interbanking declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.