JsHookMcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JSHOOK_BASE_PROFILE | No | Base profile for tool discovery tiers: search, workflow, or full | search |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {}
} |
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| extensions | {
"io.modelcontextprotocol/skills": {
"directoryRead": true
}
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_toolsA | Search 736 tools across 36 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 (85) | memory (75) | native-emulator (57) | binary-instrument (46) | network (38) | process (29) | tls-inspector (29) | adb-bridge (26) | core (25) | debugger (21) | exploit-dev (21) | v8-inspector (21) | protocol-analysis (20) | platform (18) | maintenance (17) | streaming (17) | wasm (17) | dart-inspector (16) | syscall-hook (15) | instrumentation (13) | workflow (13) | coordination (12) | canvas (11) | proxy (11) | trace (10) | webgpu (10) | cross-domain (8) | mojo-ipc (8) | transform (8) | extension-registry (7) | graphql (7) | sourcemap (7) | native-bridge (6) | encoding (5) | tasks (4) | session (3). 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. |
| route_toolA | 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. |
| describe_toolA | Get detailed information about a specific tool, including its input schema. Use this to see the exact parameters a tool expects before calling it. |
| activate_toolsA | 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; use activate_domain when you need every tool in a domain. Activated tools appear in the tool list immediately. If tools do not appear after activation, use call_tool to invoke them directly. |
| deactivate_toolsA | Remove previously activated tools to free context. Only affects dynamically activated tools (added via activate_tools, activate_domain, or extension activation), not base profile tools. |
| activate_domainA | Register every tool in a single domain at once. Use this when a task needs a whole capability area; prefer search_tools or activate_tools when you only need a few specific tools, because activating a domain costs far more context. Domains: . Activated tools appear in the tool list immediately; if your client does not refresh its tool list, invoke them with call_tool. Activation draws on the session context budget: when the budget is full, least-recently-used tools are evicted to make room, and the response reports what was activated and what was evicted. Pass precheck: true to preview wouldActivate / wouldEvict without changing anything. Activated tools auto-deactivate after ttlMinutes (default 30; pass 0 for no expiry). Use reload_extensions first to include external plugin/workflow domains. |
| call_toolA | 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. |
| coverage_reportA | Report 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_anti_debug | Runbook and scripts for defeating debugger protections and traps. |
| hook_generation_guide | Instructions on how to deploy and use hooks generated by the hook builder. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| evidence_graph_json | Serializable snapshot of the current reverse evidence graph. |
| evidence_graph_markdown | Markdown report for the current reverse evidence graph. |
| instrumentation_sessions | Expanded snapshots for all active instrumentation sessions. |
| search_engine_status | Current status of the multi-signal tool search engine. |
| token_budget_stats | Current token budget usage, top-10 tool distribution, and optimization suggestions. |
| activation_state | Currently activated tools, per-domain TTL remaining, and auto-pruner predictions. |
| tool_coverage | Called vs uncalled tools in the current runtime, with last-call metadata. |
| cache_stats | Global cache entry count, total size, and per-cache-instance hit rates. |
| browser_tabs | List of currently open browser tabs with URL, title, and tabIndex. |
| Domain: adb-bridge | 0 tools |
| Domain: core | 0 tools |
| Domain: binary-instrument | 0 tools |
| Domain: browser | 0 tools |
| Domain: canvas | 0 tools |
| Domain: coordination | 0 tools |
| Domain: cross-domain | 0 tools |
| Domain: dart-inspector | 0 tools |
| Domain: debugger | 0 tools |
| Domain: encoding | 0 tools |
| Domain: exploit-dev | 0 tools |
| Domain: extension-registry | 0 tools |
| Domain: graphql | 0 tools |
| Domain: instrumentation | 0 tools |
| Domain: maintenance | 0 tools |
| Domain: memory | 0 tools |
| Domain: mojo-ipc | 0 tools |
| Domain: native-bridge | 0 tools |
| Domain: native-emulator | 0 tools |
| Domain: network | 0 tools |
| Domain: platform | 0 tools |
| Domain: process | 0 tools |
| Domain: protocol-analysis | 0 tools |
| Domain: proxy | 0 tools |
| Domain: session | 0 tools |
| Domain: sourcemap | 0 tools |
| Domain: streaming | 0 tools |
| Domain: syscall-hook | 0 tools |
| Domain: tasks | 0 tools |
| Domain: tls-inspector | 0 tools |
| Domain: trace | 0 tools |
| Domain: transform | 0 tools |
| Domain: v8-inspector | 0 tools |
| Domain: wasm | 0 tools |
| Domain: webgpu | 0 tools |
| Domain: workflow | 0 tools |
| best-practices | 配置与日常使用的最佳实践:避免常见坑、性能与安全建议 |
| configuration | 配置参考:环境变量、profile、阈值等全部配置项说明 |
| getting-started | 快速开始:五分钟接入 jshookmcp——安装、MCP 客户端配置与首次调用 |
| telemetry | 遥测与可观测性:默认开启的指标、OTLP 导出、search.query span 与 /health |
| tool-selection | 工具路由与生命周期:36 域命名空间、按需激活、profile 分层下如何选择与调度 jshookmcp 工具 |
| troubleshooting | Troubleshooting:安装、连接、工具调用失败的诊断步骤与修复方法 |
TDQS
Scored across 8 tools
Most tools have clearly distinct roles: discovery (search_tools, route_tool, describe_tool), activation lifecycle (activate_tools, activate_domain, deactivate_tools), execution (call_tool), and reporting (coverage_report). The only mild overlaps are search_tools vs route_tool (both discovery) and activate_tools vs activate_domain, but the descriptions explicitly differentiate them by intent and cost.
Nearly all names follow a consistent verb_noun snake_case pattern (search_tools, activate_tools, call_tool, describe_tool). The main deviation is coverage_report, which is a noun phrase rather than an action, but it remains readable and predictable.
Eight tools is well-scoped for a meta-server that manages 736 tools across 36 domains. Each tool covers a distinct phase of the discovery-activation-execution lifecycle and none feels redundant or filler.
The surface covers discovery, activation, deactivation, execution, and coverage reporting, but there is no dedicated tool to list currently active tools or enumerate domains, and activate_domain's domain list is empty. The descriptions also reference reload_extensions, which is not present in the tool set, creating a dead end for plugin/workflow domain loading.