{
  "checker": {
    "details": {
      "argv": [
        "/usr/bin/npx",
        "-y",
        "@chronary/mcp"
      ],
      "kind": "mcp",
      "scope": "product operation",
      "serverInfo": {
        "name": "chronary-mcp",
        "version": "1.5.3"
      },
      "tools": [
        "list_calendars",
        "get_calendar",
        "create_calendar",
        "update_calendar",
        "delete_calendar",
        "create_booking_page",
        "list_booking_pages",
        "get_booking_page",
        "delete_booking_page",
        "list_events",
        "get_event",
        "create_event",
        "update_event",
        "cancel_event",
        "confirm_event",
        "release_event",
        "create_agent",
        "list_agents",
        "get_agent",
        "update_agent",
        "delete_agent",
        "get_availability",
        "find_meeting_time",
        "create_connection_link",
        "get_connection_link",
        "cancel_connection_link",
        "get_calendar_context",
        "create_proposal",
        "list_proposals",
        "get_proposal",
        "respond_to_proposal",
        "resolve_proposal",
        "cancel_proposal",
        "set_availability_rules",
        "get_availability_rules",
        "clear_availability_rules",
        "list_webhooks",
        "get_webhook",
        "create_webhook",
        "update_webhook",
        "delete_webhook",
        "list_webhook_deliveries",
        "list_ical_subscriptions",
        "get_ical_subscription",
        "subscribe_ical",
        "update_ical_subscription",
        "delete_ical_subscription",
        "sync_ical_subscription",
        "create_scoped_key",
        "list_scoped_keys",
        "revoke_scoped_key",
        "get_audit_log",
        "accept_terms",
        "get_usage"
      ],
      "working": true
    },
    "status": "PASS"
  },
  "deviations": [
    "`npm install` in <host-path> failed with `npm ERR! code EUNSUPPORTEDPROTOCOL: Unsupported URL Type \"workspace:\": workspace:*`. Expected: the repo's workspace deps only resolve inside the monorepo (the release workflow rewrites them to published versions before install). Not built from source; the README's published-package path was used instead.",
    "Earlier failure `sh: 1: chronary-mcp: not found` (exit 127) reproduced when `npx -y @chronary/mcp` runs with cwd=<host-path> Cause: the workspace package.json is itself named @chronary/mcp and has a bin `chronary-mcp`, so npx resolves the local project, whose node_modules were never installed, instead of fetching the package. The same command succeeds from /tmp and <host-path> `--package=@chronary/mcp chronary-mcp` also fails from the workspace cwd.",
    "Probe cwd set to <host-path> (no package.json) instead of <host-path>, so npx fetches the published package. The argv itself is unchanged.",
    "tools/list returned 54 tools; the README says 50. Documentation count mismatch only, not a blocker.",
    "Node 18 used (guest default via apt); package engines and the Dockerfile target Node 20+. npm printed EBADENGINE warnings for transitive deps but the server ran."
  ],
  "fault_owner": "test",
  "main_blocker": null,
  "operation": "Start the published @chronary/mcp stdio MCP server via the README command `npx -y @chronary/mcp`, perform the MCP initialize handshake, and call tools/list (returned 54 tools, e.g. list_calendars, get_calendar, create_calendar).",
  "operation_scope": "Verified MCP start and tools/list only. Did not call any Chronary API endpoint (no real chr_sk_ key; placeholder key is enough for tools/list). Repo source was not built: package.json uses pnpm `workspace:*` deps that npm cannot install (EUNSUPPORTEDPROTOCOL), and the Dockerfile/smithery.yaml both run the published package. Full unit/lint suites were not run per task instructions.",
  "outcome": "working",
  "steps": [
    "Read README.md and package.json; found the README's documented runtime command `npx -y @chronary/mcp` and verify command `CHRONARY_API_KEY=test npx -y @chronary/mcp --help`.",
    "Installed Node.js 18.19.1 and npm 9.2.0 via `sudo apt-get install nodejs npm` (node was not present in the guest).",
    "Ran `npm view @chronary/sdk`, `@chronary/toolkit`, `@chronary/mcp` (all resolve on the registry).",
    "Ran README verify command `CHRONARY_API_KEY=test npx -y @chronary/mcp --help` from /tmp: exit 0, printed help (only an EBADENGINE warning for Node 18).",
    "Ran a stdio MCP driver (outside the source tree) against `/usr/bin/npx -y @chronary/mcp`: initialize returned serverInfo chronary-mcp 1.5.3; tools/list returned 54 tools.",
    "Wrote <host-path> (kind mcp) and report.json; ran the checker --validate: valid."
  ],
  "stuck_step": null,
  "suggested_fix": null,
  "test_correction": "Run the probe with cwd outside the source tree (e.g. <host-path> or /tmp). Running `npx -y @chronary/mcp` in <host-path> resolves the repo's own package.json (name @chronary/mcp, bin chronary-mcp) and returns 127 because its dependencies are not installed. Also, the probe cwd should not be the source tree for README npx commands. Repo source was left unchanged; no patch was needed."
}