io.github.CloudCorpRecords/headlessstage
NPM · @RENETURCIOS/HEADLESSSTAGE · 2 COMPONENTS
Browser automation: navigate, click, fill, screenshot and evaluate in a headless browser.
Available components
Last scanned (9 hours ago)
Scores higher than 33% 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 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
- 30 of 93 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 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 360 tokens (~51/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "puppeteer_evaluate" implies "execute" 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 7 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
- Stability: unverified → 0.07 ▲ functional
- 31 Oct 26 62
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@reneturcios/headlessstage@0.1.0
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 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
puppeteer_click ~30
Click elements on the page
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | The CSS selector of the element to click |
No output schema declared.
No examples provided.
puppeteer_evaluate ~35
Execute JavaScript in the browser console
| Name | Type | Req | Description |
|---|---|---|---|
| script | string | yes | The JavaScript code to execute in the browser console |
No output schema declared.
No examples provided.
puppeteer_fill ~44
Fill out input fields
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | The CSS selector of the input field to fill |
| value | string | yes | The value to enter into the field |
No output schema declared.
No examples provided.
puppeteer_hover ~31
Hover elements on the page
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | The CSS selector of the element to hover over |
No output schema declared.
No examples provided.
puppeteer_navigate ~71
Navigate to any URL in the browser
| Name | Type | Req | Description |
|---|---|---|---|
| allowDangerous | boolean | – | Whether to allow dangerous launch options such as disabling the browser sandbox |
| launchOptions | object | – | Optional Puppeteer launch options object for the browser instance |
| url | string | yes | The URL to navigate the browser to |
No output schema declared.
No examples provided.
puppeteer_screenshot ~106
Capture screenshots of the entire page or specific elements
| Name | Type | Req | Description |
|---|---|---|---|
| encoded | boolean | – | Whether to return the screenshot as a base64 encoded data URL |
| height | number | – | Optional viewport height in pixels for the screenshot |
| name | string | yes | The name to store the screenshot under |
| selector | string | – | Optional CSS selector of the element to screenshot; the full page is captured when omitted |
| width | number | – | Optional viewport width in pixels for the screenshot |
No output schema declared.
No examples provided.
puppeteer_select ~43
Select an element with a SELECT tag
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | The CSS selector of the SELECT element |
| value | string | yes | The option value to select |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/headlessstage MCP server?
io.github.CloudCorpRecords/headlessstage runs locally as an npm package, launched with npx -y @reneturcios/headlessstage. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/headlessstage
claude mcp add cloudcorprecords-headlessstage -- npx -y @reneturcios/headlessstage
What is the io.github.CloudCorpRecords/headlessstage MCP server?
io.github.CloudCorpRecords/headlessstage is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/headlessstage. Browser automation: navigate, click, fill, screenshot and evaluate in a headless browser. This page covers its npm package (@reneturcios/headlessstage).
Is the io.github.CloudCorpRecords/headlessstage MCP server safe to use?
io.github.CloudCorpRecords/headlessstage scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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.CloudCorpRecords/headlessstage MCP server expose?
io.github.CloudCorpRecords/headlessstage exposes 7 tools: puppeteer_navigate, puppeteer_screenshot, puppeteer_click, puppeteer_hover, puppeteer_fill, and 2 more. Their descriptions and schemas cost roughly 360 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/headlessstage MCP server still maintained?
io.github.CloudCorpRecords/headlessstage is still listed as active in the MCP registry. We last reached this channel on 5 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.CloudCorpRecords/headlessstage MCP server under?
io.github.CloudCorpRecords/headlessstage declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.