Skip to main content
Glama
pipeworx-io

mcp-mitre-cwe

by pipeworx-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

@pipeworx/mitre-cwe

MITRE Common Weakness Enumeration (CWE) MCP — software/hardware weakness taxonomy. Wraps the CWE API. Keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

  • weakness(id, view?) — CWE record by id (e.g. 79, CWE-79)

  • category(id) — category record

  • view(id) — view record (e.g. 1003)

  • children(id) — children of a weakness/category/view

  • parents(id) — parent relationships

  • descendants(id) — full subtree

  • relationship(source_id, target_id) — relationship details between two CWEs

Related MCP server: CVE MCP Server

Data source

https://cwe-api.mitre.org/api/v1/

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "mitre-cwe": {
      "url": "https://gateway.pipeworx.io/mitre-cwe/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/mitre-cwe/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Mitre Cwe data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

This server cannot be deployed

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • ATT&CK MCP Server

    alex-llm
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables querying the MITRE ATT\&CK framework for adversarial tactics, techniques, mitigations, and detection methods through natural language, supporting both ID-based and fuzzy name-based searches.
    3
    -

  • CVE MCP Server

    davidculver
    A
    license
    B
    quality
    D
    maintenance
    Provides conversational access to a local CVE (Common Vulnerabilities and Exposures) database, enabling natural language queries to search vulnerabilities, retrieve detailed CVE information, and view security statistics.
    3
    MIT