io.github.javalenciacai/mcp-reportia (io.github.javalenciacai/mcp-reportia@0.3.2) The MCP server io.github.javalenciacai/mcp-reportia reached version 0.3.2, published to the official MCP registry on 2026-09-11 and distributed as @james.valencia/mcp-reportia on npm, according to the mcpindex registry index. The server exposes the Reportia HTTP API as 66 curated MCP tools covering accounting, mappings, and SIIGO, and declares 10 environment variables. mcpindex's semantic screen of the server's description returned a pass with status PARTIAL, finding no malicious instructions, while noting the deterministic conformance probe has not yet run and that its confidence scores are uncalibrated at v1. ← Index /leaderboard io.github.javalenciacai/mcp-reportia Reportia HTTP API as 66 curated MCP tools accounting, mappings, SIIGO . The current version, v0.3.2, was published to the official MCP registry on 2026-09-11. It is distributed as @james.valencia/mcp-reportia on npm, filed under Other by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts /stats put this record in context. Using io.github.javalenciacai/mcp-reportia in Claude, Cursor, Gemini CLI, Cline, or Zed? MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself use Install this server for that . Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less uv tool install mcpindex-gate && mcpindex-config-wire method /methodology Semantic screen found no manipulation pattern in the description. Conformance probe not yet run. mcpindex.integrity.description passINFO evidence“No malicious instructions found in description”via static description - - Semantic screen only - the deterministic conformance probe has not run on this server - - Confidence is reported but not yet calibrated v1 - - Screen reads the tool description, not the live behavior - - advisory - - registry description only no input schema - - screen model 8b - - Still current: the description we screened is unchanged, re-checked against the registry - - The registry listing version, packages, links changed after this screen ran - the description we assessed did not Semantic screen: an LLM judge reads the tool description for hidden instructions status PARTIAL . A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated calibrated=false at v1 . Full verdict history is not shown on this page. Own this server? Screen its description → /screen That verdict was true at screening time snapshot 2026-09-11 . Contracts can change after screening, with no version bump. The gate pins io.github.javalenciacai/mcp-reportia’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday. See your first HOLD in 2 minutes → /guides/install-the-gate-first-hold Related: how to trust an MCP server /guides/how-to-trust-an-mcp-server · screen before install /guides/screen-mcp-server-before-install · silent contract drift /guides/mcp-silent-contract-drift People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land. Independent trust record for io.github.javalenciacai/mcp-reportia https://mcpindex.ai/server/io-github-javalenciacai-mcp-reportia - screening verdict, registry provenance, and contract drift monitoring.