updated 2026-11-10 04:07 UTC

JS Reverse MCP

Repository

AI Agent-first JS 逆向 MCP Server：有头 Chrome 调试、断点、网络/WebSocket 分析、Patchright 反检测，可选 CloakBrowser。

MCP Servers TypeScript Listed Apache-2.0

Is JS Reverse MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.6 / 10
Provenance None
Signed commits 0%
Last push 68d ago
Advisories None known
Compare JS Reverse MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: JS Reverse MCP scores 54.0/100 (Grade C), ranked #881 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.6/10; recent commits are unsigned; no published advisory affects its latest release (js-reverse-mcp); last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How JS Reverse MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships JS Reverse MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Unsigned

    github.com/zhizhuodemao/js-reverse-mcp, Apache-2.0, last pushed 2026-09-03. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.6/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 3
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • npm js-reverse-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: js-reverse-mcp 4.0.5. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-01 OSSF Scorecard: 5.2/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues JS Reverse MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How JS Reverse MCP compares in MCP Servers

  1. #485 Plumb MCP 54.1 +0.1
  2. #486 A2asearch MCP 54.0 ±0
  3. #487 JS Reverse MCP 54.0 this agent
  4. #488 RPG Maker MV Ultimate MCP 54.0 ±0
  5. #489 Tomyud1 Godot MCP 54.0 ±0

Bars show each HVTrust score; the tick marks JS Reverse MCP’s 54.0.

Where the 54.0 comes from

HVTrust dimensions vs the MCP Servers average

54.0 / 100 · 100.0% confidence

JS Reverse MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.8 / 25
5.0 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
7.5 / 20
4.7 below avg 12.2
AdoptionLog-scaled stars · package downloads
12.5 / 20
4.9 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-28
Rank Moved
Rank dropped 40 spots (#828 → #868)
2026-10-27
Rank Moved
Rank rose 36 spots (#864 → #828)
2026-10-15
Rank Moved
Rank dropped 11 spots (#805 → #816)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 68 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
48.7
Activity sub-score · out of 100
#487
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 68 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
3.1k
Forks
399
Last Push
2026-09-03
68 days ago
Commits (4 wk)
0
Downloads (7d)
1,274
npm
HN mentions (30d)
—
Open Issues
4
Rank Change
▲1
was #882

Analysis

Activity Inputs

48.7 / 100
StarsRepository reach
20.9 / 30
FreshnessLast push recency
15.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.1 / 20

Common questions about JS Reverse MCP

Public trust evidence for JS Reverse MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does JS Reverse MCP publish package provenance?
No published build provenance is currently detected for JS Reverse MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does JS Reverse MCP have an OpenSSF Scorecard?
JS Reverse MCP has an OpenSSF Scorecard score of 4.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is JS Reverse MCP actively maintained?
Slowing down. Last push was 68 days ago — keep an eye on whether activity resumes.
What license does JS Reverse MCP use?
JS Reverse MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are JS Reverse MCP's commits signed?
0% of the last 100 commits to JS Reverse MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
JS Reverse MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to JS Reverse MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain JS Reverse MCP?

For maintainers

HVTrust scores JS Reverse MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 29HVTrust 3Score 2Grade 2Scorecard 1Delisted 1Listed 1MCP 1
2026-10-28
Rank Moved
Rank dropped 40 spots (#828 → #868)
2026-10-27
Rank Moved
Rank rose 36 spots (#864 → #828)
2026-10-15
Rank Moved
Rank dropped 11 spots (#805 → #816)
2026-10-13
Rank Moved
Rank dropped 10 spots (#794 → #804)
2026-10-12
Rank Moved
Rank dropped 13 spots (#781 → #794)
2026-10-09
Rank Moved
Rank dropped 15 spots (#764 → #779)
2026-10-03
Rank Moved
Rank dropped 64 spots (#690 → #754)
2026-10-03
Activity Score Changed
Activity score down 6pts (60 → 54)
2026-09-30
Rank Moved
Rank dropped 19 spots (#666 → #685)
2026-09-24
Rank Moved
Rank dropped 48 spots (#609 → #657)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 180 spots (#789 → #609)
2026-09-23
HVTrust Changed
HVTrust up 31.5pts (29.0 → 60.5)
2026-09-22
Newly Listed
First tracked at rank #789
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank dropped 33 spots (#556 → #589)
2026-09-12
Rank Moved
Rank dropped 13 spots (#523 → #536)
2026-09-11
Rank Moved
Rank dropped 10 spots (#513 → #523)
2026-09-10
Rank Moved
Rank dropped 29 spots (#484 → #513)
2026-09-07
Rank Moved
Rank dropped 34 spots (#442 → #476)
2026-09-06
Rank Moved
Rank dropped 10 spots (#432 → #442)
2026-09-05
Rank Moved
Rank dropped 65 spots (#367 → #432)
2026-09-04
Rank Moved
Rank dropped 15 spots (#352 → #367)
2026-09-01
Scorecard Added
OSSF Scorecard: 5.2/10
2026-09-01
Grade Changed
Trust grade D → C
2026-09-01
Rank Moved
Rank rose 619 spots (#967 → #348)
2026-09-01
HVTrust Changed
HVTrust up 26.5pts (36.4 → 62.9)
2026-08-31
Rank Moved
Rank dropped 32 spots (#935 → #967)
2026-08-30
Rank Moved
Rank dropped 48 spots (#887 → #935)
2026-08-29
Rank Moved
Rank dropped 47 spots (#840 → #887)
2026-08-28
Rank Moved
Rank dropped 25 spots (#815 → #840)
2026-08-27
Rank Moved
Rank dropped 24 spots (#791 → #815)
2026-08-26
Rank Moved
Rank dropped 102 spots (#689 → #791)
2026-08-25
Rank Moved
Rank rose 12 spots (#701 → #689)
2026-08-20
Rank Moved
Rank rose 45 spots (#749 → #704)
2026-08-20
HVTrust Changed
HVTrust up 3.4pts (32.4 → 35.8)
2026-08-20
Activity Score Changed
Activity score up 13pts (52 → 66)
2026-08-16
Rank Moved
Rank dropped 13 spots (#734 → #747)
2026-08-15
Rank Moved
Rank dropped 11 spots (#723 → #734)
GitHub → npm: js-reverse-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/js-reverse-mcp.svg)](https://hvtracker.net/agents/js-reverse-mcp)
HTML:
<a href="https://hvtracker.net/agents/js-reverse-mcp"><img src="https://hvtracker.net/badge/js-reverse-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON