Amitnarw Web MCP Server

@amitnarw/web-mcp npm v0.1.6

Published by @amitnarw — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Dedicated browser automation MCP server using an isolated Chromium profile and Extension to provide AI browser control. Fully supports OpenCode, Cursor, Claude Code, Zed Editor, Sourcegraph Cody, Windsurf, Cline, and OpenAI Codex.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/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
Minimal
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 99 − adoption risk = 97/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 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 99 − 2 = 97. 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
−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 6

low Shell/command execution in packaging/dev tooling (dist/cli/browser.min.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/cli/browser.min.js:1`): 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: awn as y,exec as S}from"child_process";import{promisify as E}from"util";var v=E(S),u=r.join(b.homedir(),".web-mcp");asyn

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 dist/cli/browser.min.js

low Shell/command execution in packaging/dev tooling (dist/cli/interactive.min.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/cli/interactive.min.js:9`): 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: n as le,exec as me}from"child_process";import{promisify as De}from"util";async function $e(){try{let n=await(await impor

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 dist/cli/interactive.min.js

low Shell/command execution in packaging/dev tooling (dist/cli/stop.min.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/cli/stop.min.js:1`): 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 as m}from"child_process";import{promisify as l}from"util";var t=l(m),p=i.join(c.homedir(),".web-mcp"),s=i.

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 dist/cli/stop.min.js

low Shell/command execution in packaging/dev tooling (dist/cli/troubleshoot.min.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/cli/troubleshoot.min.js:1`): 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 as u}from"child_process";import{promisify as x}from"util";var c=x(u);async function j(s){let e=["\x1B[36mR

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 dist/cli/troubleshoot.min.js

low Shell/command execution in packaging/dev tooling (dist/mcp/wrapper.min.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/mcp/wrapper.min.js:1`): 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: as F,execSync as E}from"child_process";import*as i from"fs";import*as u from"path";import*as J from"os";import{fileURLTo

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 dist/mcp/wrapper.min.js

low Package runs install-time scripts (postinstall)MTC-SUP-010

"@amitnarw/web-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: node bin/postinstall.js

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package @amitnarw/web-mcp

Tools 21

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

  • browser_clickno sensitive capability
  • browser_close_tabno sensitive capability
  • browser_doneno sensitive capability
  • browser_dragno sensitive capability
  • browser_evaluateno sensitive capability
  • browser_fillno sensitive capability
  • browser_get_statusno sensitive capability
  • browser_get_tabsno sensitive capability
  • browser_get_urlno sensitive capability
  • browser_hoverno sensitive capability
Show 11 more tools ↓
  • browser_navigateno sensitive capability
  • browser_new_tabno sensitive capability
  • browser_press_keyno sensitive capability
  • browser_screenshotno sensitive capability
  • browser_scrollno sensitive capability
  • browser_snapshotno sensitive capability
  • browser_startno sensitive capability
  • browser_stopno sensitive capability
  • browser_switch_tabno sensitive capability
  • browser_typeno sensitive capability
  • browser_waitno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v0.1.6 latest A 97/100 6 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.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/amitnarw-web-mcp/badge.svg)](https://mcptrustchecker.com/registry/amitnarw-web-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/amitnarw-web-mcp"><img src="https://mcptrustchecker.com/registry/amitnarw-web-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/amitnarw-web-mcp/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 @amitnarw/web-mcp --online

Use the free API → How scoring works

Other implementations of Amitnarw Web 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Web, Search & Scraping