CRA AGENT (io.github.giupy997/cra-agent@0.0.9) MCP registry index mcpindex.ai published a screening record for CRA AGENT (io.github.giupy997/cra-agent@0.0.9), an MCP server that lets an agent pay for x402 APIs in USDC on Arc under a spending policy it cannot change. The server, distributed as @cra-agent/mcp on npm and published to the official MCP registry on 2026-09-23, declares 5 environment variables including CRA_NETWORK (arc mainnet or arcTestnet) and CRA_KEY_FILE, and received a semantic-screen pass with status PARTIAL and advisory posture; the deterministic conformance probe has not been run. mcpindex.ai noted the registry listing changed after the screen ran and that its gate pins each tool contract and holds calls when contracts drift without a version bump. ← Index https://mcpindex.ai/leaderboard CRA AGENT Lets an agent pay for x402 APIs in USDC on Arc, under a spending policy it cannot change. The current version, v0.0.9, was published to the official MCP registry on 2026-09-23. It is distributed as @cra-agent/mcp on npm, filed under Other by this index, and declares 5 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 https://mcpindex.ai/stats put this record in context. Using CRA AGENT 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 https://mcpindex.ai/methodology Semantic screen found no manipulation pattern in the description. Conformance probe not yet run. mcpindex.integrity.description passINFO evidence“No malicious instructions”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 - - 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 → https://mcpindex.ai/screen That verdict was true at screening time snapshot 2026-09-23 . Contracts can change after screening, with no version bump. The gate pins CRA AGENT’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 → https://mcpindex.ai/guides/install-the-gate-first-hold Related: how to trust an MCP server https://mcpindex.ai/guides/how-to-trust-an-mcp-server · screen before install https://mcpindex.ai/guides/screen-mcp-server-before-install · silent contract drift https://mcpindex.ai/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 CRA AGENT https://mcpindex.ai/server/io-github-giupy997-cra-agent - screening verdict, registry provenance, and contract drift monitoring.