io.github.vmoranv/jshookmcp
NPM · @JSHOOKMCP/JSHOOK · SCANNED SEP 20
MCP server for JavaScript analysis, security auditing, browser automation and hooks
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 Security38
- Malware check failed: a supply-chain vendor flagged a high-severity malware risk. See how to fix → Fail
- CVE check failed: a known high-severity CVE affects adm-zip 0.5.18, reached via camoufox-js > adm-zip. A fixed version is available. View diagnostics → Fail
- Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- Dependency health was assessed across the 400 of 469 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency48
- 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 (AGPL-3.0-only).Pass
- Actively maintained (last published 47 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 650 tokens (~65/item across 10 items; 7 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deactivate_tools" implies "remove" 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 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
How do I install the io.github.vmoranv/jshookmcp MCP server?
io.github.vmoranv/jshookmcp runs locally as an npm package, launched with npx -y @jshookmcp/jshook. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @jshookmcp/jshook
claude mcp add vmoranv-jshookmcp -- npx -y @jshookmcp/jshook
{
"mcpServers": {
"vmoranv-jshookmcp": {
"command": "npx",
"args": [
"-y",
"@jshookmcp/jshook"
]
}
}
} {
"servers": {
"vmoranv-jshookmcp": {
"command": "npx",
"args": [
"-y",
"@jshookmcp/jshook"
]
}
}
} codex mcp add vmoranv-jshookmcp -- npx -y @jshookmcp/jshook
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vmoranv-jshookmcp": {
"type": "local",
"command": [
"npx",
"-y",
"@jshookmcp/jshook"
],
"enabled": true
}
}
} openclaw mcp add vmoranv-jshookmcp --command npx --arg -y --arg @jshookmcp/jshook
mcp_servers:
vmoranv-jshookmcp:
command: "npx"
args: ["-y", "@jshookmcp/jshook"] {
"McpServers": {
"vmoranv-jshookmcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@jshookmcp/jshook"
]
}
}
} assistant mcp add vmoranv-jshookmcp -t stdio -c npx -a -y @jshookmcp/jshook
{
"mcpServers": {
"vmoranv-jshookmcp": {
"command": "npx",
"args": [
"-y",
"@jshookmcp/jshook"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- CVE-2026-77301 affects this package: high ▼ security
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
- GHSA-rgj7-g3m4-5g8c no longer affects this package ▲ security
- GHSA-f88m-g3jw-g9cj no longer affects this package ▲ security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
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/@jshookmcp/jshook@0.3.0
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 →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node scripts/postinstall.cjs |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-7q85-xj36-vmfc | CVE-2026-77301 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vwc7-r8mq-g2x9 | CVE-2026-76845 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N | no |
| GHSA-xcpc-8h2w-3j85 | CVE-2026-39244 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-7pqw-9j4j-h8q3 | CVE-2026-19693 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H | no |
| GHSA-jmr9-qjv8-65gv | CVE-2026-56876 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Deprecated | 1 |
| Stale | 111 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
activate_domain ~79
Activate all tools in a domain at once. Domains: . Use reload_extensions first to include external plugin/workflow domains.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to activate (e.g. "debugger", "network") |
| ttlMinutes | number | – | Auto-deactivate after N minutes (default: 30, set 0 for no expiry) |
No output schema declared.
No examples provided.
activate_tools ~100
Dynamically register specific tools by name, regardless of current base tier. Use after search_tools to enable exactly the tools you need. In search-tier sessions this is usually enough; you do not need boost_profile just to use a few exact tools. Activated tools appear in the tool list immediately. If tools do not appear after activation, use call_tool to invoke them directly.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Array of tool names to activate (from search_tools results) |
No output schema declared.
No examples provided.
call_tool ~79
Execute an already-active tool by name. Use this when activate_tools/activate_domain registered a tool but your client did not refresh its tool list. Does not auto-activate inactive tools.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | Arguments object to pass to the tool |
| name | string | yes | The tool name to execute (from search_tools or describe_tool results) |
No output schema declared.
No examples provided.
deactivate_tools ~42
Remove previously activated tools to free context. Only affects tools added via activate_tools, not base profile tools.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Array of tool names to deactivate |
No output schema declared.
No examples provided.
describe_tool ~46
Get detailed information about a specific tool, including its input schema. Use this to see the exact parameters a tool expects before calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Tool name to describe |
No output schema declared.
No examples provided.
route_tool ~87
One-stop tool router: accepts a natural language task description, returns recommended tools and next actions. Automatically detects workflow patterns, recommends activation order, and provides example arguments. Use this instead of search_tools when you want guided tool discovery with actionable next steps.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | Optional context hints for routing |
| task | string | yes | Natural language description of the task you want to accomplish |
No output schema declared.
No examples provided.
search_tools ~173
Search 0 tools across 0 capability domains. This includes built-in tools plus any loaded plugin/workflow tools (0 currently loaded). In search-tier sessions, call this before assuming a capability is unavailable. Use activate_tools for exact matches, activate_domain for an entire domain. Domains: . Query tip: before searching, distill your intent into key concepts (action verb + target + domain). Pass distilled keywords, not full sentences — the search engine works on token matching, not semantic understanding.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Before calling, distill your intent into 2-5 key concepts: what action, on what target, in which domain. Pass only those distilled keywords — not the original user request. |
| top_k | number | – | Max results to return (default: 10, max: 30) |
No output schema declared.
No examples provided.
What is the io.github.vmoranv/jshookmcp MCP server?
io.github.vmoranv/jshookmcp is an MCP server listed in the public MCP registry as io.github.vmoranv/jshookmcp. MCP server for JavaScript analysis, security auditing, browser automation and hooks. This page covers its npm package (@jshookmcp/jshook).
Is the io.github.vmoranv/jshookmcp MCP server safe to use?
io.github.vmoranv/jshookmcp scores 65 out of 100 on VerifyMCP. A supply-chain scanner flagged a possible malware risk on one channel of this server. We recorded 5 known advisories against it as of 20 September 2026. 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.vmoranv/jshookmcp MCP server expose?
io.github.vmoranv/jshookmcp exposes 7 tools: search_tools, route_tool, describe_tool, activate_tools, deactivate_tools, and 2 more. Their descriptions and schemas cost roughly 606 tokens of context every time the server is loaded.
Is the io.github.vmoranv/jshookmcp MCP server still maintained?
io.github.vmoranv/jshookmcp 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.vmoranv/jshookmcp MCP server under?
io.github.vmoranv/jshookmcp declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.