noone-hub/jsreverser-mcp

English README

An MCP service that standardizes the frontend JavaScript reverse process.
The goal is not just page debugging, but to weave page observation, runtime sampling, local reproduction, environment supplementation, and evidence accumulation into a reusable workflow.

Core Methodology

This project defaults to the following methodology:

• Observe-first
• Hook-preferred
• Breakpoint-last
• Rebuild-oriented
• Evidence-first
• Pure-extraction-after-pass

This means:

1. First, confirm the sources of requests, scripts, functions, and dependencies in your browser
2. Then minimize hook sampling
3. Then export the local rebuild
4. Then, add the environment item by item in the Node
5. Every step is settled as a task artifact, not just in conversation

Already settled links

The following parameter links are publicly indexed and can serve as reuse entries within the warehouse:

• JD.com h5st parameters

• Index: scripts/cases/README.md

• Case：scripts/cases/jd-h5st-pure-node.mjs

• Certain hand falcon risk control parameters

• Index: scripts/cases/README.md

• Case：scripts/cases/ks-hxfalcon-pure-node.mjs

• Certain sound a-bogus parameters

• Index: scripts/cases/README.md

• Case：scripts/cases/douyin-a-bogus-pure-node.mjs

Explanation:

• The README homepage only displays the parameter types and public entry points after desensitization
• True artifacts/tasks/ / is treated by default as a local private task directory
• Git only commits by default artifacts/tasks/_TEMPLATE/

Parameter Blueprint Library

The public parameter method has been deposited into docs/knowledge/parameter-blueprints/ to replace the old runnable case entry. How to view and contribute:

Contribution guidelines can be found in docs/guides/parameter-workflow-contribution.md.

The ability to support it

Page Observation and Script Positioning

First, answer “What scripts and target code are on the page?”

• list_scripts: List the scripts loaded on the current page, first establishing the script scope.
• get_script_source: View the specified script source code, suitable for further reading on the specific implementation.
• find_in_script: Locates strings, variable names, or feature fragments within a single script.
• search_in_scripts: Batch searches in the cache of collected scripts, suitable for narrowing down candidate scripts.

Hook and runtime sampling