coldpass

Chronary/chronary-mcp

GitHub ↗ · How this check works

Per-setup public labels: Linux / Haiku: Didn’t work

Static status badge · SVG · read-only JSON. Embed with ![Coldpass status](https://coldpass.dev/badge/Chronary--chronary-mcp.svg).

Didn’t work

Only older checks are saved; no current product test.

Answers apply to each recorded setup, revision and operation. Earlier observations remain in Run details.

Tested on Linux
PlatformHaikuLuna
Linuxno

Linux / Haiku 5.5: no · Oct 18, 2026 · 00b86e6e810e · claude-code / 2.1.300 (Claude Code)
Recorded operation: /usr/bin/npx -y @chronary/mcp · local stdio MCP start + initialize + tools/list

MCP
yes, local
Yes, runs locally
Issue
yes, not fixed yet
Our test was blocked; no repo verdict.

Safety: no observations were recorded for the selected revision. Functional results do not establish a safety result.

Repair history and test corrections
Current diagnosis: unknown · resolved

npx for published packages runs from outside the checkout, not the unbuilt same-named package

Repair record fix-7da829582286fa58751e · current status JSON. Original run outcomes remain unchanged.

Failed run: Chronary/chronary-mcp · Oct 18, 2026 · Recorded operation failed.

Repair development: Chronary/chronary-mcp · Oct 18, 2026 · Repair work (development) · not an initial-trial result.

Run details

Haiku 5.5

Native agent · Recorded operation failed

Operation / attempted scope /usr/bin/npx -y @chronary/mcp · local stdio MCP start + initialize + tools/list

Agent-reported scope: Start the published @chronary/mcp stdio MCP server via npx and call tools/list (initialize handshake, then tools/list returned 54 tools).

Run details
run
Chronary--chronary-mcp-claude-haiku-5-5-1792340885790568326
date
Oct 18, 2026
time to working
not recorded
product hosting / execution
Local stdio MCP server in the guest
recorded operation scope
Verified only the MCP server start and tools/list. No Chronary API calls were made, so no real CHRONARY_API_KEY was needed; a placeholder key was passed. The local source build (npm install / tsc) is NOT working because package.json uses workspace:* deps (@chronary/sdk, @chronary/toolkit) that are not in this repo. Tool count (54) differs from the README (50).
model
claude-haiku-5-5
agent / version
claude-code / 2.1.300 (Claude Code)
platform
linux
reported cost
$0.006779
Recorded source
https://github.com/Chronary/chronary-mcp
Tool transport
mcp-assigned-vm
Test version
readme-03aea4c41d53955e3723c330e9927d2a9df627f6642624cc0078a97c73a53c8a
revision
00b86e6e810e3807c558bd107ed375996c9c6cca
Current diagnosis: unknown · resolved

npx for published packages runs from outside the checkout, not the unbuilt same-named package

Repair record fix-7da829582286fa58751e · current status JSON. Original run outcomes remain unchanged.

Failed run: Chronary/chronary-mcp · Oct 18, 2026 · Recorded operation failed.

Repair development: Chronary/chronary-mcp · Oct 18, 2026 · Repair work (development) · not an initial-trial result.

Fix: fix-7da829582286fa58751e.

Recorded blocker / warning

Step: /usr/bin/npx -y @chronary/mcp

MCP response missing for request 1: argv did not answer as a stdio MCP server (a client CLI that talks to servers is kind cli); stderr: sh: 1: chronary-mcp: not found

Suggested next step (agent-reported): To build from source, publish @chronary/sdk and @chronary/toolkit to npm or provide them in the checkout (the release workflow rewrites workspace:* to published versions before install). Not required for the README's npx path.

What the agent did

Start the published @chronary/mcp stdio MCP server via npx and call tools/list (initialize handshake, then tools/list returned 54 tools).

cd <host-path> && ls -la && cat README.md 2>/dev/null | head -200
ls -la <host-path> 2>/dev/null; ls -la <host-path> 2>/dev/null; echo "CDP=$CDP_URL $<env-var>"; node -v; npm -v; python3 --version
cd <host-path> && sed -n 200,400p README.md; cat package.json; ls src test
(sudo -n apt-get update -qq && sudo -n DEBIAN_FRONTEND=noninteractive apt-get install -y -qq nodejs npm) >/tmp/apt.log 2>&1; echo rc=$?; tail -5 /tmp/apt.log; node -v; npm -v
cd <host-path> && cat .chronary-release.json; echo; cat RELEASE_NOTES.txt; echo; ls .github/workflows && cat .github/workflows/*.yml | head -80; ls src; head -40 src/index.ts
cd /tmp && export NODE_USE_ENV_PROXY=1 && CHRONARY_API_KEY=test timeout 180 npx -y @chronary/mcp --help; echo rc=$?
cd <host-path> && export NODE_USE_ENV_PROXY=1 && timeout 240 npm install --no-audit --no-fund 2>&1 | tail -15; echo rc=${PIPESTATUS[0]}
which npx; mkdir -p /tmp/mcpcheck && cat > /tmp/mcpcheck/list.py <<'EOF'
import json, subprocess, sys
p = subprocess.Popen(["/usr/bin/npx","-y","@chronary/mcp"], stdin=subprocess.PIPE, stdout=subprocess.PIPE, stderr=subprocess.PIPE, text=True, env={"PATH":"/usr/bin:/bin","HOME":"<host-path>","NODE_USE_ENV_PROXY":"1","CHRONARY_API_KEY":"chr_sk_placeholder"})
def send(m): p.stdin.write(json.dumps(m)+"\n"); p.stdin.flush()
def recv():
    while True:
        line = p.stdout.readline()
        if not line: raise SystemExit("EOF: "+p.stderr.read())
        if line.startswith("{"): return json.loads(line)
send({"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}})
print("init:", recv()["result"]["serverInfo"])
send({"jsonrpc":"2.0","method":"notifications/initialized"})
send({"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}})
r = recv()["result"]["tools"]
print("tools:", len(r)); print([t["name"] for t in r][:10])
p.terminate()
EOF
cd /tmp/mcpcheck && timeout 240 python3 -I list.py; echo rc=$?
cd <host-path> && mkdir -p .coldpass && cat > .coldpass/probe.json <<'EOF'
{"kind":"mcp","argv":["/usr/bin/npx","-y","@chronary/mcp"],"cwd":"<host-path>","env":{"CHRONARY_API_KEY":"chr_sk_placeholder","NODE_USE_ENV_PROXY":"1"}}
EOF
cat > .coldpass/report.json <<'EOF'
{"outcome":"working","operation":"Start the published @chronary/mcp stdio MCP server via npx and call tools/list (initialize handshake, then tools/list returned 54 tools).","operation_scope":"Verified only the MCP server start and tools/list. No Chronary API calls were made, so no real CHRONARY_API_KEY was needed; a placeholder key was passed. The local source build (npm install / tsc) is NOT working because package.json uses workspace:* deps (@chronary/sdk, @chronary/toolkit) that are not in this repo. Tool count (54) differs from the README (50).","steps":["apt-get install -y nodejs npm (Node v18.19.1, npm 9.2.0)","CHRONARY_API_KEY=test npx -y @chronary/mcp --help (README Troubleshooting: 'Verify the binary runs locally') - exit 0","MCP stdio initialize + tools/list via npx -y @chronary/mcp - serverInfo chronary-mcp 1.5.3, 54 tools"],"deviations":["README 'Prerequisites' Node >=18 satisfied; npm reports EBADENGINE warnings for @hono/node-server (requires node >=20) - warning only.","Repo build: 'npm install' in <host-path> failed with EUNSUPPORTEDPROTOCOL 'Unsupported URL Type \"workspace:\"' for @chronary/sdk and @chronary/toolkit. Source not edited; fell back to the published npm package per README client configuration.","Tool count observed: 54 vs README's 50."],"stuck_step":null,"main_blocker":null,"suggested_fix":"To build from source, publish @chronary/sdk and @chronary/toolkit to npm or provide them in the checkout (the release workflow rewrites workspace:* to published versions before install). Not required for the README's npx path."}
EOF
python3 -I -c "import json;json.load(open('.coldpass/probe.json'));json.load(open('.coldpass/report.json'));print('json ok')"; ls -la; <env-var>=<host-path> python3 -I <host-path> --validate; echo rc=$?
pgrep -af "chronary-mcp|@chronary/mcp" || echo "none running"; rm -rf /tmp/mcpcheck

No product verdict. Run record.