firecrawl-mcp-server tested by Argusic Runner

What the test found

The Firecrawl MCP server builds with pnpm (84/84 tests pass via `npm test` on Node 22), and its HTTP-stream server answered 200 on /health and /ready, listed the full tool set on /v2/mcp, exposed exactly the 7 documented tools on /v2/mcp-search with auth enforcement (401 without credentials), and returned the mock API's search result JSON through a `tools/call firecrawl_search` on both surfaces.

Installed with `npx pnpm@10 install --frozen-lockfile` (prepares build via tsup). Real Firecrawl cloud credentials were not used: I stood up a local fake Firecrawl API (mocked /v2/search, /api/oauth/introspect) on 127.0.0.1:3900 and pointed FIRECRAWL_API_URL at it with a dummy API key. The repo's own test suite runs the same in-process mock pattern. Final state is a clean pnpm install plus `node dist/index.js` binary that builds and starts. No repo files were modified; the only environment change is the user-space Node 22 binary and pnpm cache under /home/runner.

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

Runs with mocksall runs of firecrawl-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.