Is Jshookmcp safe to use?

Jshookmcp has an HVTrust score of 82.7/100 (Grade A), ranked #135 of 1387 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Jshookmcp?

Jshookmcp scores 82.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.1k GitHub stars and is categorized under MCP Servers.

Jshookmcp

Repository

Website

A search-first, profile-aware reverse-engineering workspace for AI agents — 735 tools across 36 domains in one MCP server.

MCP Servers TypeScript Listed AGPL-3.0

Is Jshookmcp safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.5 / 10

Provenance Attested

Signed commits 20%

Last push yesterday

Advisories None known

Compare Jshookmcp

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Jshookmcp scores 82.7/100 (Grade A), ranked #135 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.5/10; 20% of recent commits are signed; no published advisory affects its latest release (@jshookmcp/jshook); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Jshookmcp 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.

Raise the OSSF Scorecard from 5.5 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Contributors 0 +5.5 → 88.2 A · #18 of 779
Sign every commit20% signed today +3.2 → 85.9 A · #27 of 779

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Jshookmcp 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.

Source Partly signed

github.com/vmoranv/jshookmcp, AGPL-3.0, last pushed 2026-11-10. 20% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.5/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection1
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 5

Branch-Protection 1

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 6
Published packages Linked and attested
- npm @jshookmcp/jshook Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: @jshookmcp/jshook 0.4.3. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

2026-10-10 Package provenance attestation detected
2026-08-30 OSSF Scorecard: 5.0/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 Jshookmcp’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 Jshookmcp compares in MCP Servers

Bars show each HVTrust score; the tick marks Jshookmcp’s 82.7.

Where the 82.7 comes from

HVTrust dimensions vs the MCP Servers average

82.7 / 100 · 100.0% confidence

Jshookmcp MCP Servers average (779 agents)

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

15.4 / 25

4.6 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

0.9 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.6 above avg 12.3

AdoptionLog-scaled stars · package downloads

12.1 / 20

4.5 above avg 7.6

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-11-10

Rank Moved

Rank rose 18 spots (#153 → #135)

2026-10-22

Grade Changed

Trust grade B → A

2026-10-22

Rank Moved

Rank rose 26 spots (#180 → #154)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent View MCP Servers Report missing data

82.3

Activity sub-score · out of 100

#57

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 A 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-09-29 2026-11-10

Activity & Reach

Stars

2.1k

Forks

465

Last Push

2026-11-10

yesterday

Commits (4 wk)

293

Downloads (7d)

1,148

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #135

Analysis

Activity Inputs

82.3 / 100

StarsRepository reach

19.9 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

12.4 / 20

Common questions about Jshookmcp

Public supply-chain signals for Jshookmcp are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Jshookmcp carries less obvious unverified-evidence risk than projects with thin signals.

Does Jshookmcp publish package provenance?

Yes. Jshookmcp's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Jshookmcp have an OpenSSF Scorecard?

Jshookmcp has an OpenSSF Scorecard score of 5.5/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 Jshookmcp actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Jshookmcp use?

Jshookmcp ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Jshookmcp's commits signed?

20% of the last 100 commits to Jshookmcp 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

Jshookmcp 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

high confidence

Extensions

Extension based plugin/integration surface detected.

browser

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 Jshookmcp'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-10-10

Provenance Added

Package provenance attestation detected

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Jshookmcp?

For maintainers

HVTrust scores Jshookmcp 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-11-10

Rank Moved

Rank rose 18 spots (#153 → #135)

2026-10-22

Grade Changed

Trust grade B → A

2026-10-22

Rank Moved

Rank rose 26 spots (#180 → #154)

2026-10-10

Provenance Added

Package provenance attestation detected

2026-10-10

Grade Changed

Trust grade C → B

2026-10-10

Rank Moved

Rank rose 342 spots (#515 → #173)

2026-10-10

HVTrust Changed

HVTrust up 14.7pts (64.5 → 79.2)

2026-10-06

Grade Changed

Trust grade B → C

2026-10-06

Rank Moved

Rank dropped 32 spots (#475 → #507)

2026-10-04

Rank Moved

Rank dropped 17 spots (#459 → #476)

2026-09-30

Rank Moved

Rank dropped 88 spots (#380 → #468)

2026-09-27

Rank Moved

Rank dropped 19 spots (#355 → #374)

2026-09-25

Rank Moved

Rank dropped 16 spots (#346 → #362)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 260 spots (#614 → #354)

2026-09-23

HVTrust Changed

HVTrust up 35.2pts (33.5 → 68.7)

2026-09-22

Newly Listed

First tracked at rank #614

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank rose 11 spots (#364 → #353)

2026-09-19

Rank Moved

Rank rose 14 spots (#378 → #364)

2026-09-15

Rank Moved

Rank rose 38 spots (#404 → #366)

2026-09-13

Rank Moved

Rank dropped 10 spots (#394 → #404)

2026-09-12

Rank Moved

Rank dropped 10 spots (#384 → #394)

2026-09-11

Rank Moved

Rank dropped 12 spots (#372 → #384)

2026-09-07

Rank Moved

Rank dropped 29 spots (#335 → #364)

2026-09-05

Grade Changed

Trust grade D → B

2026-09-05

Rank Moved

Rank rose 657 spots (#985 → #328)

2026-09-05

HVTrust Changed

HVTrust up 24.4pts (43.0 → 67.4)

2026-09-04

Rank Moved

Rank dropped 24 spots (#961 → #985)

2026-09-03

Rank Moved

Rank dropped 55 spots (#906 → #961)

2026-09-02

Rank Moved

Rank dropped 54 spots (#852 → #906)

2026-09-01

Rank Moved

Rank dropped 30 spots (#822 → #852)

2026-08-31

Rank Moved

Rank dropped 35 spots (#787 → #822)

2026-08-30

Scorecard Added

OSSF Scorecard: 5.0/10

2026-08-30

Rank Moved

Rank rose 310 spots (#1097 → #787)

2026-08-30

HVTrust Changed

HVTrust up 19.9pts (23.3 → 43.2)

2026-08-29

Rank Moved

Rank dropped 39 spots (#1058 → #1097)

2026-08-28

Rank Moved

Rank dropped 29 spots (#1029 → #1058)

2026-08-27

Rank Moved

Rank dropped 23 spots (#1006 → #1029)

2026-08-26

Rank Moved

Rank dropped 94 spots (#912 → #1006)

2026-08-25

Rank Moved

Rank rose 38 spots (#950 → #912)

2026-08-24

Rank Moved

Rank dropped 11 spots (#939 → #950)

2026-08-16

Rank Moved

Rank dropped 26 spots (#925 → #951)

GitHub → Website → npm: @jshookmcp/jshook

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/jshookmcp.svg)](https://hvtracker.net/agents/jshookmcp)
            
HTML:
            <a href="https://hvtracker.net/agents/jshookmcp"><img src="https://hvtracker.net/badge/jshookmcp.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

Jshookmcp

How Jshookmcp could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Jshookmcp compares in MCP Servers

Where the 82.7 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Jshookmcp

AI agent surface

Maintain Jshookmcp?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers