{
  "checker": {
    "details": {
      "argv": [
        "<host-path>",
        "mcp"
      ],
      "kind": "mcp",
      "scope": "product operation",
      "serverInfo": {
        "name": "arcane-rmcp",
        "version": "0.4.4"
      },
      "tools": [
        "arcane"
      ],
      "working": true
    },
    "status": "PASS"
  },
  "deviations": [
    "Rust/cargo was not preinstalled: installed via rustup to satisfy the README build step.",
    "C toolchain missing: installed build-essential, pkg-config, libssl-dev via apt; README does not list these prerequisites.",
    "`rarcane mcp` exits with 'configuration error: RARCANE_API_URL is not set' and then 'RARCANE_API_KEY is not set' when unset. Set placeholder values in probe env so the stdio server starts; no real Arcane credential was obtained.",
    "Used the built binary path instead of `npx -y @dinglebear/rarcane mcp` (npm postinstall downloads a GitHub Release binary; the pinned source build was used)."
  ],
  "main_blocker": null,
  "operation": "Start the stdio MCP server (`rarcane mcp`) from the release build, complete initialize, and call tools/list; returns the single `arcane` tool.",
  "operation_scope": "Start and tools/list only. No real Arcane instance or API key was available, so the probe uses placeholder RARCANE_API_URL=http://127.0.0.1:9 and RARCANE_API_KEY=placeholder-smoke. No upstream Arcane action (status, container list, etc.) was executed; those need a real Arcane server and key.",
  "outcome": "working",
  "steps": [
    "Installed rustup toolchain 1.97.1 with clippy and rustfmt (README Build From Source; rust-toolchain.toml)",
    "apt-get update; apt-get install build-essential pkg-config libssl-dev (cc was missing)",
    "cargo build --release (README Install > Build from source) produced target/release/rarcane (v0.4.4)",
    "Ran target/release/rarcane mcp with initialize + tools/list over stdio (README MCP Tool Reference / Runtime Surfaces)"
  ],
  "stuck_step": null,
  "suggested_fix": "For a real end-to-end check, provide RARCANE_API_URL and RARCANE_API_KEY for an Arcane server, then run the `status` action via `rarcane call` or MCP tools/call."
}