Browser Tools (npm) MCP Server
mcp-browser-tools
npm
v2.0.2
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
A powerful suite of 36 development and analysis tools for browser automation and web application analysis.
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 − 5 = 95. 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 |
|---|---|
| −3 | capability blast radius (moderate) — 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
medium Hardcoded egress to an external endpoint (dist/mcp-server.js)MTC-SRC-003
In the server's implementation (`dist/mcp-server.js:57`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const response = await fetch(`http://${host}:${port}/.identity`, { signal: AbortSignal.timeout(1000) });
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-server.js
medium Hardcoded egress to an external endpoint (mcp-server.ts)MTC-SRC-003
In the server's implementation (`mcp-server.ts:56`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const response = await fetch(`http://${host}:${port}/.identity`, { signal: AbortSignal.timeout(1000) }); if (re
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 mcp-server.ts
Tools 36
Each tool and what it can reach — statically extracted from the published source.
analyzeConsoleErrorsno sensitive capabilityanalyzeNetworkPerformanceno sensitive capabilityanalyzeTechStackno sensitive capabilityassessPageComplexityno sensitive capabilitycheckNavigationStatusno sensitive capabilitycompareScreenshotsOverTimeno sensitive capabilitycreatePageHealthSummaryno sensitive capabilitycreatePerformanceBudgetno sensitive capabilitydetectAPIErrorsno sensitive capabilitydetectConsolePatternsno sensitive capability
Show 26 more tools ↓
detectLayoutIssuesno sensitive capabilityenableNavigationno sensitive capabilityexportDevelopmentDatano sensitive capabilityextractColorPaletteno sensitive capabilityextractPageMetadatano sensitive capabilitygenerateComprehensiveReportno sensitive capabilitygenerateLighthouseCIno sensitive capabilitygetConsoleErrorsno sensitive capabilitygetConsoleLogsno sensitive capabilitygetNetworkErrorsno sensitive capabilitygetNetworkLogsno sensitive capabilitygetSelectedElementno sensitive capabilityidentifyUnusedResourcesno sensitive capabilityrunAccessibilityAuditno sensitive capabilityrunAuditModeno sensitive capabilityrunBestPracticesAuditno sensitive capabilityrunDebuggerModeno sensitive capabilityrunNextJSAuditno sensitive capabilityrunPerformanceAuditno sensitive capabilityrunSEOAuditno sensitive capabilitysummarizeConsoleActivityno sensitive capabilitytakeScreenshotno sensitive capabilitytrackConsoleWarningsno sensitive capabilitytrackImprovementTrendsno sensitive capabilitytrackResourceLoadingno sensitive capabilitywipeLogsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (36 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 |
|---|---|---|---|---|
v2.0.2 latest |
A 95/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 mcp-browser-tools --onlineOther implementations of Browser Tools 4
Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →
Monitors and interacts with your local browser: console logs, network traffic, audits and screenshots.
MCP (Model Context Protocol) server for browser tools integration
MCP (Model Context Protocol) server for browser tools integration
A starter template for building MCP (Model Context Protocol) servers
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.