public-browser (Silbercue/public-browser) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 3 tools. No publisher has claimed this listing.

C
Emerging
74/100

public-browser

Lets Claude Code and Cursor drive Chrome. Browse your real profile: -30% tokens, -25% cost, -41% tool calls, -34% tool defs, +40% faster. Direct CDP, a11y-tree refs, server-side plan executor. MIT, no paid tier.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Silbercue

Source: Glama · also listed on github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Known vulnerabilities in dependencies: 2 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// tools this server exposes3 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

inspect_element

Inspect CSS + geometry (Pro)

late_tool

Registered too late

too_early

No delegate yet

// known CVEs in dependencies2 critical1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@3GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

Zod denial of service vulnerability

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCHROME_PATHGoogle Chrome, Chromium, or any Chromium-based browser (auto-detected on macOS/Linux/Windows; override with )
configPUBLIC_BROWSER_CORTEX_DIR
configPUBLIC_BROWSER_PROFILE"Julian" npx public-browser
configPUBLIC_BROWSER_TELEMETRY1 / true — (disabled) Opt-in: upload anonymised Cortex patterns to the community endpoint
configPUBLIC_BROWSER_TELEMETRY_ENDPOINTURL https://cortex.public-browser.dev/v1/patterns Override the telemetry collection endpoint (must be HTTPS)
configProgramFiles
configProgramFiles(x86)
configSILBERCUE_CHROME_DIFF_RETRY_MS
configSILBERCUE_CHROME_DIFF_SETTLE_MS
configSILBERCUE_CHROME_FULL_TOOLS
configSILBERCUE_CHROME_HEADLESStrue / false false Opt-in headless mode for CI/server environments
configSILBERCUE_CHROME_MINIMAL_TOOLS
configSILBERCUE_CHROME_PORT1–65535 9222 CDP debugging port. Non-default values spawn an isolated Chrome instance (separate --user-data-dir) that won't conflict with the user's browser
configSILBERCUE_CHROME_PROFILEpath — Chrome user profile directory (auto-launch only)
configSILBERCUE_PUBLISH_BRANCH
configSILBERCUE_PUBLISH_REMOTE
configSILBERCUE_SCRIPT_PORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

3/3 tools missing one or more hints — inspect_element (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); late_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); too_early (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 0/2 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/2 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 0/3 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

1/4 production deps stale: pngjs@2023-02-20 (3.3y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/silbercue/public-browser)](https://m8ven.ai/mcp/silbercue/public-browser)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: d105ff66dd12ea0bb1bed7130d101c56bf3325ab
code hash: 95a8d5610df9f7f657065ee36a5ba48f8e10b271454b5e57f161421442469db7
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client