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 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
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 →
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 →
Related: how to trust an MCP server · screen before install · 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.
<a href="https://mcpindex.ai/server/io-github-javalenciacai-mcp-reportia">Independent trust record for io.github.javalenciacai/mcp-reportia</a> - screening verdict, registry provenance, and contract drift monitoring.
A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-javalenciacai-mcp-reportia)
<a href="https://mcpindex.ai/server/io-github-javalenciacai-mcp-reportia"><img src="https://mcpindex.ai/api/v1/badge/io-github-javalenciacai-mcp-reportia" alt="mcpindex verdict" height="20" /></a>
REPORTIA_BASE_URL
Base URL of the Reportia API (without trailing slash). Example: https://reportia.example.com
REPORTIA_TOKEN
Bearer token for M2M authentication. Mutually exclusive with REPORTIA_COOKIE; either can be paired with REPORTIA_EMAIL+REPORTIA_PASSWORD (session login) for cookie fallback.
REPORTIA_COOKIE
Pre-issued Reportia session cookie (e.g. connect.sid=s%3A...). For upstream callers that already hold the resolved user's session and want the child to authenticate as that user without re-login. Mutually exclusive with REPORTIA_TOKEN. Skips /api/auth/login and /api/auth/logout.
REPORTIA_EMAIL
Email for cookie-session authentication.
REPORTIA_PASSWORD
Password for cookie-session authentication.
REPORTIA_COMPANY_ID
Default companyId used when a tool accepts it as optional.
REPORTIA_TIMEOUT_MS
HTTP request timeout in milliseconds (default 30000).
REPORTIA_DOWNLOAD_DIR
Directory where downloaded Excel/PDF exports are saved (default ./downloads).
REPORTIA_USER_AGENT
Custom User-Agent header (default mcp-reportia/0.1.0).
REPORTIA_MAX_DOWNLOAD_BYTES
Maximum bytes for a single binary download (default 104857600 = 100MB).
AgentRoamai.agentroam/agentroam
Buy travel eSIMs, gift cards and mobile top-ups with crypto — user confirms before any order.
Authoryzeai.authoryze/authoryze
Give your AI agent a spending limit: approval controls and single-use virtual cards.
io.github.javalenciacai/siigo-pyme-mcpio.github.javalenciacai/siigo-pyme-mcp
SIIGO Pyme as MCP tools: the 47 ExcelSIIGO functions, plus company discovery.