JS Reverse MCP

io.github.YuanHuakkPublished by GitHub account YuanHuakkv2.5.0Updated Oct 24, 2026

MCP server for JavaScript reverse engineering and browser debugging.

VerifiedSTDIODesktop onlyBrowser Automation Developer Tools

Server details

Identifier: io.github.YuanHuakk/js-reverse-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account YuanHuakk for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.YuanHuakk%2Fjs-reverse-mcp.svg)](https://sourceweft.com/mcp/io.github.YuanHuakk%2Fjs-reverse-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server for JavaScript reverse engineering and browser debugging, letting an assistant work on deobfuscating and analyzing JavaScript.

What you can do: Supports JavaScript reverse engineering tasks such as analyzing and deobfuscating scripts, based on the registry description. Provides browser debugging capabilities so an assistant can inspect and troubleshoot JavaScript running in a browser. Runs as a local process on the user's machine over stdio. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it: Useful when you need an assistant to help reverse engineer, deobfuscate or debug JavaScript, especially in a browser context, and you are working on a desktop machine where a local process can be started.
Requirements: Runs as a local process on the user's machine over stdio, installed from the npm package @yuanhuakk/js-reverse-mcp, so a Node.js runtime and npm are needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.

Before you install

Reverse engineering and browser debugging can expose sensitive page content, credentials or session data to the assistant and the local process; review what is captured before sharing. No credentials, payments or write actions are declared, but the tool set is undocumented, so verify behavior before use.

Installation

In SourceWeft

Open JS Reverse MCP in the dashboard and add it to a workspace.
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

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

Version history

v2.5.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.