io.github.inSideos-designs/cowork-qa
NPM · COWORK-QA-MCP
Goal-driven Playwright browser sessions for LLMs, with full action traces and aria-snapshots.
Available components
Last scanned (18 hours ago)
Scores higher than 51% of npm servers
Category Browser Automation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security74
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 181 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 239 tokens (~47/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.93 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 26 Oct 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/cowork-qa-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | playwright install chromium |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
qa_get_trace ~54
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 session_end first.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
session_act ~76
Perform a browser action in a session: goto | click | fill | press | eval.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| session_id | string | yes | – |
| target | string | – | Selector for click/fill, URL for goto, key for press, JS expression for eval. |
| value | string | – | Value for fill. |
No output schema declared.
No examples provided.
session_end ~31
Close the session, persist the trace to disk, and return the path.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
session_observe ~31
Return the current URL and aria-snapshot of the session's page.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
session_start ~47
Open a fresh browser tab and start recording a goal-driven session.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | Plain-English goal the agent will try to accomplish. |
| url | string | – | Optional starting URL. |
No output schema declared.
No examples provided.
How do I install the io.github.inSideos-designs/cowork-qa MCP server?
io.github.inSideos-designs/cowork-qa runs locally as an npm package, launched with npx -y cowork-qa-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cowork-qa-mcp
claude mcp add insideos-designs-cowork-qa -- npx -y cowork-qa-mcp
What is the io.github.inSideos-designs/cowork-qa MCP server?
io.github.inSideos-designs/cowork-qa is an MCP server listed in the public MCP registry as io.github.inSideos-designs/cowork-qa. Goal-driven Playwright browser sessions for LLMs, with full action traces and aria-snapshots. This page covers its npm package (cowork-qa-mcp).
Is the io.github.inSideos-designs/cowork-qa MCP server safe to use?
io.github.inSideos-designs/cowork-qa scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.inSideos-designs/cowork-qa MCP server expose?
io.github.inSideos-designs/cowork-qa exposes 5 tools: session_start, session_act, session_observe, session_end, qa_get_trace. Their descriptions and schemas cost roughly 239 tokens of context every time the server is loaded.
Is the io.github.inSideos-designs/cowork-qa MCP server still maintained?
io.github.inSideos-designs/cowork-qa is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.inSideos-designs/cowork-qa MCP server under?
io.github.inSideos-designs/cowork-qa declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.