Is JS Reverse MCP safe to use?

JS Reverse MCP has an HVTrust score of 58.9/100 (Grade C), ranked #663 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for JS Reverse MCP?

JS Reverse MCP scores 58.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.8k GitHub stars and is categorized under MCP Servers.

JS Reverse MCP

zhizhuodemao/js-reverse-mcp

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

MCP Servers TypeScript Listed Apache-2.0

Is JS Reverse MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.8 / 10

Provenance None

Signed commits 0%

Last push 23d ago

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 58.9/100 (Grade C), ranked #663 of 1325 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.8/10; recent commits are unsigned; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How JS Reverse MCP compares in MCP Servers

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

Where the 58.9 comes from

HVTrust dimensions vs the MCP Servers average

58.9 / 100 · 100.0% confidence

JS Reverse MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

6.0 / 25

4.3 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.6 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

12.4 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

12.1 / 20

4.9 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.8/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.

Compare with another agent Get email alerts for JS Reverse MCP View MCP Servers Report missing data

60.5

Activity sub-score · out of 100

#367

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

2.8k

Forks

369

Last Push

2026-09-03

23 days ago

Commits (4 wk)

Downloads (7d)

714

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #663

Analysis

Activity Inputs

60.5 / 100

StarsRepository reach

20.7 / 30

FreshnessLast push recency

21.8 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

11.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.8 / 10

OpenSSF Scorecard · scanned Sep 16, 2026

Signed Commits

of last 100 commits verified

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 2

Common questions about JS Reverse MCP

JS Reverse MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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.8/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?

Maintained. Last push was 23 days ago.

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

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)

2026-08-10

Newly Listed

First tracked at rank #720

GitHub → npm: js-reverse-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON