io.github.Tampermonkey/tampermonkey-mcp
NPM · TAMPERMONKEY-MCP · SCANNED SEP 20
MCP server to manage your Tampermonkey scripts
Available components
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
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 69 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).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 Management97
- Stability observed for 29 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "tampermonkey.delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 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
How do I install the io.github.Tampermonkey/tampermonkey-mcp server?
io.github.Tampermonkey/tampermonkey-mcp runs locally as an npm package, launched with npx -y tampermonkey-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 · tampermonkey-mcp
claude mcp add tampermonkey-tampermonkey-mcp -- npx -y tampermonkey-mcp
{
"mcpServers": {
"tampermonkey-tampermonkey-mcp": {
"command": "npx",
"args": [
"-y",
"tampermonkey-mcp"
]
}
}
} {
"servers": {
"tampermonkey-tampermonkey-mcp": {
"command": "npx",
"args": [
"-y",
"tampermonkey-mcp"
]
}
}
} codex mcp add tampermonkey-tampermonkey-mcp -- npx -y tampermonkey-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tampermonkey-tampermonkey-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tampermonkey-mcp"
],
"enabled": true
}
}
} openclaw mcp add tampermonkey-tampermonkey-mcp --command npx --arg -y --arg tampermonkey-mcp
mcp_servers:
tampermonkey-tampermonkey-mcp:
command: "npx"
args: ["-y", "tampermonkey-mcp"] {
"McpServers": {
"tampermonkey-tampermonkey-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tampermonkey-mcp"
]
}
}
} assistant mcp add tampermonkey-tampermonkey-mcp -t stdio -c npx -a -y tampermonkey-mcp
{
"mcpServers": {
"tampermonkey-tampermonkey-mcp": {
"command": "npx",
"args": [
"-y",
"tampermonkey-mcp"
]
}
}
} 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.
- 19 Sept 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 Sept 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.
- 16 Sept 26 −3
- Stability: pass → 0.83 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 13 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 11 Sept 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.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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/tampermonkey-mcp@0.0.4
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 99 packages
| Packages resolved | 99 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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)
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The 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
| Name | Type | Req | Description |
|---|---|---|---|
| ifNotModifiedSince | number | – | Unix timestamp - only return if script was modified after this time |
| path | string | yes | The 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)
| Name | Type | Req | Description |
|---|---|---|---|
| includePattern | array | – | Filter scripts by include URL pattern |
| pattern | string | – | Filter 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)
| Name | Type | Req | Description |
|---|---|---|---|
| lastModified | number | – | Unix timestamp for optimistic locking |
| path | string | yes | The script path (e.g., "<script-uuid>/source") |
| value | string | yes | The 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)
| Name | Type | Req | Description |
|---|---|---|---|
| lastModified | number | – | Unix timestamp for optimistic locking |
| value | string | yes | The script source code content |
No output schema declared.
No examples provided.
What is the io.github.Tampermonkey/tampermonkey-mcp server?
io.github.Tampermonkey/tampermonkey-mcp is listed in the public MCP registry as io.github.Tampermonkey/tampermonkey-mcp. MCP server to manage your Tampermonkey scripts. This page covers its npm package (tampermonkey-mcp).
Is the io.github.Tampermonkey/tampermonkey-mcp server safe to use?
io.github.Tampermonkey/tampermonkey-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.Tampermonkey/tampermonkey-mcp server expose?
io.github.Tampermonkey/tampermonkey-mcp exposes 6 tools: tampermonkey.get-connection-code, tampermonkey.list, tampermonkey.get, tampermonkey.patch, tampermonkey.put, tampermonkey.delete. Their descriptions and schemas cost roughly 948 tokens of context every time the server is loaded.
Is the io.github.Tampermonkey/tampermonkey-mcp server still maintained?
io.github.Tampermonkey/tampermonkey-mcp 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.Tampermonkey/tampermonkey-mcp server under?
io.github.Tampermonkey/tampermonkey-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.