ThinkRun MCP Server

@thinkrun/mcp npm v0.3.14

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

Connects AI coding agents to the user's real Chrome browser with real sessions and cookies so they can test their own frontend work.

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 9

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

Tool "extract" appears to run shell commands or evaluate code (parameter "script"). 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 extract

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

Tool "evaluate" appears to run shell commands or evaluate code (parameter "script"). 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 evaluate

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

In the server's implementation (`dist/src/onboarding.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: spawnSync } from 'node:child_process'; import { existsSync, readFileSync, readdirSync, statSync, } from 'node:fs'; impo

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/src/onboarding.js

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

Untrusted-input tools ([page_cache_html]) co-exist with external-action tools ([extract, evaluate]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [page_cache_html] → sinks [extract, evaluate]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow page_cache_html → extract

medium Unconstrained URL/host parameter "url" on "page_cache_html"MTC-CAP-007

Tool "page_cache_html" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool page_cache_html · inputSchema.properties.url

medium Unconstrained command parameter "script" on "extract"MTC-CAP-006

Tool "extract" takes a command-shaped parameter "script" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool extract · inputSchema.properties.script

medium Unconstrained command parameter "script" on "evaluate"MTC-CAP-006

Tool "evaluate" takes a command-shaped parameter "script" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool evaluate · inputSchema.properties.script

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

Tool "extract" 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 extract

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

Tool "evaluate" 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 evaluate

Tools 67

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

  • evaluateruns code / shell
  • extractruns code / shell
  • page_cache_htmlingests untrusted input
  • agent_identityno sensitive capability
  • browser_clickno sensitive capability
  • browser_extractno sensitive capability
  • browser_fillno sensitive capability
  • browser_grant_statusno sensitive capability
  • browser_navigateno sensitive capability
  • browser_release_controlno sensitive capability
Show 57 more tools ↓
  • browser_request_controlno sensitive capability
  • browser_screenshotno sensitive capability
  • browser_snapshotno sensitive capability
  • browser_type_textno sensitive capability
  • browser_wait_for_textno sensitive capability
  • clear_logsno sensitive capability
  • clickno sensitive capability
  • click_atno sensitive capability
  • console_messagesno sensitive capability
  • fillno sensitive capability
  • focusno sensitive capability
  • get_dialogno sensitive capability
  • get_htmlno sensitive capability
  • get_titleno sensitive capability
  • get_urlno sensitive capability
  • go_backno sensitive capability
  • go_forwardno sensitive capability
  • handle_dialogno sensitive capability
  • hoverno sensitive capability
  • local_action_cancelno sensitive capability
  • local_action_runno sensitive capability
  • local_action_statusno sensitive capability
  • local_diagnosticsno sensitive capability
  • local_reset_connectionno sensitive capability
  • navigateno sensitive capability
  • network_requestsno sensitive capability
  • page_cache_screenshotno sensitive capability
  • page_cache_textno sensitive capability
  • press_keyno sensitive capability
  • recording_uploadno sensitive capability
  • screenshotno sensitive capability
  • scrollno sensitive capability
  • select_optionno sensitive capability
  • session_artifactsno sensitive capability
  • session_createno sensitive capability
  • session_deleteno sensitive capability
  • session_listno sensitive capability
  • session_releaseno sensitive capability
  • session_statusno sensitive capability
  • session_useno sensitive capability
  • session_wait_readyno sensitive capability
  • set_auditingno sensitive capability
  • set_modeno sensitive capability
  • sleepno sensitive capability
  • snapshotno sensitive capability
  • tab_attachno sensitive capability
  • tab_closeno sensitive capability
  • tab_listno sensitive capability
  • tab_newno sensitive capability
  • tab_switchno sensitive capability
  • task_createno sensitive capability
  • task_executeno sensitive capability
  • task_statusno sensitive capability
  • type_textno sensitive capability
  • wait_for_elementno sensitive capability
  • wait_for_textno sensitive capability
  • window_newno 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
v0.3.14 latest A 93/100 9 1.13.0 2026-09-04
v0.3.13 A 93/100 9 1.13.0 2026-08-25
v0.3.12 A 93/100 9 1.12.1 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/thinkrun-mcp/badge.svg)](https://mcptrustchecker.com/registry/thinkrun-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/thinkrun-mcp"><img src="https://mcptrustchecker.com/registry/thinkrun-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/thinkrun-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 @thinkrun/mcp --online

Use the free API → How scoring works

More in Browser Automation