by shaun0927 · MCP Server · ★ 238
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
npm install -g openchrome-mcp
git clone https://github.com/shaun0927/openchrome.gitTaken from the project's README on GitHub. Check the security audit before running it.
None of the 42 rules matched — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against 42 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours. Full audit →
The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.
| Stars | 238 |
| Forks | 41 |
| Language | TypeScript |
| Category | MCP Server |
| License | MIT |
| Quality Score | 66/100 |
| Open Issues | 17 |
| Last Updated | 2026-09-29 |
| Created | 2026-01-24 |
| Platforms | browser, mcp, node |
| Est. Tokens | ~14k |
OpenChrome OpenChrome is a browser automation MCP server for controlling a real Chrome browser from Claude Code, Codex CLI, OpenCode, or any MCP client. It ships as a Node CLI plus MCP runtime. Desktop apps, browser extensions, native-host installers, deployment templates, and release artifact builders are outside this repository surface. Install Requires Node.js 20 or newer.
Explore other popular mcp server tools:
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 42 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: