@apireno/domshell
npm
v2.0.10
Published by @apireno — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server that gives AI agents Unix-style filesystem commands (ls, cd, grep, click, type) to drive Chrome. Single-tool interface, concurrent multi-agent isolation, per-lane tab groups.
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. 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 |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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.
Tool "domshell_eval" appears to run shell commands or evaluate code (keyword "eval" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool domshell_eval
Untrusted-input tools ([domshell_refresh]) co-exist with external-action tools ([domshell_eval]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [domshell_refresh] → sinks [domshell_eval]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow domshell_refresh → domshell_eval
Tool "domshell_eval" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool domshell_eval
Each tool and what it can reach — statically extracted from the published source.
domshell_evalruns code / shelldomshell_refreshingests untrusted inputdomshell_aboutno sensitive capabilitydomshell_backno sensitive capabilitydomshell_callno sensitive capabilitydomshell_catno sensitive capabilitydomshell_cdno sensitive capabilitydomshell_clickno sensitive capabilitydomshell_closeno sensitive capabilitydomshell_diffno sensitive capabilitydomshell_eachno sensitive capabilitydomshell_executeno sensitive capabilitydomshell_extract_linksno sensitive capabilitydomshell_extract_tableno sensitive capabilitydomshell_findno sensitive capabilitydomshell_focusno sensitive capabilitydomshell_forno sensitive capabilitydomshell_forwardno sensitive capabilitydomshell_functionsno sensitive capabilitydomshell_grepno sensitive capabilitydomshell_hereno sensitive capabilitydomshell_jsno sensitive capabilitydomshell_lsno sensitive capabilitydomshell_navigateno sensitive capabilitydomshell_openno sensitive capabilitydomshell_pwdno sensitive capabilitydomshell_readno sensitive capabilitydomshell_screenshotno sensitive capabilitydomshell_scriptno sensitive capabilitydomshell_scrollno sensitive capabilitydomshell_selectno sensitive capabilitydomshell_submitno sensitive capabilitydomshell_tabsno sensitive capabilitydomshell_textno sensitive capabilitydomshell_treeno sensitive capabilitydomshell_typeno sensitive capabilitydomshell_waitno sensitive capabilitydomshell_watchno sensitive capabilitydomshell_whoamino sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
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 |
|---|---|---|---|---|
v2.0.10 latest |
A 93/100 | 3 | 1.13.0 | 2026-09-07 |
v2.0.9 |
A 93/100 | 3 | 1.12.1 | 2026-08-14 |
v2.0.8 |
A 93/100 | 3 | 1.10.0 | 2026-07-27 |
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.
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 @apireno/domshell --online
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