MCP server intelligence profile

JsHookMcp MCP Server

The js hook toolkit that all you need

Local Onlyvmoranv
Awaiting current scanNpm · 0.3.5

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

1Distribution channel
8Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence

Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.

Install and connect

Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.

Install @jshookmcp/jshook from npm

Version 0.3.5 declares 1 executable entrypoint.

npm install --save-exact @jshookmcp/jshook@0.3.5
npx -y -p @jshookmcp/jshook@0.3.5 @jshookmcp/jshook
MCP client configuration example
{
  "mcpServers": {
    "@jshookmcp/jshook": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@jshookmcp/jshook@0.3.5",
        "@jshookmcp/jshook"
      ]
    }
  }
}

Identity

Canonical slugjshookmcp-fed8418aDeploymentLocal Only
Canonical packagenpm:@jshookmcp/jshookRepositoryvmoranv/jshookmcp
First publishedLatest release
Last security verificationClassification confidence90%
PublicationDraftOfficial distributionNot verified

Distributions

ChannelIdentifierCurrent versionVersionsSource
npm@jshookmcp/jshook0.3.523Repository

Current release

PackageVersionPublished / observedInventorySecurity scan
npm@jshookmcp/jshook0.3.5CurrentSep 5, 20268 toolsSucceeded · 43 resources · 2 promptsEvidence restricted
Enterprise protection

Continuously monitor this MCP for security risk

Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.

  • Independent exact-version security scans
  • Continuous release and vulnerability monitoring
  • Risk-change alerts with capability context
  • Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.

Current version evidence

No public current-version evidence is available yet.

Current protocol inventory

2025-06-18Negotiated protocol
jshookmcpServer-reported name
5Capability groups
Aug 14, 2026Observed

Tools 8

ToolCategoryAnnotationsRisk
activate_domainActivate all tools in a domain at once. Domains: . Use reload_extensions first to include external plugin/workflow domains.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain name to activate (e.g. \"debugger\", \"network\")"
    },
    "ttlMinutes": {
      "description": "Auto-deactivate after N minutes (default: 30, set 0 for no expiry)",
      "type": "number"
    }
  },
  "required": [
    "domain"
  ]
}
activate_toolsDynamically 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.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "names": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "string",
          "description": "JSON stringified array for MCP clients that serialize arrays as strings"
        }
      ],
      "description": "Array of tool names to activate (from search_tools results). Also accepts a JSON stringified array for clients that serialize arrays as strings."
    }
  },
  "required": [
    "names"
  ]
}
call_toolExecute 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.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "The tool name to execute (from search_tools or describe_tool results)"
    },
    "args": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "Arguments object to pass to the tool"
    },
    "parameters": {
      "type": "string",
      "description": "Alternative: JSON-serialized arguments string. Some MCP clients serialize the nested arguments as a single stringified-JSON field."
    },
    "arguments": {
      "type": "string",
      "description": "Another alternative: MCP clients that stringify the entire arguments wrapper. Carries the same nested {name, args/parameters} payload as a JSON string."
    }
  },
  "required": [
    "name"
  ]
}
coverage_reportReport which tools have been called in the current runtime and which known tools remain uncalled. Loads all domains first so the uncalled list reflects the full tool catalog, not just currently active tools.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {}
}
deactivate_toolsRemove previously activated tools to free context. Only affects tools added via activate_tools, not base profile tools.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "names": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "string",
          "description": "JSON stringified array"
        }
      ],
      "description": "Array of tool names to deactivate"
    }
  },
  "required": [
    "names"
  ]
}
describe_toolGet detailed information about a specific tool, including its input schema. Use this to see the exact parameters a tool expects before calling it.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Tool name to describe"
    }
  },
  "required": [
    "name"
  ]
}
route_toolOne-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.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "task": {
      "type": "string",
      "description": "Natural language description of the task you want to accomplish"
    },
    "context": {
      "type": "object",
      "properties": {
        "preferredDomain": {
          "type": "string",
          "description": "Domain preference (e.g., \"browser\", \"network\")"
        },
        "autoActivate": {
          "description": "Whether to auto-activate recommended tools (default: false)",
          "type": "boolean"
        },
        "maxRecommendations": {
          "description": "Maximum number of recommendations (default: 5)",
          "type": "number"
        }
      },
      "description": "Optional context hints for routing"
    }
  },
  "required": [
    "task"
  ]
}
search_toolsSearch 668 tools across 34 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: browser (76) | native-emulator (54) | binary-instrument (44) | network (41) | memory (34) | boringssl-inspector (28) | process (28) | adb-bridge (26) | core (25) | v8-inspector (22) | debugger (21) | exploit-dev (21) | protocol-analysis (20) | platform (18) | streaming (17) | wasm (17) | dart-inspector (16) | syscall-hook (15) | maintenance (14) | instrumentation (13) | coordination (12) | workflow (12) | proxy (11) | trace (10) | canvas (9) | webgpu (9) | cross-domain (8) | mojo-ipc (8) | extension-registry (7) | graphql (7) | sourcemap (7) | transform (7) | native-bridge (6) | encoding (5). Query tip: before searching, distill your intent into key concepts (action verb + target + domain). The engine combines token matching, fuzzy names, profile context, and optional static embeddings.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "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": {
      "description": "Max results to return (default: 10, max: 30)",
      "type": "number"
    },
    "auto_activate": {
      "description": "Auto-activate found tools so they are immediately callable. Set false to only search without activating (default: true)",
      "type": "boolean"
    }
  },
  "required": [
    "query"
  ]
}

