Browsentic
NPM · BROWSENTIC
Agentic browser harness: your agent CLI in your real, signed-in browser, from a side panel or MCP.
Available components
Last scanned (22 hours ago)
Scores higher than 93% 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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to imshaikot/browsentic). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- 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 9060 tokens (~167/item across 54 items; 51 tools + 3 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 Management70
- Stability observed for 21 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; "page_pressKey" implies "send" 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 53 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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +40
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.63 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.8.0 → 0.8.9 functional
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- Package version: 0.8.1 → 0.8.9 functional
- Package version: 0.8.0 → 0.8.1 functional
- 11 Oct 26 −37
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.8.0 → 0.8.1 functional
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 37. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 0
- Stability: 0.27 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Licence: MIT → Apache-2.0 functional
- Package version: 0.7.15 → 0.8.0 functional
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +15
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.7.14 → 0.7.15 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 16 Oct 2026 · Analysed npm/browsentic@0.8.9
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | imshaikot/browsentic |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/imshaikot/browsentic/.github/workflows/release.yml@refs/tags/v0.8.9 |
| Rekor log index | 3225138434 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b48bb16a846cde9e3667035df9e5ebfdeca827b5867690fb164d447412c3e7aa721b56a37b396c40f9aee7664106af7b2da9e62d917fd6c2fd5173cd3 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
page_waitForElement ~79
Wait until an element reaches a state: attached, visible, hidden, or detached.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | State to wait for: present in the DOM, present and visible, invisible or absent, or absent |
| target | object | yes | Element to wait for |
| timeoutMs | integer | – | Give up after this many milliseconds |
No output schema declared.
No examples provided.
How do I install the Browsentic MCP server?
Browsentic runs locally as an npm package, launched with npx -y browsentic. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · browsentic
claude mcp add imshaikot-browsentic -- npx -y browsentic
What is the Browsentic MCP server?
Browsentic is an MCP server listed in the public MCP registry as io.github.imshaikot/browsentic. Agentic browser harness: your agent CLI in your real, signed-in browser, from a side panel or MCP. This page covers its npm package (browsentic).
Is the Browsentic MCP server safe to use?
Browsentic scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Browsentic MCP server expose?
Browsentic exposes 51 tools: page_getPageInfo, page_scrollTo, page_clickElement, page_trustedClick, page_findCaptcha, and 46 more. Their descriptions and schemas cost roughly 8,744 tokens of context every time the server is loaded.
Is the Browsentic MCP server still maintained?
Browsentic is still listed as active in the MCP registry. We last reached this channel on 16 October 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 Browsentic MCP server under?
Browsentic declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.