Skills/npm/qwksearch-mcp-server

qwksearch-mcp-server@1.0.316

VERIFIED· startup only

Publisher claims: "MCP server exposing web search and content extraction tools via stdio transport" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher opensourceagi · publishing for 112 daysInstalls 10,084Last detonated 16 h ago
$claude mcp add qwksearch-mcp-server -- npx -y qwksearch-mcp-server
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
SCRAPER_API_KEYConfiguration, not credentials: SCRAPER_URL
Where it talks to
no vendor host named in the codeAlso workers.dev — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names workers.dev as well as its own vendor. The guard injects SCRAPER_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y qwksearch-mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 1.0.315

vet-skills diff qwksearch-mcp-server 1.0.315 1.0.316

In the sandbox, this version reached for nothing 1.0.315 did not. Compared from the two recorded runs, not from source.

1.0.315 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-19 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 73 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
52sprocessdependency install exit 0
72sclaimedstartup only: exited (0) before answering · code: 'ERR_MODULE_NOT_FOUND', url: 'file:///tmp/ks-detonate-NhK4yX/task/home/work/acme-api/.claude/skills/qwksearch-mcp-server/src/index.js' } Node.js v22.23.5
72sprocessscript backend runs setup only
72sprocessno install scripts to re-run

Static findings

No findings across 740 lines in 15 files.

Cost to the agent

Instructions loaded
≈61 tok
1 file · 15 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for qwksearch-mcp-server@1.0.316 as of 16 h ago. This is the package itself, not its dependencies.