updated 2026-11-10 04:07 UTC

Openwebninja MCP

Repository

OpenWeb Ninja APIs MCP server

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 2.4 / 10
Provenance None
Signed commits 5%
Last push yesterday
Compare Openwebninja MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Openwebninja MCP scores 46.6/100 (Grade D), ranked #1093 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 2.4/10; 5% of recent commits are signed; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Openwebninja 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 Openwebninja 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 Partly signed

    github.com/OpenWeb-Ninja/openwebninja-mcp, MIT, last pushed 2026-11-09. 5% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

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

  3. Published packages Not linked

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

Changes to this chain

  • 2026-09-01 OSSF Scorecard: 2.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 Openwebninja 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 Openwebninja MCP compares in MCP Servers

  1. #619 Markifact: AI Performance Marketing 46.6 ±0
  2. #620 CleanSlice 46.6 ±0
  3. #621 Openwebninja MCP 46.6 this agent
  4. #622 Godot MCP 46.6 ±0
  5. #623 MCP Slim Guard 46.4 −0.2

Bars show each HVTrust score; the tick marks Openwebninja MCP’s 46.6.

Where the 46.6 comes from

HVTrust dimensions vs the MCP Servers average

46.6 / 100 · 100.0% confidence

Openwebninja MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.2 / 25
7.6 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
10.5 / 17
1.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.8 / 20
1.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.3 / 20
in line with avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-07
Rank Moved
Rank rose 10 spots (#1106 → #1096)
2026-10-30
Rank Moved
Rank rose 21 spots (#1129 → #1108)
2026-10-29
Rank Moved
Rank dropped 37 spots (#1092 → #1129)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.4/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
View MCP Servers Report missing data
50.0
Activity sub-score · out of 100
#621
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 D 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 yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
38
Forks
5
Last Push
2026-11-09
yesterday
Commits (4 wk)
8?
Downloads (7d)
383
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼2
was #1091

Analysis

Activity Inputs

50.0 / 100
StarsRepository reach
9.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
3.6 / 20

Common questions about Openwebninja MCP

Public trust evidence for Openwebninja 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 Openwebninja MCP publish package provenance?
No published build provenance is currently detected for Openwebninja 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 Openwebninja MCP have an OpenSSF Scorecard?
Openwebninja MCP has an OpenSSF Scorecard score of 2.4/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 Openwebninja MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Openwebninja MCP use?
Openwebninja MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Openwebninja MCP's commits signed?
4% of the last 100 commits to Openwebninja 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
Openwebninja 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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Openwebninja 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 Openwebninja MCP?

For maintainers

HVTrust scores Openwebninja 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 31HVTrust 3Score 2Scorecard 1Delisted 1Listed 1MCP 1
2026-11-07
Rank Moved
Rank rose 10 spots (#1106 → #1096)
2026-10-30
Rank Moved
Rank rose 21 spots (#1129 → #1108)
2026-10-29
Rank Moved
Rank dropped 37 spots (#1092 → #1129)
2026-10-28
Rank Moved
Rank rose 34 spots (#1126 → #1092)
2026-10-27
Rank Moved
Rank rose 16 spots (#1142 → #1126)
2026-10-23
Rank Moved
Rank rose 19 spots (#1155 → #1136)
2026-10-18
Rank Moved
Rank dropped 18 spots (#1128 → #1146)
2026-10-14
Rank Moved
Rank rose 13 spots (#1135 → #1122)
2026-10-13
Rank Moved
Rank rose 12 spots (#1147 → #1135)
2026-10-09
Activity Score Changed
Activity score up 5pts (39 → 44)
2026-09-25
Rank Moved
Rank rose 12 spots (#1131 → #1119)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 17 spots (#1145 → #1128)
2026-09-23
HVTrust Changed
HVTrust up 21.1pts (20.8 → 41.9)
2026-09-22
Newly Listed
First tracked at rank #1145
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 18 spots (#1100 → #1118)
2026-09-17
Rank Moved
Rank rose 110 spots (#1212 → #1102)
2026-09-17
HVTrust Changed
HVTrust up 6.4pts (36.6 → 43.0)
2026-09-17
Activity Score Changed
Activity score up 15pts (26 → 42)
2026-09-09
Rank Moved
Rank dropped 11 spots (#1189 → #1200)
2026-09-08
Rank Moved
Rank dropped 16 spots (#1173 → #1189)
2026-09-07
Rank Moved
Rank dropped 22 spots (#1151 → #1173)
2026-09-06
Rank Moved
Rank dropped 16 spots (#1135 → #1151)
2026-09-05
Rank Moved
Rank dropped 51 spots (#1084 → #1135)
2026-09-04
Rank Moved
Rank dropped 24 spots (#1060 → #1084)
2026-09-03
Rank Moved
Rank dropped 48 spots (#1012 → #1060)
2026-09-02
Rank Moved
Rank dropped 52 spots (#960 → #1012)
2026-09-01
Scorecard Added
OSSF Scorecard: 2.0/10
2026-09-01
Rank Moved
Rank rose 205 spots (#1165 → #960)
2026-09-01
HVTrust Changed
HVTrust up 15.2pts (23.3 → 38.5)
2026-08-31
Rank Moved
Rank dropped 30 spots (#1135 → #1165)
2026-08-30
Rank Moved
Rank dropped 44 spots (#1091 → #1135)
2026-08-29
Rank Moved
Rank dropped 41 spots (#1050 → #1091)
2026-08-28
Rank Moved
Rank dropped 31 spots (#1019 → #1050)
2026-08-27
Rank Moved
Rank dropped 28 spots (#991 → #1019)
2026-08-26
Rank Moved
Rank dropped 94 spots (#897 → #991)
2026-08-24
Rank Moved
Rank dropped 17 spots (#882 → #899)
2026-08-17
Rank Moved
Rank rose 12 spots (#886 → #874)
2026-08-16
Rank Moved
Rank dropped 22 spots (#864 → #886)
GitHub → npm: @openwebninja/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 46.6 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/openwebninja-mcp.svg)](https://hvtracker.net/agents/openwebninja-mcp)
HTML:
<a href="https://hvtracker.net/agents/openwebninja-mcp"><img src="https://hvtracker.net/badge/openwebninja-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