Pilot MCP Server

pilot-mcp npm v0.4.2

Published by tacosyhorchata — 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.

Fast browser automation MCP server for LLMs — persistent Chromium, ref-based interaction, cookie migration

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/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 99 − adoption risk = 92/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 − 7 = 92. 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 6

high Dynamic evaluation of a non-literal value (extension/content.js)MTC-SRC-010

In the server's implementation (`extension/content.js:334`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: o-eval const result = eval(script); return { result: typeof result === 'object' ? JSON.stringify(result) : String(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 extension/content.js

high Dynamic code execution in server code (extension/content.js)MTC-SRC-001

In the server's implementation (`extension/content.js:334`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: o-eval const result = eval(script); return { result: typeof result === 'object' ? JSON.stringify(result) : String(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 extension/content.js

high Shell/command execution in server code (dist/cli/client.js)MTC-SRC-002

In the server's implementation (`dist/cli/client.js:26`): 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 { spawn } from 'child_process'; import { fileURLToPath } from 'url'; const SOCKET_PATH = path.join(os.tmpdir(),

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/client.js

high Shell/command execution in server code (dist/cookie-import.js)MTC-SRC-002

In the server's implementation (`dist/cookie-import.js:15`): 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 { spawn } from 'child_process'; export class CookieImportError extends Error { code; action; constru

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/cookie-import.js

high Shell/command execution in server code (dist/index.js)MTC-SRC-002

In the server's implementation (`dist/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: port { execSync } from 'child_process'; import * as fs from 'fs'; import * as path from 'path'; import * as os from 'os'

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/index.js

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

"pilot-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 scripts/postinstall.js

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

Location: package pilot-mcp

Tools 61

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

  • pilot_annotated_screenshotno sensitive capability
  • pilot_assertno sensitive capability
  • pilot_authno sensitive capability
  • pilot_backno sensitive capability
  • pilot_blockno sensitive capability
  • pilot_cdpno sensitive capability
  • pilot_clickno sensitive capability
  • pilot_clipboardno sensitive capability
  • pilot_closeno sensitive capability
  • pilot_consoleno sensitive capability
Show 51 more tools ↓
  • pilot_cookiesno sensitive capability
  • pilot_dialogno sensitive capability
  • pilot_dragno sensitive capability
  • pilot_element_stateno sensitive capability
  • pilot_evaluateno sensitive capability
  • pilot_extension_statusno sensitive capability
  • pilot_file_uploadno sensitive capability
  • pilot_fillno sensitive capability
  • pilot_findno sensitive capability
  • pilot_forwardno sensitive capability
  • pilot_frame_resetno sensitive capability
  • pilot_frame_selectno sensitive capability
  • pilot_framesno sensitive capability
  • pilot_geolocationno sensitive capability
  • pilot_getno sensitive capability
  • pilot_handle_dialogno sensitive capability
  • pilot_handoffno sensitive capability
  • pilot_hoverno sensitive capability
  • pilot_import_cookiesno sensitive capability
  • pilot_interceptno sensitive capability
  • pilot_navigateno sensitive capability
  • pilot_networkno sensitive capability
  • pilot_page_attrsno sensitive capability
  • pilot_page_cssno sensitive capability
  • pilot_page_diffno sensitive capability
  • pilot_page_formsno sensitive capability
  • pilot_page_htmlno sensitive capability
  • pilot_page_linksno sensitive capability
  • pilot_page_textno sensitive capability
  • pilot_pdfno sensitive capability
  • pilot_perfno sensitive capability
  • pilot_press_keyno sensitive capability
  • pilot_reloadno sensitive capability
  • pilot_resizeno sensitive capability
  • pilot_responsiveno sensitive capability
  • pilot_resumeno sensitive capability
  • pilot_screenshotno sensitive capability
  • pilot_scrollno sensitive capability
  • pilot_select_optionno sensitive capability
  • pilot_set_cookieno sensitive capability
  • pilot_set_headerno sensitive capability
  • pilot_set_useragentno sensitive capability
  • pilot_snapshotno sensitive capability
  • pilot_snapshot_diffno sensitive capability
  • pilot_storageno sensitive capability
  • pilot_tab_closeno sensitive capability
  • pilot_tab_newno sensitive capability
  • pilot_tab_selectno sensitive capability
  • pilot_tabsno sensitive capability
  • pilot_typeno sensitive capability
  • pilot_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.4.2 latest A 92/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 · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/pilot-mcp/badge.svg)](https://mcptrustchecker.com/registry/pilot-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/pilot-mcp"><img src="https://mcptrustchecker.com/registry/pilot-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pilot-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 pilot-mcp --online

Use the free API → How scoring works

More in Browser Automation