vuln-priority
Related Servers
Alternatives to vuln-priority
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables CVE lookups and risk assessment by integrating CISA Known Exploited Vulnerabilities (KEV) data and CVSS metrics. It helps users prioritize patching efforts by ranking vulnerabilities based on exploitation status and calculated risk scores.MIT
- AlicenseNot gradedqualityDmaintenanceProvides multi-source vulnerability intelligence for AI-powered security operations, combining NVD CVSS, CISA KEV, and EPSS scores without requiring an API key.1MIT
- AlicenseBqualityBmaintenanceEnables vulnerability lookup and triage across NVD, EPSS, CISA KEV, OSV, and many other sources, while tracking an estate's exposure changes from SBOMs and lockfiles through snapshots and prioritized diffs.32Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to look up CVE details, EPSS exploit probability, and CISA KEV status from free public APIs to prioritize vulnerabilities by real-world risk. Combines these sources into a single enriched, prioritized view using a KEV > EPSS > CVSS rule.MIT
- AlicenseNot gradedqualityDmaintenanceProvides real-time vulnerability intelligence including CVE lookup, EPSS exploit probability, and CISA KEV status from free APIs, enabling AI assistants to prioritize CVEs by real-world risk.MIT
- AlicenseAqualityCmaintenanceEnables Claude to look up known vulnerabilities in a project's dependencies across OSV.dev, CVE.org, NVD, CISA KEV and EPSS, then rank the findings by real-world exploitation so the most urgent fixes surface first. It supports single-package checks, keyword CVE searches, and whole-lockfile scans, with upgrade-path reasoning.4MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: package_vulns checks package versions, prioritize_vulns ranks CVE IDs, recent_exploited shows newly added KEV entries, and vuln_details provides deep dive on a single CVE. No two tools overlap in their primary function.
Tool names mix conventions: 'prioritize_vulns' follows verb_noun, but 'package_vulns' and 'vuln_details' are noun phrases, and 'recent_exploited' is adjective+past participle. The naming is readable and consistent in style (lowercase underscores) but lacks a uniform verb_noun pattern.
With 4 tools, the server is tightly scoped to its purpose of vulnerability prioritization. Each tool covers a distinct workflow step, and none feel redundant or unnecessary.
The surface covers the core workflows: checking packages, ranking CVEs, viewing recent exploited vulnerabilities, and retrieving detailed information. Minor gaps exist (e.g., no direct way to list all vulnerabilities for a package beyond the top 50), but agents can still accomplish the intended tasks without dead ends.