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

io.github.Tampermonkey/tampermonkey-mcp

NPM · TAMPERMONKEY-MCP · SCANNED AUG 3

MCP server to manage your Tampermonkey scripts

Available components

+23 this week 67 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (98 of 102), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (98 of 102), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 948 tokens (~158/item across 6 items; 6 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · tampermonkey-mcp

# add to Claude Code
claude mcp add tampermonkey-tampermonkey-mcp -- npx -y tampermonkey-mcp
# add to Codex CLI
codex mcp add tampermonkey-tampermonkey-mcp -- npx -y tampermonkey-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tampermonkey-tampermonkey-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tampermonkey-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tampermonkey-tampermonkey-mcp --command npx --arg -y --arg tampermonkey-mcp
# ~/.hermes/config.yaml
mcp_servers:
  tampermonkey-tampermonkey-mcp:
    command: "npx"
    args: ["-y", "tampermonkey-mcp"]
// mcp.json
{
  "mcpServers": {
    "tampermonkey-tampermonkey-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tampermonkey-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.

  • 3 Aug 26 +47
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Security disclosure: unverified → fail functional
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • Stability: unverified → 0.27 functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → good functional
    • Licence: MIT functional
  • 2 Aug 26 +1
    • Malware scan: unverified → pass security
    • Security disclosure: fail → unverified functional
    • Tool coverage: 100 → unverified functional
  • 31 Jul 26 −5
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −20
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 44

    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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 98 packages

98 packages in the resolved dependency tree · 97 deprecated · 29 stale.

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

MCP tools — 6 exposed · ~948 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.

Tool Tokens
tampermonkey.delete ~129

Delete a userscript by path. **Input:** - `path`: The script or resource path (<script-uuid>/source, <script-uuid>/storage or <script-uuid>/<external-resource-url>) **Output:** - `success`: true if script was deleted successfully - `error`: Error object if deletion failed (e.g., script not found)

NameTypeReqDescription
pathstringyesThe script or resource path (<script-uuid>/source, <script-uuid>/storage or <script-uuid>/<external-resource-url>)

No output schema declared.

No examples provided.

tampermonkey.get ~164

Get the content of a specific userscript. **Input:** - `path`: The script path (from list operation) - `ifNotModifiedSince` (optional): Unix timestamp - only return if script was modified after this time **Output:** - `value`: The script source code - `lastModified`: Unix timestamp of last modification - `error`: Error object if script not found or concurrent edit detected

NameTypeReqDescription
ifNotModifiedSincenumberUnix timestamp - only return if script was modified after this time
pathstringyesThe script or resource path (<script-uuid>/source, <script-uuid>/storage or <script-uuid>/<external-resource-url>

No output schema declared.

No examples provided.

tampermonkey.get-connection-code ~227

REQUIRED FIRST STEP: Get the connection code to connect Tampermonkey Editors to the MCP server. **How it works:** The MCP server creates a WebSocket server that waits for Tampermonkey Editors to connect. You must call this tool FIRST to start the WebSocket server and get a connection code. Then enter the code in the Tampermonkey Editors extension - it will connect TO the MCP server. **Steps:** 1. Call this tool to get the connection code 2. Open Tampermonkey Editors extension in your browser 3. Enter the code in the extension popup 4. The extension connects to the MCP server's WebSocket 5. After connection, you can use tampermonkey.list, tampermonkey.get, tampermonkey.patch, tampermonkey.put, tampermonkey.delete **Output:** - `code`: The connection code to enter in Tampermonkey Editors

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tampermonkey.list ~152

List all userscripts available in Tampermonkey. **Input:** - `pattern` (optional): Filter scripts by name pattern - `includePattern` (optional): Filter scripts by include URL pattern **Output:** Array of userscript metadata including: - `name`: Script name - `namespace`: Script namespace - `path`: Script path (used for get/patch operations) - `requires`: List of @require dependencies - `storage`: Storage path (if any)

NameTypeReqDescription
includePatternarrayFilter scripts by include URL pattern
patternstringFilter scripts by name pattern

No output schema declared.

No examples provided.

tampermonkey.patch ~146

Update the content of a userscript. **Input:** - `path`: The script or resource path (from list operation) - `value`: The new script content - `lastModified` (optional): Unix timestamp for optimistic locking **Output:** - `success`: true if patch was applied successfully - `error`: Error object if patch failed (e.g., concurrent edit conflict)

NameTypeReqDescription
lastModifiednumberUnix timestamp for optimistic locking
pathstringyesThe script path (e.g., "<script-uuid>/source")
valuestringyesThe new script content

No output schema declared.

No examples provided.

tampermonkey.put ~130

Create a new userscript. **Input:** - `value`: The script source code content - `lastModified` (optional): Unix timestamp for optimistic locking **Output:** - `success`: true if script was created successfully - `path/name`: The path and name of the new script - `error`: Error object if creation failed (e.g., script already exists, concurrent edit conflict)

NameTypeReqDescription
lastModifiednumberUnix timestamp for optimistic locking
valuestringyesThe script source code content

No output schema declared.

No examples provided.