Npm Sentinel MCP

A powerful Model Context Protocol (MCP) server that revolutionizes NPM package analysis through AI.

MCP Servers TypeScript Grade D Listed MIT
42.4/100
Rank #986 of 1320
Compare Npm Sentinel MCP

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-24 · 11d ago
Recent change
Rank +7

Is Npm Sentinel MCP safe? Npm Sentinel MCP scores 42.4/100 (Grade D), ranked #986 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 36% of recent commits are signed; last pushed 2026-08-24. 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
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 12 spots (#974 → #986)
2026-09-03
Rank Moved
Rank dropped 40 spots (#934 → #974)
2026-09-02
Rank Moved
Rank dropped 56 spots (#878 → #934)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
50.0
Activity sub-score · out of 100
#546

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

Signals refreshed 2026-09-04 13:33 UTC · Repo last pushed 11 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
18
Forks
10
Last Push
2026-08-24
11 days ago
Commits (4 wk)
12
Downloads (7d)
HN mentions (30d)
Open Issues
0
Rank Change
▼12
was #974

Analysis

HVTrust Dimensions vs MCP Servers

42.4 / 100 · 67.0% confidence

Npm Sentinel MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.3 / 25
in line with avg 9.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.3 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
15.7 / 20
3.5 above avg 12.2
AdoptionLog-scaled stars · package downloads
3.1 / 20
3.1 below avg 6.2

Activity Inputs

50.0 / 100
StarsRepository reach
7.7 / 30
FreshnessLast push recency
23.5 / 25
ActivityRecent commits
13.9 / 25
CommunityFork signal
4.8 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
Not available
Signed Commits
36%
of last 100 commits verified

Is Npm Sentinel MCP safe?

Public trust evidence for Npm Sentinel 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 Npm Sentinel MCP publish package provenance?
Yes. Npm Sentinel MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Npm Sentinel MCP have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Npm Sentinel MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Npm Sentinel MCP actively maintained?
Maintained. Last push was 11 days ago.
What license does Npm Sentinel MCP use?
Npm Sentinel MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Npm Sentinel MCP's commits signed?
36% of the last 100 commits to Npm Sentinel 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
Npm Sentinel MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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

Maintain Npm Sentinel MCP?

For maintainers

HVTrust scores Npm Sentinel 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.

Reputation Timeline

Signal history
Rank 14Listed 1
2026-09-04
Rank Moved
Rank dropped 12 spots (#974 → #986)
2026-09-03
Rank Moved
Rank dropped 40 spots (#934 → #974)
2026-09-02
Rank Moved
Rank dropped 56 spots (#878 → #934)
2026-09-01
Rank Moved
Rank dropped 31 spots (#847 → #878)
2026-08-31
Rank Moved
Rank dropped 30 spots (#817 → #847)
2026-08-30
Rank Moved
Rank dropped 53 spots (#764 → #817)
2026-08-29
Rank Moved
Rank dropped 50 spots (#714 → #764)
2026-08-28
Rank Moved
Rank dropped 44 spots (#670 → #714)
2026-08-27
Rank Moved
Rank dropped 24 spots (#646 → #670)
2026-08-26
Rank Moved
Rank dropped 99 spots (#547 → #646)
2026-08-24
Rank Moved
Rank rose 18 spots (#563 → #545)
2026-08-13
Rank Moved
Rank dropped 13 spots (#534 → #547)
2026-08-12
Rank Moved
Rank rose 11 spots (#545 → #534)
2026-08-10
Rank Moved
Rank dropped 21 spots (#524 → #545)
2026-08-08
Newly Listed
First tracked at rank #521

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 42.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/npm-sentinel-mcp.svg)](https://hvtracker.net/agents/npm-sentinel-mcp)
HTML:
<a href="https://hvtracker.net/agents/npm-sentinel-mcp"><img src="https://hvtracker.net/badge/npm-sentinel-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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