ref-tools-mcp tested by Argusic Runner

Attempt 1 of 3 · Runs with mocks · Argusic Score 92.0 of 100

all runs of ref-tools-mcpcoding-agentdocumentation-toolmcpmcp-server

Session recording

Loading recording...

Download the original recording · fingerprint 2a01329845791458...

What the test found

After npm install, npm run build, and npm run check all succeeded, the app builds to an executable dist/index.cjs; the HTTP server answered 200 'pong' on /ping and a full MCP session (initialize, tools/list, tools/call search/read, prompts) returned 200 with correct results against a mock Ref API, while the stdio transport answered initialize with serverInfo Ref 3.0.3.

No test suite exists in package.json. Third-party Ref API requires a real API key, so a schema-correct mock Ref API at 127.0.0.1:8123 was used via REF_URL; real credentials were never required because the mock was sufficient.

Argusic installed ref-tools-mcp in 12 minutes and launched it; verification reached Verified with mock services. 3 of 3 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of ref-tools-mcp

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.

Error and fix timeline

No errors were recorded for this run.

Discussion