exploitdb

This ExploitDB MCP Server exposes a suite of tools to query and analyze the ExploitDB dataset within an MCP-enabled assistant workflow. It supports core search capabilities to find exploits by keywords, IDs, or CVEs, as well as advanced filters by platform, type, author, and date. You can retrieve detailed exploit information, get recent additions, and explore statistics and trends. Additionally, there are utilities to batch fetch, export results, and compare multiple exploits side-by-side. Use the provided tool names under the mcp-exploitdb-server to perform the corresponding operations in your prompts or automation scripts.

Prerequisites:

• Node.js v16 or higher
• npm v7 or higher

Installation steps:

1. Clone the repository:

git clone https://github.com/Cyreslab-AI/exploitdb-mcp-server.git
cd exploitdb-mcp-server

2. Install dependencies:

npm install

3. Build the project:

npm run build

4. Configure the server:

• Create a .env file in the root directory based on .env.example
• Adjust settings as needed (data directory, update frequency, etc.)

5. Initialize the database:

npm run update-db

Note: The initial database update may take several minutes as it processes ~47,000 exploits from the ExploitDB CSV file. The script handles missing or malformed data gracefully by using fallback values for required fields.

6. Run the server:

node build/index.js

MCP configuration: To use this server with Claude or other MCP-compatible assistants, add it to your MCP configuration:

{
  "mcpServers": {
    "mcp-exploitdb-server": {
      "command": "node",
      "args": ["/path/to/exploitdb-mcp-server/build/index.js"]
    }
  }
}

Tips and considerations:

• The initial database update processes a large dataset; ensure adequate disk space and consider running updates during off-peak times.
• Environment variables like DATA_DIR and UPDATE_INTERVAL can be tuned to fit your deployment (e.g., containerized environments may require mounting a volume for DATA_DIR).
• The server exposes 18 tools; each has specific arguments. Refer to examples in the README to structure your tool calls correctly.
• If you modify the build, remember to re-run npm run build and restart the MCP server to apply changes.