Resources 43

  • activation_statejshook://activation/state

    Currently activated tools, per-domain TTL remaining, and auto-pruner predictions.

  • browser_tabsjshook://browser/tabs

    List of currently open browser tabs with URL, title, and tabIndex.

  • cache_statsjshook://cache/stats

    Global cache entry count, total size, and per-cache-instance hit rates.

  • Domain: adb-bridgejshook://domains/adb-bridge

    0 tools

  • Domain: binary-instrumentjshook://domains/binary-instrument

    0 tools

  • Domain: boringssl-inspectorjshook://domains/boringssl-inspector

    0 tools

  • Domain: browserjshook://domains/browser

    0 tools

  • Domain: canvasjshook://domains/canvas

    0 tools

  • Domain: coordinationjshook://domains/coordination

    0 tools

  • Domain: corejshook://domains/core

    0 tools

  • Domain: cross-domainjshook://domains/cross-domain

    0 tools

  • Domain: dart-inspectorjshook://domains/dart-inspector

    0 tools

  • Domain: debuggerjshook://domains/debugger

    0 tools

  • Domain: encodingjshook://domains/encoding

    0 tools

  • Domain: exploit-devjshook://domains/exploit-dev

    0 tools

  • Domain: extension-registryjshook://domains/extension-registry

    0 tools

  • Domain: graphqljshook://domains/graphql

    0 tools

  • Domain: instrumentationjshook://domains/instrumentation

    0 tools

  • Domain: maintenancejshook://domains/maintenance

    0 tools

  • Domain: memoryjshook://domains/memory

    0 tools

  • Domain: mojo-ipcjshook://domains/mojo-ipc

    0 tools

  • Domain: native-bridgejshook://domains/native-bridge

    0 tools

  • Domain: native-emulatorjshook://domains/native-emulator

    0 tools

  • Domain: networkjshook://domains/network

    0 tools

  • Domain: platformjshook://domains/platform

    0 tools

  • Domain: processjshook://domains/process

    0 tools

  • Domain: protocol-analysisjshook://domains/protocol-analysis

    0 tools

  • Domain: proxyjshook://domains/proxy

    0 tools

  • Domain: sourcemapjshook://domains/sourcemap

    0 tools

  • Domain: streamingjshook://domains/streaming

    0 tools

  • Domain: syscall-hookjshook://domains/syscall-hook

    0 tools

  • Domain: tracejshook://domains/trace

    0 tools

  • Domain: transformjshook://domains/transform

    0 tools

  • Domain: v8-inspectorjshook://domains/v8-inspector

    0 tools

  • Domain: wasmjshook://domains/wasm

    0 tools

  • Domain: webgpujshook://domains/webgpu

    0 tools

  • Domain: workflowjshook://domains/workflow

    0 tools

  • evidence_graph_jsonjshook://evidence/graph

    Serializable snapshot of the current reverse evidence graph.

  • evidence_graph_markdownjshook://evidence/graph.md

    Markdown report for the current reverse evidence graph.

  • instrumentation_sessionsjshook://instrumentation/sessions

    Expanded snapshots for all active instrumentation sessions.

  • search_engine_statusjshook://search/status

    Current status of the multi-signal tool search engine.

  • token_budget_statsjshook://token-budget/stats

    Current token budget usage, top-10 tool distribution, and optimization suggestions.

  • tool_coveragejshook://tools/coverage

    Called vs uncalled tools in the current runtime, with last-call metadata.

Resource templates 2

  • domain_status_templatejshook://domains/{domainName}

    Per-domain tool listing and activation state.

  • instrumentation_session_snapshotjshook://instrumentation/session/{sessionId}

    Expanded snapshot for a single instrumentation session.

Prompts 2

  • analyze_anti_debuganalyze_anti_debug

    Runbook and scripts for defeating debugger protections and traps.

  • hook_generation_guidehook_generation_guide

    Instructions on how to deploy and use hooks generated by the hook builder.

Remote endpoints

EndpointTransportAuthenticationHealthObserved
No verified remote endpoint is linked.

JsHookMcp MCP Server questions

How do I install JsHookMcp MCP Server?

Install the selected package version with: npm install --save-exact @jshookmcp/jshook@0.3.5

What tools does JsHookMcp MCP Server provide?

JsHookMcp MCP Server exposed 8 tools during independent protocol observation, including activate_domain, activate_tools, call_tool, coverage_report, deactivate_tools, describe_tool, route_tool, search_tools.

Is JsHookMcp MCP Server secure?

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

Explore related MCP server guides

Curated product and capability guides containing this catalog record.

Official vs Community MCP Servers

Let’s talk about MCP security.

Share your details and our security team will contact you.