Domshell MCP Server

@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.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

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:

PointsAdoption-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.

Findings 3

high Tool "domshell_eval" exposes command/code executionMTC-CAP-001

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

medium Untrusted input can drive an external actionMTC-FLOW-005

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

low Mutating tool "domshell_eval" declares no destructiveHintMTC-CAP-005

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

Tools 39

Each tool and what it can reach — statically extracted from the published source.

  • domshell_evalruns code / shell
  • domshell_refreshingests untrusted input
  • domshell_aboutno sensitive capability
  • domshell_backno sensitive capability
  • domshell_callno sensitive capability
  • domshell_catno sensitive capability
  • domshell_cdno sensitive capability
  • domshell_clickno sensitive capability
  • domshell_closeno sensitive capability
  • domshell_diffno sensitive capability
Show 29 more tools ↓
  • domshell_eachno sensitive capability
  • domshell_executeno sensitive capability
  • domshell_extract_linksno sensitive capability
  • domshell_extract_tableno sensitive capability
  • domshell_findno sensitive capability
  • domshell_focusno sensitive capability
  • domshell_forno sensitive capability
  • domshell_forwardno sensitive capability
  • domshell_functionsno sensitive capability
  • domshell_grepno sensitive capability
  • domshell_hereno sensitive capability
  • domshell_jsno sensitive capability
  • domshell_lsno sensitive capability
  • domshell_navigateno sensitive capability
  • domshell_openno sensitive capability
  • domshell_pwdno sensitive capability
  • domshell_readno sensitive capability
  • domshell_screenshotno sensitive capability
  • domshell_scriptno sensitive capability
  • domshell_scrollno sensitive capability
  • domshell_selectno sensitive capability
  • domshell_submitno sensitive capability
  • domshell_tabsno sensitive capability
  • domshell_textno sensitive capability
  • domshell_treeno sensitive capability
  • domshell_typeno sensitive capability
  • domshell_waitno sensitive capability
  • domshell_watchno sensitive capability
  • domshell_whoamino sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 3

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.

VersionScoreFindingsEngineScanned
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

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/apireno-domshell/badge.svg)](https://mcptrustchecker.com/registry/apireno-domshell)
HTML
<a href="https://mcptrustchecker.com/registry/apireno-domshell"><img src="https://mcptrustchecker.com/registry/apireno-domshell/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/apireno-domshell/badge.json via https://img.shields.io/endpoint?url=…

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 @apireno/domshell --online

Use the free API → How scoring works

More in Browser Automation