JS Reverse MCP Server

by yuanhuakk Your server? Claim it

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.

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.

194 installs/wk local only

Qualityforge

by ninelegsdog

Evidence-first browser QA with read-only MCP server for AI agent debugging.

688 installs/wk local only

Safari DevTools MCP

by hayodev

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

61 installs/wk local only

MCP Server Browser

by bytedance

MCP server for browser use access

811 installs/wk local only

MCP Server Browserbase

by browserbase

MCP server for AI web browser automation using Browserbase and Stagehand

683 installs/wk local only

Debugai MCP

by 1shizaan

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

86 installs/wk local only

Glamour

by gratise

Browser-measured visual debugging and verification tools for coding agents.

40 installs/wk local only

TestMu AI (formerly LambdaTest)

by lambdatest

Agentic AI quality engineering: run, debug and triage tests on real browsers and devices

88 tools answering

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.