io.github.mikusnuz/cws
NPM · CWS-MCP · SCANNED SEP 22
MCP server for Chrome Web Store — extension upload, publish, status, and rollout
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 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 47 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 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 1053 tokens (~117/item across 9 items; 8 tools + 1 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add mikusnuz-cws -- npx -y cws-mcp
{
"mcpServers": {
"mikusnuz-cws": {
"command": "npx",
"args": [
"-y",
"cws-mcp"
]
}
}
} {
"servers": {
"mikusnuz-cws": {
"command": "npx",
"args": [
"-y",
"cws-mcp"
]
}
}
} codex mcp add mikusnuz-cws -- npx -y cws-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mikusnuz-cws": {
"type": "local",
"command": [
"npx",
"-y",
"cws-mcp"
],
"enabled": true
}
}
} openclaw mcp add mikusnuz-cws --command npx --arg -y --arg cws-mcp
mcp_servers:
mikusnuz-cws:
command: "npx"
args: ["-y", "cws-mcp"] {
"McpServers": {
"mikusnuz-cws": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"cws-mcp"
]
}
}
} assistant mcp add mikusnuz-cws -t stdio -c npx -a -y cws-mcp
{
"mcpServers": {
"mikusnuz-cws": {
"command": "npx",
"args": [
"-y",
"cws-mcp"
]
}
}
} 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.
- 21 Sept 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.
- 19 Sept 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 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.
- 12 Sept 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.
- 10 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ 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 22 Sept 2026 · Analysed npm/cws-mcp@1.4.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 →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| 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 →
cancel ~71
Cancel a pending submission on Chrome Web Store. Can be used to cancel an item currently in review.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | string | – | Extension item ID (defaults to CWS_ITEM_ID env var) |
| publisherId | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | string | – | Extension item ID (defaults to CWS_ITEM_ID env var) |
| percentage | number | yes | Deploy percentage (0-100). Must be larger than the current target percentage. |
| publisherId | string | – | Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me') |
No output schema declared.
No examples provided.
get ~92
Get the current metadata of a Chrome Web Store item (v1.1 API). Returns title, description, category, and other listing fields. Note: v1 API is deprecated and will be removed after Oct 15, 2026.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | string | – | Extension item ID (defaults to CWS_ITEM_ID env var) |
| projection | string | – | Metadata projection to fetch (defaults to DRAFT) |
No output schema declared.
No examples provided.
publish ~158
Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, and skip-review.
| Name | Type | Req | Description |
|---|---|---|---|
| deployPercentage | integer | – | Initial deploy percentage for staged rollout (0-100). Only used with STAGED_PUBLISH or DEFAULT_PUBLISH. |
| itemId | string | – | Extension item ID (defaults to CWS_ITEM_ID env var) |
| publishType | string | – | DEFAULT_PUBLISH: publishes immediately after approval. STAGED_PUBLISH: stages for manual publishing after approval. Defaults to DEFAULT_PUBLISH. |
| publisherId | string | – | Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me') |
| skipReview | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | string | – | Extension item ID (defaults to CWS_ITEM_ID env var) |
| publisherId | string | – | Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me') |
No output schema declared.
No examples provided.
update-metadata ~205
Update the store listing metadata of a Chrome Web Store item (v1.1 API). Supports both common fields and raw metadata payload for advanced fields. Note: v1 API is deprecated and will be removed after Oct 15, 2026. Use update-metadata-ui as an alternative.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category (e.g. 'productivity', 'developer_tools') |
| defaultLocale | string | – | Default locale (e.g. 'ko', 'en') |
| description | string | – | Store listing description |
| homepageUrl | string | – | Homepage URL |
| itemId | string | – | Extension item ID (defaults to CWS_ITEM_ID env var) |
| metadata | object | – | Raw metadata object forwarded as-is to the v1 API. Useful for fields not exposed as first-class params. |
| summary | string | – | Store listing short summary |
| supportUrl | string | – | Support URL |
| title | string | – | Store listing title |
No output schema declared.
No examples provided.
update-metadata-ui ~189
Update listing metadata via Chrome Web Store dashboard UI automation (Playwright). Use this when API metadata updates are not reflected, or as the primary metadata update method since the v1 API is deprecated.
| Name | Type | Req | Description |
|---|---|---|---|
| accountIndex | integer | – | Google account index in dashboard URL (default: 0) |
| category | string | – | Category label as shown in dashboard UI |
| description | string | – | Store listing long description |
| headless | boolean | – | Run browser headless (default: false) |
| homepageUrl | string | – | Homepage URL |
| itemId | string | – | Extension item ID (defaults to CWS_ITEM_ID env var) |
| storeIconPath | string | – | Absolute path to 128x128 store icon image |
| summary | string | – | Store listing short summary |
| supportUrl | string | – | Support URL |
| title | string | – | Store listing title |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | string | – | Extension item ID (defaults to CWS_ITEM_ID env var) |
| publisherId | string | – | Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me') |
| zipPath | string | yes | Absolute path to the ZIP file to upload |
No output schema declared.
No examples provided.
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 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 8 tools: upload, publish, status, cancel, deploy-percentage, and 3 more. Their descriptions and schemas cost roughly 1,020 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 22 September 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.