# Tabhand (npm · tabhand)

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

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- npm · `tabhand`: 85/100 (this document), [markdown](https://verifymcp.io/servers/dev-tabhand-tabhand/tabhand.md), [page](https://verifymcp.io/servers/dev-tabhand-tabhand/tabhand)

## Channel facts

- Registry: `npm`
- Package: `tabhand`
- Version: `0.10.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add dev-tabhand-tabhand -- npx -y tabhand mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-tabhand-tabhand": {
      "command": "npx",
      "args": [
        "-y",
        "tabhand",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-tabhand-tabhand": {
      "command": "npx",
      "args": [
        "-y",
        "tabhand",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-tabhand-tabhand -- npx -y tabhand mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-tabhand-tabhand": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tabhand",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-tabhand-tabhand --command npx --arg -y --arg tabhand --arg mcp
```

### Hermes

```yaml
mcp_servers:
  dev-tabhand-tabhand:
    command: "npx"
    args: ["-y", "tabhand", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-tabhand-tabhand": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tabhand",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-tabhand-tabhand -t stdio -c npx -a -y tabhand mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-tabhand-tabhand": {
      "command": "npx",
      "args": [
        "-y",
        "tabhand",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 85, +1)

- [security] Stability: 0.97 → pass

### 2026-11-19 (score 84, +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.

### 2026-11-17 (score 83, +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.

### 2026-11-15 (score 82, +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.

### 2026-11-13 (score 81, +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.

### 2026-11-10 (score 80, +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.

### 2026-11-08 (score 79, +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.

### 2026-11-06 (score 78, +1)

- [functional regression] Security disclosure: unverified → fail

## MCP tools (13)

### `browser_open_tab` (~141 tokens)

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.

Input parameters:

- `profile` (string): 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.
- `url` (string): Page to load, e.g. https://example.com. Omit for a blank tab.

### `browser_list_profiles` (~53 tokens)

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.

### `browser_navigate` (~55 tokens)

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

Input parameters:

- `tabId` (integer, required): Tab id from browser_open_tab or browser_list_tabs.
- `url` (string, required): Page to load.

### `browser_snapshot` (~91 tokens)

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.

Input parameters:

- `tabId` (integer, required): Tab id from browser_open_tab or browser_list_tabs.

### `browser_click` (~141 tokens)

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.

Input parameters:

- `ref` (string): Element ref from browser_snapshot, e.g. e123.
- `tabId` (integer, required): Tab id from browser_open_tab or browser_list_tabs.
- `text` (string): 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.

### `browser_type` (~131 tokens)

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.

Input parameters:

- `clear` (boolean): Replace the field's current text.
- `ref` (string): Field ref from browser_snapshot, e.g. e123.
- `submit` (boolean): Press Enter after typing.
- `tabId` (integer, required): Tab id from browser_open_tab or browser_list_tabs.
- `text` (string, required): Text to type.

### `browser_press_key` (~98 tokens)

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.

Input parameters:

- `key` (string, required): Key or combination, e.g. Enter or Shift+Tab.
- `tabId` (integer, required): Tab id from browser_open_tab or browser_list_tabs.

### `browser_handle_dialog` (~107 tokens)

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.

Input parameters:

- `accept` (boolean, required): true for OK, false for Cancel.
- `tabId` (integer, required): Tab id from browser_open_tab or browser_list_tabs.
- `text` (string): What to enter, for a prompt dialog.

### `browser_scroll` (~74 tokens)

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

Input parameters:

- `amount` (number): Pixels to scroll. Defaults to 600.
- `direction` (string): Defaults to down.
- `tabId` (integer, required): Tab id from browser_open_tab or browser_list_tabs.

### `browser_screenshot` (~87 tokens)

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.

Input parameters:

- `fullPage` (boolean): Capture the whole page instead of the visible area (capped at 8000 px tall).
- `tabId` (integer, required): Tab id from browser_open_tab or browser_list_tabs.

### `browser_list_tabs` (~30 tokens)

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

### `browser_upload_file` (~110 tokens)

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).

Input parameters:

- `paths` (array, required): Files to attach: absolute paths, or relative to the directory you run in.
- `ref` (string, required): Ref of the file field, or of the button that opens the file picker.
- `tabId` (integer, required): Tab id from browser_open_tab or browser_list_tabs.

### `browser_close_tab` (~41 tokens)

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

Input parameters:

- `tabId` (integer, required): Tab id from browser_open_tab or browser_list_tabs.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-tabhand-tabhand/tabhand#diagnostics

## Score history

- 2026-11-22: 85
- 2026-11-21: 85
- 2026-11-20: 84
- 2026-11-19: 84
- 2026-11-18: 83
- 2026-11-17: 83
- 2026-11-16: 82
- 2026-11-15: 82
- 2026-11-14: 81
- 2026-11-13: 81
- 2026-11-12: 80
- 2026-11-11: 80
- 2026-11-10: 80
- 2026-11-09: 79
- 2026-11-08: 79
- 2026-11-07: 78
- 2026-11-06: 78
- 2026-11-05: 77
- 2026-11-04: 77
- 2026-11-03: 76
- 2026-11-02: 76
- 2026-11-01: 75
- 2026-10-31: 75
- 2026-10-30: 74
- 2026-10-29: 74
- 2026-10-28: 73
- 2026-10-27: 73
- 2026-10-26: 73
- 2026-10-25: 72
- 2026-10-24: 72

## 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.

## Links

- npm package: https://www.npmjs.com/package/tabhand
- Socket report: https://socket.dev/npm/package/tabhand
- Repository: https://github.com/tabhand/tabhand
- Website: https://tabhand.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-tabhand-tabhand/tabhand.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-tabhand-tabhand/tabhand/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-tabhand-tabhand/tabhand.json
- HTML version of this page: https://verifymcp.io/servers/dev-tabhand-tabhand/tabhand
