scout-mcp-server
PyPI
v1.8.1
Published by stemado — 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 for browser automation with anti-detection. Scout pages, find elements, interact with websites, and monitor network traffic.
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 − 11 = 83. 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 |
|---|---|
| −10 | capability blast radius (critical) — 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.
In the server's implementation (`npm/index.js:18`): 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: , execSync } = require("child_process"); const IS_WIN = process.platform === "win32"; function commandExists(cmd) {
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 npm/index.js
In the server's implementation (`src/scout/profile_clone.py:167`): 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: result = subprocess.run( ["esentutl.exe", "/y", src, "/d", dst, "/o"],
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 src/scout/profile_clone.py
In the server's implementation (`src/scout/scheduler/linux.py:45`): 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: ne.""" result = subprocess.run( ["crontab", "-l"], capture_output=True, text=True,
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 src/scout/scheduler/linux.py
In the server's implementation (`src/scout/scheduler/macos.py:124`): 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: h.exists(): subprocess.run( ["launchctl", "unload", str(plist_path)], captur
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 src/scout/scheduler/macos.py
In the server's implementation (`src/scout/scheduler/windows.py:31`): 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: "] = "1" return subprocess.run( ["schtasks.exe", *args], capture_output=True,
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 src/scout/scheduler/windows.py
In the server's implementation (`src/scout/screencast.py:357`): 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: 5) result = subprocess.run( cmd, capture_output=True, timeou
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 src/scout/screencast.py
In the server's implementation (`npm/index.js:24`): 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: ists(cmd) { try { execSync(`${cmd} --version`, { stdio: "ignore", shell: true }); return true; } catch {
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 npm/index.js
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/capture_annotated_demos.py:306`): 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: etter color quality subprocess.run([ ffmpeg, "-y", "-framerate", str(fps), "-i", input_patte
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 scripts/capture_annotated_demos.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_native_messaging_host.py:38`): 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: input_msg) result = subprocess.run( [sys.executable, NM_HOST_SCRIPT], input=encoded, capture
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 tests/test_native_messaging_host.py
Each tool and what it can reach — statically extracted from the published source.
browseingests untrusted inputprocess_downloadingests untrusted inputallow_navigationno sensitive capabilitycheck_extensionno sensitive capabilityclose_sessionno sensitive capabilityexecute_action_toolno sensitive capabilityexecute_javascriptno sensitive capabilityfill_secretno sensitive capabilityfind_elementsno sensitive capabilityget_2fa_codeno sensitive capabilityget_security_logno sensitive capabilityget_session_historyno sensitive capabilityinspect_element_toolno sensitive capabilitylaunch_sessionno sensitive capabilitymonitor_networkno sensitive capabilityrecord_videono sensitive capabilityschedule_createno sensitive capabilityschedule_deleteno sensitive capabilityschedule_listno sensitive capabilityscout_page_toolno sensitive capabilitytake_screenshot_toolno sensitive capabilityScan 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.8.1 latest |
B 83/100 | 9 | 1.13.0 | 2026-08-25 |
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 scout-mcp-server --online --registry pypi
Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →
Scout your MCP tools before loading them: search_tools/describe_tools/call_tool meta-tools so clients don't pay the full tool-schema context tax upfront.
MCP server for Claude Code integration with Scout - AI-powered test management and bug tracking
Browser MCP server that connects to your existing browser — your sessions, passwords, and extensions preserved
Scout MCP server for enhanced coding context via vector search and RAG
MCP server for Scout - exposes Scout query capabilities to other agents
MCP server for browser automation with anti-detection. Scout pages, find elements, interact with websites, and monitor network traffic.
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.