Jshookmcp

js hook toolkit that all you need

MCP Servers TypeScript Grade B Listed AGPL-3.0
67.4/100
Rank #361 of 1328
Compare Jshookmcp

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-08 · 0d ago
Recent change
Rank +7

Is Jshookmcp safe? Jshookmcp scores 67.4/100 (Grade B), ranked #361 of 1328 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 5.0/10; 33% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/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.
82.2
Activity sub-score · out of 100
#205

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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-09-08 15:03 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
2.0k
Forks
457
Last Push
2026-09-08
today
Commits (4 wk)
185
Downloads (7d)
782
npm
HN mentions (30d)
Open Issues
2
Rank Change
▲3
was #364

Analysis

HVTrust Dimensions vs MCP Servers

67.4 / 100 · 100.0% confidence

Jshookmcp MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.9 / 25
2.0 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.8 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
11.8 / 20
4.9 above avg 6.9

Activity Inputs

82.2 / 100
StarsRepository reach
19.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.0 / 10
OpenSSF Scorecard · scanned Sep 1, 2026
Signed Commits
33%
of last 100 commits verified
Binary-Artifacts 5
Branch-Protection 1
CI-Tests 10
CII-Best-Practices 0
Code-Review 1
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 7
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Jshookmcp safe?

Jshookmcp 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 Jshookmcp publish package provenance?
No published build provenance is currently detected for Jshookmcp. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Jshookmcp have an OpenSSF Scorecard?
Jshookmcp has an OpenSSF Scorecard score of 5.0/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?
33% 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

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.

Reputation Timeline

Signal history
Rank 17HVTrust 2Listed 1Scorecard 1Grade 1
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)
2026-08-12
Rank Moved
Rank rose 12 spots (#922 → #910)
2026-08-10
Rank Moved
Rank dropped 52 spots (#856 → #908)
2026-08-08
Newly Listed
First tracked at rank #852

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 67.4 Grade B
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.3 · Raw JSON