What are the risks of connecting to npm:cowork-qa-mcp?

Runs an install/postinstall script — supply-chain surface to review. Overall trust grade C (73/100).

When was npm:cowork-qa-mcp last audited?

Last checked 2026-08-17; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

npm:cowork-qa-mcp

Item: npm:cowork-qa-mcp
Rating: 73
Author: wmcp.sh

https://www.npmjs.com/package/cowork-qa-mcp

73/100 · MCP Trust Grade · checked 27d ago · MCP 0.1.1

Is the npm:cowork-qa-mcp MCP server safe to use?

Independent trust grade C (73/100). Runs an install/postinstall script — supply-chain surface to review. wmcp.sh continuously watches npm:cowork-qa-mcp for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 5 tools · AI & ML

session_start

Open a fresh browser tab and start recording a goal-driven session.

session_act

Perform a browser action in a session: goto | click | fill | press | eval.

session_observe

Return the current URL and aria-snapshot of the session

session_end

Close the session, persist the trace to disk, and return the path.

qa_get_trace

Return the full recorded trace (goal, every step, final URL, final aria-snapshot) so the calling LLM can judge whether the goal was achieved. Call ses

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 5 tool(s) detected in source

Security (OWASP MCP)30%55

install/postinstall script present (supply-chain surface)
scanned 2 source files

Maintenance / popularity20%75

last published ~3mo ago
2 published versions

Tool hygiene15%55

no TypeScript types
3 runtime deps
install script reduces hygiene

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
41 weekly downloads

Findings

WARN Runs an install/postinstall script — supply-chain surface to review.

INFO Static analysis of npm package cowork-qa-mcp@0.1.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:cowork-qa-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:cowork-qa-mcp grade C

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Acowork-qa-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade C](https://wmcp.sh/mcp/grade/npm%3Acowork-qa-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Acowork-qa-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Acowork-qa-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Acowork-qa-mcp/badge.svg" alt="MCP Trust Grade C · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.