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.

Tab Hammer

NPM · TAB-HAMMER-MCP

List, group, move, focus, open, and close browser tabs through the Tab Hammer extension.

Available components

+3 this week 85 Trust /100

Last scanned (18 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 & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to BoltCreative/tab-hammer). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 439 tokens (~54/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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.

  • 22 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 21 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 14 Nov 26 −1
    • Malware scan: pass → unverified ▼ security
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: BoltCreative/tab-hammer security
    • Stability: unverified → 0.27 ▲ functional
    • Package version: 0.1.0 → 0.1.1 functional
  • 7 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 6 Nov 26 52

    First indexed and scored.

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/tab-hammer-mcp@0.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo BoltCreative/tab-hammer
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/BoltCreative/tab-hammer/.github/workflows/release.yml@refs/heads/main
Rekor log index 3888067298
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8e073bd02323683012ceb8cfefda1a25b0ef4f0e3137c108cdb58b47e5f939778ece920f055fc2880bcad8bd1c7f6bb01e98e149acc7497f4d37aeadd

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 · 8 exposed · ~439 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
close_tabs ~38

Close tabs. They can be reopened from Chrome history, but not by this tool.

NameTypeReqDescription
tabIdsarrayyesTab IDs from list_tabs

No output schema declared.

No examples provided.

focus_tab ~33

Bring a tab to the front: select it in its window and focus that window.

NameTypeReqDescription
tabIdintegeryes–

No output schema declared.

No examples provided.

group_tabs ~82

Put tabs in a tab group: an existing one (groupId) or a new one, optionally titled and colored. Tabs from other windows move into the group's window. Returns the groupId.

NameTypeReqDescription
colorstring––
groupIdinteger––
tabIdsarrayyesTab IDs from list_tabs
titlestring––

No output schema declared.

No examples provided.

list_tabs ~72

Every open Chrome window with its tab groups and tabs, in tab-strip order (Tab Hammer's own window excluded). Gives the IDs the other tools take, plus each tab's title, URL, and when the user last viewed it. IDs change when Chrome restarts, so list again rather than reusing old ones.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

move_tabs ~82

Move tabs, in the given order, into a window (no windowId: a new window). `index` is the position in that window; omit it to append. Moving a tab out of its group ungroups it.

NameTypeReqDescription
indexinteger––
tabIdsarrayyesTab IDs from list_tabs
windowIdinteger––

No output schema declared.

No examples provided.

open_tabs ~43

Open URLs as new tabs, in an existing window or (no windowId) a new window.

NameTypeReqDescription
urlsarrayyes–
windowIdinteger––

No output schema declared.

No examples provided.

ungroup_tabs ~34

Take tabs out of their groups (the tabs stay open).

NameTypeReqDescription
tabIdsarrayyesTab IDs from list_tabs

No output schema declared.

No examples provided.

update_group ~55

Rename, recolor, or collapse/expand a tab group in Chrome's tab strip.

NameTypeReqDescription
collapsedboolean––
colorstring––
groupIdintegeryes–
titlestring––

No output schema declared.

No examples provided.

Install

How do I install the Tab Hammer MCP server?

Tab Hammer runs locally as an npm package, launched with npx -y tab-hammer-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 · tab-hammer-mcp

# add to Claude Code
claude mcp add boltcreative-tab-hammer -- npx -y tab-hammer-mcp
Common questions

What is the Tab Hammer MCP server?

Tab Hammer is an MCP server listed in the public MCP registry as io.github.BoltCreative/tab-hammer. List, group, move, focus, open, and close browser tabs through the Tab Hammer extension. This page covers its npm package (tab-hammer-mcp).

Is the Tab Hammer MCP server safe to use?

Tab Hammer 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. Its build provenance is signed and verified. 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 Tab Hammer MCP server expose?

Tab Hammer exposes 8 tools: list_tabs, focus_tab, open_tabs, move_tabs, group_tabs, and 3 more. Their descriptions and schemas cost roughly 439 tokens of context every time the server is loaded.

Is the Tab Hammer MCP server still maintained?

Tab Hammer 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 Tab Hammer MCP server under?

Tab Hammer 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 Tab Hammer MCP server?

VerifyMCP ran 16 checks on Tab Hammer, 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.