updated 2026-11-10 04:07 UTC

CVE MCP Server

Repository Website by mukul975

Production-grade MCP server giving Claude 27 security intelligence tools across 21 APIs — CVE lookup, EPSS scoring, CISA KEV, MITRE ATT&CK, Shodan, VirusTotal, and more.

MCP Servers Python Listed Apache-2.0

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

OSSF Scorecard 3.7 / 10
Provenance None
Signed commits 14%
Last push 40d ago
Compare CVE MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: CVE MCP Server scores 45.8/100 (Grade D), ranked #1105 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.7/10; 14% of recent commits are signed; last pushed 2026-10-01. Every point is earned from checkable signals — never paid placement. How scoring works →

How CVE MCP Server 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 CVE MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/mukul975/cve-mcp-server, Apache-2.0, last pushed 2026-10-01. 14% 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 3.7/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:

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

  3. Published packages None

    No registry package. CVE MCP Server is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-01 OSSF Scorecard: 4.7/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues CVE MCP Server’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 CVE MCP Server compares in MCP Servers

  1. #628 Codealive MCP 45.9 +0.1
  2. #629 Academia MCP 45.8 ±0
  3. #630 CVE MCP Server 45.8 this agent
  4. #631 Gemini MCP 45.7 −0.1
  5. #632 Linkup MCP Server 45.6 −0.2

Bars show each HVTrust score; the tick marks CVE MCP Server’s 45.8.

Where the 45.8 comes from

HVTrust dimensions vs the MCP Servers average

45.8 / 100 · 100.0% confidence

CVE MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.3 / 25
5.5 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
11.6 / 17
0.7 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
9.3 / 20
2.9 below avg 12.2
AdoptionLog-scaled stars · package downloads
7.8 / 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.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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.
Refresh maintenance signals The repo was last pushed 40 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
50.5
Activity sub-score · out of 100
#630
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 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-11-10 04:07 UTC · Repo last pushed 40 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
1.8k
Forks
284
Last Push
2026-10-01
40 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
5
Rank Change
▼1
was #1104

Analysis

Activity Inputs

50.5 / 100
StarsRepository reach
19.5 / 30
FreshnessLast push recency
19.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.4 / 20

Common questions about CVE MCP Server

Public trust evidence for CVE MCP Server 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 CVE MCP Server publish package provenance?
No published build provenance is currently detected for CVE MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does CVE MCP Server have an OpenSSF Scorecard?
CVE MCP Server has an OpenSSF Scorecard score of 3.7/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 CVE MCP Server actively maintained?
Slowing down. Last push was 40 days ago — keep an eye on whether activity resumes.
What license does CVE MCP Server use?
CVE MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are CVE MCP Server's commits signed?
14% of the last 100 commits to CVE MCP Server 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
medium confidence
Implemented
CVE MCP Server 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
N/A
No package source configured
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 CVE MCP Server'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
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain CVE MCP Server?

For maintainers

HVTrust scores CVE MCP Server 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 24HVTrust 2Scorecard 1Surface 1Score 1Grade 1Delisted 1Listed 1MCP 1
2026-10-09
Rank Moved
Rank dropped 11 spots (#1017 → #1028)
2026-10-01
Rank Moved
Rank dropped 25 spots (#967 → #992)
2026-09-30
Rank Moved
Rank dropped 14 spots (#953 → #967)
2026-09-25
Rank Moved
Rank dropped 15 spots (#932 → #947)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 407 spots (#521 → #928)
2026-09-23
HVTrust Changed
HVTrust up 10.2pts (39.6 → 49.8)
2026-09-22
Newly Listed
First tracked at rank #521
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 15 spots (#908 → #923)
2026-09-18
Grade Changed
Trust grade D → C
2026-09-18
Rank Moved
Rank rose 78 spots (#989 → #911)
2026-09-18
Activity Score Changed
Activity score up 6pts (49 → 55)
2026-09-11
Rank Moved
Rank dropped 14 spots (#958 → #972)
2026-09-08
Rank Moved
Rank dropped 16 spots (#937 → #953)
2026-09-07
Rank Moved
Rank dropped 44 spots (#893 → #937)
2026-09-06
Rank Moved
Rank dropped 11 spots (#882 → #893)
2026-09-05
Rank Moved
Rank dropped 56 spots (#826 → #882)
2026-09-04
Rank Moved
Rank dropped 36 spots (#790 → #826)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-09-03
Rank Moved
Rank dropped 33 spots (#757 → #790)
2026-09-02
Rank Moved
Rank dropped 36 spots (#721 → #757)
2026-09-01
Scorecard Added
OSSF Scorecard: 4.7/10
2026-09-01
Rank Moved
Rank rose 524 spots (#1245 → #721)
2026-09-01
HVTrust Changed
HVTrust up 28.7pts (19.6 → 48.3)
2026-08-31
Rank Moved
Rank dropped 18 spots (#1227 → #1245)
2026-08-30
Rank Moved
Rank dropped 18 spots (#1209 → #1227)
2026-08-29
Rank Moved
Rank dropped 21 spots (#1188 → #1209)
2026-08-28
Rank Moved
Rank dropped 17 spots (#1171 → #1188)
2026-08-27
Rank Moved
Rank dropped 16 spots (#1155 → #1171)
2026-08-26
Rank Moved
Rank dropped 57 spots (#1098 → #1155)
2026-08-24
Rank Moved
Rank dropped 12 spots (#1085 → #1097)
2026-08-16
Rank Moved
Rank dropped 32 spots (#1057 → #1089)
GitHub → Website →

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON