mcpbeat Sign in

JS Reverse MCP Server

local only

JS Reverse MCP runs on your own machine — the client starts it, so there is no endpoint to ping.

MCP server for JavaScript reverse engineering and browser debugging.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs / week
not published
Stars
on GitHub
Last commit
from GitHub
License
language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Alternatives to JS Reverse MCP

same job, measured the same way
JS Reverse MCP
by yuanhuakk

MCP server for JavaScript reverse engineering and browser debugging.

33 installs/wk local only
Jshookmcp
by vmoranv

MCP server for JavaScript analysis, security auditing, browser automation and hooks

561 installs/wk local only
Safari DevTools MCP
by hayodev

MCP server for Safari DevTools — browser debugging and automation for AI coding agents

29 installs/wk local only
MCP Server Browser
by bytedance

MCP server for browser use access

1 793 installs/wk local only
MCP Server Browserbase
by browserbase

MCP server for AI web browser automation using Browserbase and Stagehand

4 036 installs/wk local only
Debugai MCP
by 1shizaan

MCP server for DebugAI. Browser sign-in, auto client setup, no key pasting.

305 installs/wk local only
UI Debugger MCP
by developerz-ai

Autonomous UI debugging MCP server: an agent drives the browser/desktop, reports bugs + UX issues.

70 installs/wk local only
Chrome Debugger MCP
by bitepro

Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code

31 installs/wk local only

JS Reverse MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for JS Reverse MCP?
JS Reverse MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.
Is JS Reverse MCP still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.