JS Reverse MCP

io.github.YuanHuakkPublished by GitHub account YuanHuakkv3.0.0Updated Oct 24, 2026

MCP server for JavaScript reverse engineering and browser debugging.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

A local MCP server for JavaScript reverse engineering and browser debugging, letting an assistant work on JS analysis and debug sessions.

What you can do
The manifest lists no tools, so capabilities come from the registry description only. It is positioned for JavaScript reverse engineering, meaning examining and understanding JavaScript code. It also covers browser debugging, so an assistant can be involved in debugging work in a browser context.
When to use it
Worth considering when you need an assistant to help analyze JavaScript or debug behavior in a browser during reverse-engineering work. It is a desktop-only local tool, so it suits individual developer machines rather than hosted or web environments. It is not a general-purpose server for other tasks.},
Requirements
Runs as a local process over stdio, installed from the npm package, so a Node.js runtime is needed. It is desktop-only and not available as a web executable. No authentication, environment variables or headers are declared.

Installation

In SourceWeft

  1. Open JS Reverse MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v3.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.