Skip to main content
Glama
johannschiffer

CVESentry MCP

by johannschiffer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CVESentry MCP

No user-submitted related servers found.

    Related Servers

    • @4da/mcp-server by 4DA-Systems

      @4da/mcp-serverofficial

      4DA-Systems
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to learn, from locally read lockfiles, what changes between the dependency version installed and a target version, which of the user's files that upgrade touches, and which vulnerabilities it resolves. It also performs OSV-matched vulnerability scans, ranks upgrade plans, and stores decision memory, running entirely on the user's machine with no account or API keys.
      11
      394 npm
      Apache 2.0

    • OSV Dependency Vulnerability

      fairquery
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to submit npm, PyPI, Go, or Maven packages and manifests to the free OSV.dev database and receive per-package and per-advisory results with CVE mappings, CVSS scores, severities, and the versions that fix each issue. It also supports filtering by minimum severity, de-duplicating alias advisories, and machine-readable error/warning rows for CI gates and upgrade recommendations.
      3
      MIT
    • Fetter MCP by fetter-io

      Fetter MCPofficial

      fetter-io
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time Python package vulnerability data, enabling AI agents to check CVEs, CVSS scores, and safe versions for informed dependency decisions.
      1
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct primary purpose, but there is minor overlap: search_cve can search by CVE ID while get_cve_details retrieves full details for a CVE ID, and audit_manifest returns fix recommendations that overlap with get_safe_recommendation's single-package fix output. The descriptions still provide enough guidance to select correctly.

    Naming Consistency5/5

    All four tool names follow a consistent snake_case verb_noun pattern (search_cve, audit_manifest, get_cve_details, get_safe_recommendation). There is no mixing of conventions or verb styles.

    Tool Count5/5

    Four tools are well-scoped for a local CVE lookup and remediation server: search, audit, detailed lookup, and safe version recommendation. Each tool earns its place and the set is not bloated or thin.

    Completeness4/5

    The set covers the core lifecycle: lookup by ID/package/keyword, audit a manifest, retrieve full CVE metadata, and get a safe patch version. A minor gap is the lack of a direct 'is this version vulnerable?' query, though agents can infer this from search_cve or get_safe_recommendation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources