Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mikusnuz/cws

NPM · CWS-MCP

MCP server for Chrome Web Store — extension upload, publish, status, and rollout

Available components

0 this week 79 Trust /100

Last scanned (14 hours ago)

Scores higher than 63% of npm servers

Category CI/CD and DevOps

Trust breakdown (7 categories)

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 Security81
  • 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
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1190 tokens (~132/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 9 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 14 Nov 26 +1
    • Stability: 0.97 → pass security
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −8
    • Provenance: pass → unverified ▼ security
    • Stability: pass → 0.80 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
Diagnostics

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 21 Nov 2026 · Analysed npm/cws-mcp@2.0.2

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 →

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 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,190 tokens

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 →

Tool Tokens
cancel ~71

Cancel a pending submission on Chrome Web Store. Can be used to cancel an item currently in review.

NameTypeReqDescription
itemIdstring–Extension item ID (defaults to CWS_ITEM_ID env var)
publisherIdstring–Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me')

No output schema declared.

No examples provided.

deploy-percentage ~114

Set the published deploy percentage for staged rollout on Chrome Web Store. The new percentage must be higher than the current target. Only available for items with 10,000+ seven-day active users.

NameTypeReqDescription
itemIdstring–Extension item ID (defaults to CWS_ITEM_ID env var)
percentagenumberyesDeploy percentage (0-100). Must be larger than the current target percentage.
publisherIdstring–Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me')

No output schema declared.

No examples provided.

get ~85

Fetch publication status through v2 (alias of status). Version 2 no longer returns listing metadata or supports projection; use get-metadata-ui for draft listing text.

NameTypeReqDescription
itemIdstring–Extension item ID
projectionstring–Removed in 2.0; use get-metadata-ui for current draft listing text
publisherIdstring–Publisher ID

No output schema declared.

No examples provided.

get-metadata-ui ~79

Read the current draft listing description, category, homepage and support URL from the signed-in Developer Dashboard. This is not the published listing.

NameTypeReqDescription
accountIndexinteger–Google account index
headlessboolean–Run browser headless; use false for the first sign-in
itemIdstring–Extension item ID

No output schema declared.

No examples provided.

publish ~177

Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, and skip-review.

NameTypeReqDescription
blockOnWarningsboolean–Reject publishing when validation returns warnings (default: false)
deployPercentageinteger–Initial deploy percentage for staged rollout (0-100). Only used with STAGED_PUBLISH or DEFAULT_PUBLISH.
itemIdstring–Extension item ID (defaults to CWS_ITEM_ID env var)
publishTypestring–DEFAULT_PUBLISH: publishes immediately after approval. STAGED_PUBLISH: stages for manual publishing after approval. Defaults to DEFAULT_PUBLISH.
publisherIdstring–Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me')
skipReviewboolean–Attempt to skip review if the extension qualifies. Defaults to false.

No output schema declared.

No examples provided.

status ~87

Fetch the current status of an extension on Chrome Web Store. Returns published/submitted revision status, deploy percentage, version, takedown/warning flags, and last upload state.

NameTypeReqDescription
itemIdstring–Extension item ID (defaults to CWS_ITEM_ID env var)
publisherIdstring–Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me')

No output schema declared.

No examples provided.

update-metadata ~236

Save draft listing description, category, homepage or support URL via the signed-in Developer Dashboard, then reload to verify. Does not submit for review. Package title/summary, raw payloads, and icon uploads are unsupported.

NameTypeReqDescription
accountIndexinteger–Google account index
categorystring–Exact category label displayed by the dashboard
defaultLocalestring–Unsupported: change manifest default_locale and upload a new ZIP
descriptionstring–Detailed store listing description
headlessboolean–Run browser headless; use false for the first sign-in
homepageUrlstring–Homepage URL; empty string clears it
itemIdstring–Extension item ID
metadataobject–Unsupported: use the explicit dashboard fields
storeIconPathstring–Unsupported: upload the store icon directly in the dashboard
summarystring–Unsupported: change manifest description and upload a new ZIP
supportUrlstring–Support URL; empty string clears it
titlestring–Unsupported: change manifest name and upload a new ZIP

No output schema declared.

No examples provided.

update-metadata-ui ~237

Save draft listing description, category, homepage or support URL via the signed-in Developer Dashboard, then reload to verify. Does not submit for review. Package title/summary, raw payloads, and icon uploads are unsupported.

NameTypeReqDescription
accountIndexinteger–Google account index
categorystring–Exact category label displayed by the dashboard
defaultLocalestring–Unsupported: change manifest default_locale and upload a new ZIP
descriptionstring–Detailed store listing description
headlessboolean–Run browser headless; use false for the first sign-in
homepageUrlstring–Homepage URL; empty string clears it
itemIdstring–Extension item ID
metadataobject–Unsupported: use the explicit dashboard fields
storeIconPathstring–Unsupported: upload the store icon directly in the dashboard
summarystring–Unsupported: change manifest description and upload a new ZIP
supportUrlstring–Support URL; empty string clears it
titlestring–Unsupported: change manifest name and upload a new ZIP

No output schema declared.

No examples provided.

upload ~104

Upload a ZIP file to update an existing Chrome Web Store item draft. Note: Creating new items via API is not supported in v2 — use the Developer Dashboard to create new items.

NameTypeReqDescription
itemIdstring–Extension item ID (defaults to CWS_ITEM_ID env var)
publisherIdstring–Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me')
zipPathstringyesAbsolute path to the ZIP file to upload

No output schema declared.

No examples provided.

Install

How do I install the io.github.mikusnuz/cws MCP server?

io.github.mikusnuz/cws runs locally as an npm package, launched with npx -y cws-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 · cws-mcp

# add to Claude Code
claude mcp add mikusnuz-cws -- npx -y cws-mcp
Common questions

What is the io.github.mikusnuz/cws MCP server?

io.github.mikusnuz/cws is an MCP server listed in the public MCP registry as io.github.mikusnuz/cws. MCP server for Chrome Web Store, extension upload, publish, status, and rollout. This page covers its npm package (cws-mcp).

Is the io.github.mikusnuz/cws MCP server safe to use?

io.github.mikusnuz/cws scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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.mikusnuz/cws MCP server expose?

io.github.mikusnuz/cws exposes 9 tools: upload, publish, status, cancel, deploy-percentage, and 4 more. Their descriptions and schemas cost roughly 1,190 tokens of context every time the server is loaded.

Is the io.github.mikusnuz/cws MCP server still maintained?

io.github.mikusnuz/cws is still listed as active in the MCP registry. We last reached this channel on 21 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.mikusnuz/cws MCP server under?

io.github.mikusnuz/cws declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.mikusnuz/cws MCP server?

VerifyMCP ran 16 checks on io.github.mikusnuz/cws, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.