{
  "checker": {
    "details": {
      "argv": [
        "<host-path>",
        "mcp"
      ],
      "kind": "mcp",
      "scope": "product operation",
      "serverInfo": {
        "name": "unifi-rmcp",
        "version": "0.2.5"
      },
      "tools": [
        "unifi"
      ],
      "working": true
    },
    "status": "PASS"
  },
  "deviations": [
    "README 'Build From Source' (cargo build --release) not run: cargo/rustc not installed in guest; used the Release installer, which fetches the latest published release binary (0.2.5), not a build of the pinned commit 5b0cee24.",
    "npx -y @dinglebear/runifi mcp not used: node/npm not installed in guest.",
    "runifi mcp exits with 'UNIFI_URL is not set' when no config is present; set placeholder UNIFI_URL=https://127.0.0.1:1 and UNIFI_API_KEY=placeholder-not-a-real-key to start it. No real controller credentials were available or obtained."
  ],
  "main_blocker": null,
  "operation": "Start the runifi stdio MCP server (`runifi mcp`) and call MCP tools/list; server returns the single `unifi` tool with its action enum (serverInfo unifi-rmcp 0.2.5).",
  "operation_scope": "Local MCP start and tools/list only. No UniFi controller was available, so no live controller operation (health, clients, devices) was exercised. Placeholder UNIFI_URL/UNIFI_API_KEY were set only to satisfy startup config checks; tools/list does not contact the controller.",
  "outcome": "working",
  "steps": [
    "curl -fsSL https://raw.githubusercontent.com/dinglebear-ai/runifi/main/scripts/install.sh | bash (README Install > Release installer) -> installed runifi 0.2.5 to ~/.local/bin/runifi",
    "runifi --version",
    "runifi mcp, initialize + notifications/initialized + tools/list (README Install > npm / npx stdio MCP server, run via the installed binary)"
  ],
  "stuck_step": null,
  "suggested_fix": "For a live operation (health, clients), supply a real UNIFI_URL and UNIFI_API_KEY for a UniFi controller; to build the pinned commit, install rustup and run cargo build --release."
}