Skip to main content
Glama
Bilel-Eljaamii

cwe-search_mcp

by Bilel-Eljaamii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to cwe-search_mcp

No user-submitted related servers found.

    Related Servers

    • mcp-mitre-cwe

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying MITRE Common Weakness Enumeration (CWE) data, including weaknesses, categories, views, and their relationships, through natural language or direct tools.
      1 npm
      MIT

    • NVD-MCP

      aim-sec
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for searching NIST's National Vulnerability Database, enabling retrieval of recent CVEs, keyword/CPE/CWE searches, and detailed CVE information.
      Apache 2.0

    • Vulnerability Registry MCP

      MalkiLevinzon
      F
      license
      A
      quality
      B
      maintenance
      Enables querying and analyzing a legacy, file-based vulnerability registry via MCP tools for CVE lookup, search, vendor navigation, and aggregate statistics.
      5
      -

    • wpscan-mcp

      sjinks
      A
      license
      A
      quality
      A
      maintenance
      Enables querying the WPScan API for WordPress plugin, theme, core vulnerabilities, and specific vulnerability lookups through MCP tools.
      4
      7 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct aspect of CWE data: version, metadata, weakness, category, view, and specific relationship directions (parents, children, descendants, ancestors). There is minor overlap between get_cwe_info and get_cwe_weakness, but their scopes differ (metadata vs full weakness details).

    Naming Consistency5/5

    All tools consistently use the 'get_cwe_' prefix followed by a specific noun or relationship, forming a clear and predictable verb_noun pattern. The naming convention is uniform across the entire set.

    Tool Count5/5

    With 9 tools, the server is well-scoped for a CWE lookup and traversal service. Each tool serves a clear purpose without redundancy or bloat, covering all major CWE resource types and relationship queries.

    Completeness4/5

    The server provides comprehensive coverage for CWE retrieval: metadata, weaknesses, categories, views, and all four relationship directions (parents, children, ancestors, descendants). The main gap is the lack of a keyword-based search, but the core ID- and relationship-based workflows are fully supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources