JsHookMcp
Related Servers
Alternatives to JsHookMcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceStandardizes front-end JavaScript reverse engineering workflows by providing tools for browser observation, runtime sampling, hooking, debugging, network analysis, and local environment reproduction.74Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA unified MCP server for JavaScript reverse engineering that provides full hook, breakpoints, script debugging, and browser automation with CDP anti-detection, supporting both ATTACH and LAUNCH modes.2Apache 2.0
- FlicenseAqualityDmaintenanceChrome browser JS reverse engineering MCP tool for CTF/Web security, enabling dynamic analysis and restoration of login encryption logic.3120-
- AlicenseNot gradedqualityCmaintenanceEnables dynamic reverse engineering and debugging of WeChat MiniProgram JavaScript through the Chrome DevTools Protocol, letting AI agents enumerate and search scripts, set breakpoints, step through paused frames, trace function calls, hook miniprogram APIs such as wx.request, and capture network requests to analyze encryption, signing, and anti-scraping logic. It also works against Chrome, Node.js, and Electron runtimes, with tools for extracting code bundles and page business logic.31 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI coding assistants to debug and analyze JavaScript code in web pages through breakpoint debugging, function hooking, network analysis, and runtime inspection of scripts including minified code.241,064 npm3,072Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to read and modify the state of web apps (Vue, React, Svelte, Pinia, router) through MCP, acting as headless devtools.2,523 npm127MIT
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.