Codingbaby Browser MCP Server
@sydneyassistent/codingbaby-browser-mcp
npm
v1.1.6
Published by @sydneyassistent — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP tool for communicating with a Chrome extension via WebSocket
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
2. Client adoption risk — 94 − 8 = 86. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
high Shell/command execution in server code (chrome-client.js)MTC-SRC-002
In the server's implementation (`chrome-client.js:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: " import { exec } from "child_process" // 添加检测和释放端口的辅助方法 async function checkAndReleasePort(port) { console.error(`正在检
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server chrome-client.js
medium Untrusted input concatenated into a command sink (chrome-client.js)MTC-SRC-009
In the server's implementation (`chrome-client.js:48`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: `) try { exec(`taskkill /F /PID ${pid}`, (err) => { if (err) { console.error(`结束进程 ${p
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server chrome-client.js
Tools 15
Each tool and what it can reach — statically extracted from the published source.
area_screenshotno sensitive capabilitybatchno sensitive capabilityclickno sensitive capabilitycloseno sensitive capabilitynavigateno sensitive capabilitypress_keyno sensitive capabilitysave_htmlno sensitive capabilityscrollno sensitive capabilityset_viewportno sensitive capabilitytab_closeno sensitive capability
Show 5 more tools ↓
tab_listno sensitive capabilitytab_newno sensitive capabilitytab_selectno sensitive capabilitytypeno sensitive capabilitywaitno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (15 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.6 latest |
B 86/100 | 2 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @sydneyassistent/codingbaby-browser-mcp --onlineMore in Browser Automation
Model Context Protocol (MCP) server that integrates AgentQL data extraction capabilities.
Screenshot any URL or HTML as PNG/JPEG/WebP from your AI agent. Full-page, clean, no install.
MCP server for aria51 accessibility scanner
Bridge any browser web app to Claude Code via MCP
Browserbase’s official MCP server: cloud headless browsers for agents, with sessions and screenshots.
MCP server for AI web browser automation using Browserbase and Stagehand