vibe-check-mcp-server tested by Argusic Runner

What the test found

With Node 22.23.3 at /tmp/node22, npm ci and npm run build succeed, all 139 unit tests pass, the MCP server answers 200 on /healthz and handles repeated initialize/tools/list/tools/call requests over HTTP with real LLM responses, and vibe_learn entries persist in ~/.vibe-check/vibe-log.json.

npm ci added 261 packages; npm run build exits 0; npm test exits 0 with 24 files/139 tests passed. Verified live against real OpenRouter API (model openrouter/auto) via both HTTP and STDIO transports. npm run security-check exits 1 reporting 4 high/critical advisories in pinned deps (pre-existing, not changed by me). System node is still v18; I ran everything with /tmp/node22/bin on PATH. STDIO request.json with no id returns no output per documented design (docs/TESTING.md).

Argusic installed vibe-check-mcp-server in 16 minutes and launched it; verification reached Verified running for real. 3 of 3 recorded errors were worked through (see the timeline below).

Runsall runs of vibe-check-mcp-server

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.