← JsHookMcp

JsHookMcp 0.3.5

npm · @jshookmcp/jshook · current release

8
Tools
43
Resources
2
Templates
2
Prompts

Observation

Observed 2026-08-14T08:07:54.239Z using mcpSecurity-inventory. Status: succeeded. Negotiated protocol: 2025-06-18.

Server capabilities
{
  "tools": {
    "listChanged": true
  },
  "logging": {},
  "completions": {},
  "prompts": {
    "listChanged": true
  },
  "resources": {
    "listChanged": true
  }
}

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

Resource templates 2

Prompts 2

Let’s talk about MCP security.

Share your details and our security team will contact you.