cwe-search_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_cwe_content_versionA | Get CWE content version information Calls endpoint: GET /version |
| get_cwe_infoA | Get metadata for specified CWE ID(s) Args: ids: Comma-separated list of CWE IDs (with or without 'CWE-' prefix) Example: "79" or "CWE-79" or "79,89,CWE-22" Returns: Dictionary with CWE metadata or error information |
| get_cwe_weaknessA | Get CWE weaknesses by ID(s) or all weaknesses Args: ids: Comma-separated CWE IDs or "all" to retrieve all weaknesses Examples: "79", "CWE-89,125", "all" Returns: Dictionary with "Weaknesses" array or error information |
| get_cwe_categoryA | Get CWE categories by ID(s) or all categories Args: ids: Comma-separated category IDs (with/without 'CWE-') or "all" Examples: "123", "CWE-456,789", "all" Returns: Dictionary with "Categories" array or error information |
| get_cwe_viewA | Get CWE views by ID(s) or all views Args: ids: Comma-separated view IDs (with/without 'CWE-') or "all" Examples: "1000", "CWE-1010,1020", "all" Returns: Dictionary with "Views" array or error information |
| get_cwe_parentsA | Get parents of a specified CWE weakness, filtered by view Args: cwe_id: CWE ID (with/without 'CWE-') view: Optional view identifier to filter relationships Returns: Dictionary with "Parents" array or error information |
| get_cwe_descendantsA | Get descendants of a specified CWE weakness, filtered by view Args: cwe_id: CWE ID (with/without 'CWE-') view: Optional view identifier to filter relationships Returns: Dictionary with "Descendants" array or error information |
| get_cwe_childrenA | Get children of a specified CWE weakness, filtered by view Args: cwe_id: CWE ID (with/without 'CWE-') view: Optional view identifier to filter relationships Returns: Dictionary with "Children" array or error information |
| get_cwe_ancestorsA | Get ancestors of a specified CWE weakness, filtered by view and primary flag Args: cwe_id: CWE ID (with/without 'CWE-') view: Optional view identifier to filter relationships primary: Limit ancestors to include only primary parents Returns: Dictionary with "Ancestors" array or error information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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).
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.
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.
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.