Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.rje1974/arca-agro

NPM · ARCA-AGRO-MCP · SCANNED SEP 25

Cartas de porte, padron y comprobantes de ARCA (Argentina). Solo lectura.

Available components

+4 this week 76 Trust /100
Trust breakdown (7 categories)

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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 668 tokens (~95/item across 7 items; 7 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 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the io.github.rje1974/arca-agro MCP server?

io.github.rje1974/arca-agro runs locally as an npm package, launched with npx -y arca-agro-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 · arca-agro-mcp

# add to Claude Code
claude mcp add rje1974-arca-agro -- npx -y arca-agro-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "rje1974-arca-agro": {
      "command": "npx",
      "args": [
        "-y",
        "arca-agro-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "rje1974-arca-agro": {
      "command": "npx",
      "args": [
        "-y",
        "arca-agro-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add rje1974-arca-agro -- npx -y arca-agro-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rje1974-arca-agro": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "arca-agro-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add rje1974-arca-agro --command npx --arg -y --arg arca-agro-mcp
# ~/.hermes/config.yaml
mcp_servers:
  rje1974-arca-agro:
    command: "npx"
    args: ["-y", "arca-agro-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "rje1974-arca-agro": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "arca-agro-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add rje1974-arca-agro -t stdio -c npx -a -y arca-agro-mcp
// mcp.json
{
  "mcpServers": {
    "rje1974-arca-agro": {
      "command": "npx",
      "args": [
        "-y",
        "arca-agro-mcp"
      ]
    }
  }
}
Changelog

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 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 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.

  • 21 Sept 26 +36
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.20 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Package version: 1.2.0 → 1.2.1 functional
  • 20 Sept 26 −35
    • Stability: 0.13 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.2.0 → 1.2.1 functional
  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +16
    • Malware scan: unverified → pass ▲ security
  • 16 Sept 26 0
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ 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.03 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.1.0 → 1.2.0 functional
  • 15 Sept 26 56

    First indexed and scored.

Diagnostics

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/arca-agro-mcp@1.2.1

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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~668 tokens

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 →

Tool Tokens
consultar_comprobante ~91

Detalle de un comprobante ya emitido: importes, IVA, CAE y estado. Solo consulta: no autoriza comprobantes ni pide CAE.

NameTypeReqDescription
numerointegeryesNúmero de comprobante
puntoVentaintegeryesPunto de venta
tipoComprobanteintegeryesTipo de comprobante (1 = Factura A, 6 = Factura B, ...)

No output schema declared.

No examples provided.

consultar_cpe ~94

Datos completos de una carta de porte electrónica a partir de su CTG: grano, pesos, estado, fechas y los CUIT que intervienen. Incluye los pesos tomados en la balanza del destino, que son los que sirven para conciliar contra balanza propia.

NameTypeReqDescription
nroCTGstringyesNúmero de CTG (Código de Trazabilidad de Granos) de la carta de porte

No output schema declared.

No examples provided.

consultar_padron ~98

Razón social, estado de la clave fiscal, domicilio fiscal, forma jurídica y actividad principal de un CUIT. Sirve para saber contra quién se está operando. El régimen impositivo (monotributo vs. general) solo aparece si el certificado tiene habilitado el alcance A5 del padrón, que se pide aparte en ARCA.

NameTypeReqDescription
cuitstringyesCUIT a consultar, con o sin guiones

No output schema declared.

No examples provided.

cpes_recibidas_en_planta ~186

Cartas de porte que LLEGARON a una planta propia dentro de un rango de fechas. Es la consulta del que recibe la mercadería, no del que la despacha: ARCA exige el número de planta y no ofrece el listado inverso. Quien solo despacha no puede usar esto. Por defecto devuelve un resumen (totales por grano y las 20 más recientes); pedir detalle solo para rangos cortos, porque una campaña entera son cientos de cartas.

NameTypeReqDescription
desdestringyesFecha de partida desde, YYYY-MM-DD
detalleboolean–Si es true, lista todas las cartas en vez del resumen.
hastastringyesFecha de partida hasta, YYYY-MM-DD
plantaintegeryesNúmero de planta de destino. Obligatorio: ARCA rechaza la consulta sin él.

No output schema declared.

No examples provided.

estado_servicios ~57

Chequea si los servidores de ARCA están respondiendo. No usa el certificado ni consulta datos de nadie: es lo primero que conviene mirar cuando algo falla, para separar una caída del organismo de un problema de credenciales.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tipos_de_grano ~58

Códigos de grano que reconoce ARCA hoy, consultados en vivo. Útil para traducir el código que trae una carta de porte, y para descartar códigos de planillas viejas que el organismo ya no reconoce.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ultimo_nro_orden ~84

Último número de orden de carta de porte emitido para una sucursal y tipo de CPE. Sirve para detectar saltos de numeración.

NameTypeReqDescription
sucursalinteger–Número de sucursal. Default: 0.
tipoCPEinteger–Tipo de CPE. Default: 74 (carta de porte automotor).

No output schema declared.

No examples provided.

Common questions

What is the io.github.rje1974/arca-agro MCP server?

io.github.rje1974/arca-agro is an MCP server listed in the public MCP registry as io.github.rje1974/arca-agro. Cartas de porte, padron y comprobantes de ARCA (Argentina). Solo lectura. This page covers its npm package (arca-agro-mcp).

Is the io.github.rje1974/arca-agro MCP server safe to use?

io.github.rje1974/arca-agro 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/arca-agro MCP server expose?

io.github.rje1974/arca-agro exposes 7 tools: consultar_cpe, cpes_recibidas_en_planta, tipos_de_grano, ultimo_nro_orden, consultar_padron, and 2 more. Their descriptions and schemas cost roughly 668 tokens of context every time the server is loaded.

Is the io.github.rje1974/arca-agro MCP server still maintained?

io.github.rje1974/arca-agro 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/arca-agro MCP server under?

io.github.rje1974/arca-agro declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.