Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.dundas/thinkrun

NPM · @THINKRUN/MCP · SCANNED SEP 20

Browser control + session recording MCP for AI coding agents (Claude Code, Cursor) — real Chrome.

Available components

npm · @thinkrun/mcp 38
0 this week 38 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 96 of 97 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 96 of 97 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the io.github.dundas/thinkrun MCP server?

io.github.dundas/thinkrun runs locally as an npm package, launched with npx -y @thinkrun/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @thinkrun/mcp

# add to Claude Code
claude mcp add dundas-thinkrun -- npx -y @thinkrun/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "dundas-thinkrun": {
      "command": "npx",
      "args": [
        "-y",
        "@thinkrun/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dundas-thinkrun": {
      "command": "npx",
      "args": [
        "-y",
        "@thinkrun/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dundas-thinkrun -- npx -y @thinkrun/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dundas-thinkrun": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@thinkrun/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dundas-thinkrun --command npx --arg -y --arg @thinkrun/mcp
# ~/.hermes/config.yaml
mcp_servers:
  dundas-thinkrun:
    command: "npx"
    args: ["-y", "@thinkrun/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dundas-thinkrun": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@thinkrun/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dundas-thinkrun -t stdio -c npx -a -y @thinkrun/mcp
// mcp.json
{
  "mcpServers": {
    "dundas-thinkrun": {
      "command": "npx",
      "args": [
        "-y",
        "@thinkrun/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 13 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 10 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 2 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 1 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Aug 26 38
    • Security disclosure: unverified → fail ▼ functional
  • 20 Aug 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 16 Aug 26 0
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@thinkrun/mcp@0.3.8

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the io.github.dundas/thinkrun MCP server?

io.github.dundas/thinkrun is an MCP server listed in the public MCP registry as io.github.dundas/thinkrun. Browser control + session recording MCP for AI coding agents (Claude Code, Cursor), real Chrome. This page covers its npm package (@thinkrun/mcp).

Is the io.github.dundas/thinkrun MCP server safe to use?

io.github.dundas/thinkrun scores 38 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the io.github.dundas/thinkrun MCP server still maintained?

io.github.dundas/thinkrun is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.dundas/thinkrun MCP server under?

io.github.dundas/thinkrun declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.