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.

Tabhand

NPM · TABHAND

Let your coding agents use your real, signed-in Chrome, in background tabs that never steal focus.

Available components

+3 this week 85 Trust /100

Last scanned (12 hours ago)

Scores higher than 77% of npm servers

Category Browser Automation

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1467 tokens (~112/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1
    • Stability: 0.97 → pass security
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1
    • 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 22 Nov 2026 · Analysed npm/tabhand@0.10.1

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 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,159 tokens

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 →

Tool Tokens
browser_click ~141

Click an element by its ref from browser_snapshot, or else by the text it shows. Waits for any page load the click starts. Links and popups that open a new tab stay in the background, join this session, and are listed in the result. Clicking an option of a dropdown chooses it.

NameTypeReqDescription
refstring–Element ref from browser_snapshot, e.g. e123.
tabIdintegeryesTab id from browser_open_tab or browser_list_tabs.
textstring–Instead of a ref: the visible text of the element to click, for something the snapshot gives no ref but you can see in a screenshot.

No output schema declared.

No examples provided.

browser_close_tab ~41

Close one of this session's tabs when you are done with it.

NameTypeReqDescription
tabIdintegeryesTab id from browser_open_tab or browser_list_tabs.

No output schema declared.

No examples provided.

browser_handle_dialog ~107

Answer a confirm or prompt dialog the page opened: accept it (OK) or dismiss it (Cancel). The page waits until it is answered. Alerts are closed for you. Ask the user first if accepting would send, buy, delete or change something.

NameTypeReqDescription
acceptbooleanyestrue for OK, false for Cancel.
tabIdintegeryesTab id from browser_open_tab or browser_list_tabs.
textstring–What to enter, for a prompt dialog.

No output schema declared.

No examples provided.

browser_list_profiles ~53

List the Chrome profiles that have Tabhand (for example work and personal, each signed in to different accounts): each one's name, whether Tabhand is on or paused there, and which one your new tabs open in.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_list_tabs ~30

List the tabs this session has open. Other sessions' tabs and the user's own tabs are never shown.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_navigate ~55

Load a URL in one of this session's tabs and wait for it to finish loading.

NameTypeReqDescription
tabIdintegeryesTab id from browser_open_tab or browser_list_tabs.
urlstringyesPage to load.

No output schema declared.

No examples provided.

browser_open_tab ~141

Open a new tab in the user's own Chrome, with their logins, and optionally load a URL. The tab opens in the background inside this session's tab group: Chrome is not brought to the front and the user's tabs are untouched, so they can keep working. Returns the tabId the other browser tools need.

NameTypeReqDescription
profilestring–Chrome profile to open the tab in, by its name or id from browser_list_profiles. Only needed when the user has Tabhand in several profiles. Your later tabs open there too.
urlstring–Page to load, e.g. https://example.com. Omit for a blank tab.

No output schema declared.

No examples provided.

browser_press_key ~98

Press a key in the page: Enter, Tab, Escape, Backspace, Delete, ArrowUp/Down/Left/Right, Home, End, PageUp, PageDown, Space, a single character, or a combination such as Shift+Tab.

NameTypeReqDescription
keystringyesKey or combination, e.g. Enter or Shift+Tab.
tabIdintegeryesTab id from browser_open_tab or browser_list_tabs.

No output schema declared.

No examples provided.

browser_screenshot ~87

Take a screenshot of one of this session's tabs, even though it is in the background. Prefer browser_snapshot for reading text; use screenshots to check layout and visuals.

NameTypeReqDescription
fullPageboolean–Capture the whole page instead of the visible area (capped at 8000 px tall).
tabIdintegeryesTab id from browser_open_tab or browser_list_tabs.

No output schema declared.

No examples provided.

browser_scroll ~74

Scroll the page up or down, e.g. to load more content or bring something into view for a screenshot.

NameTypeReqDescription
amountnumber–Pixels to scroll. Defaults to 600.
directionstring–Defaults to down.
tabIdintegeryesTab id from browser_open_tab or browser_list_tabs.

No output schema declared.

No examples provided.

browser_snapshot ~91

Read the page as an accessibility outline (headings, text, links, buttons, fields). Elements you can act on carry a ref like e123 for browser_click and browser_type; plain elements the page made clickable show as "clickable". Refs stop working after the page changes, so take a new snapshot then.

NameTypeReqDescription
tabIdintegeryesTab id from browser_open_tab or browser_list_tabs.

No output schema declared.

No examples provided.

browser_type ~131

Type text into a field. Pass the field's ref to focus it first; omit ref to type into whatever already has focus. Set clear to replace the existing text and submit to press Enter afterwards. Given a dropdown's ref, chooses the option with that text.

NameTypeReqDescription
clearboolean–Replace the field's current text.
refstring–Field ref from browser_snapshot, e.g. e123.
submitboolean–Press Enter after typing.
tabIdintegeryesTab id from browser_open_tab or browser_list_tabs.
textstringyesText to type.

No output schema declared.

No examples provided.

browser_upload_file ~110

Attach files from this computer to the page, as if the user picked them. Pass the ref of a file field, or of the button that opens a file picker (no system dialog appears).

NameTypeReqDescription
pathsarrayyesFiles to attach: absolute paths, or relative to the directory you run in.
refstringyesRef of the file field, or of the button that opens the file picker.
tabIdintegeryesTab id from browser_open_tab or browser_list_tabs.

No output schema declared.

No examples provided.

Install

How do I install the Tabhand MCP server?

Tabhand runs locally as an npm package, launched with npx -y tabhand 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 · tabhand

# add to Claude Code
claude mcp add dev-tabhand-tabhand -- npx -y tabhand mcp
Common questions

What is the Tabhand MCP server?

Tabhand is an MCP server listed in the public MCP registry as dev.tabhand/tabhand. Let your coding agents use your real, signed-in Chrome, in background tabs that never steal focus. This page covers its npm package (tabhand).

Is the Tabhand MCP server safe to use?

Tabhand scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. 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.

What tools does the Tabhand MCP server expose?

Tabhand exposes 13 tools: browser_open_tab, browser_list_profiles, browser_navigate, browser_snapshot, browser_click, and 8 more. Their descriptions and schemas cost roughly 1,159 tokens of context every time the server is loaded.

Is the Tabhand MCP server still maintained?

Tabhand is still listed as active in the MCP registry. We last reached this channel on 22 November 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 Tabhand MCP server under?

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

What did VerifyMCP test on the Tabhand MCP server?

VerifyMCP ran 16 checks on Tabhand, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.