misp-mcp
An MCP (Model Context Protocol) server for MISP (Malware Information Sharing Platform & Threat Intelligence Sharing). Enables LLMs to perform IOC lookups, manage events, discover correlations, and export threat intelligence directly from your MISP instance.
Features
36 MCP Tools covering events, attributes, correlations, tags, exports, sightings, warninglists, objects, galaxies, feeds, organisations, and server management
3 MCP Resources for browsing attribute types, instance statistics, and available taxonomies
3 MCP Prompts for guided IOC investigation, incident event creation, and threat reporting
SSL Flexibility for self-signed certificates common in MISP deployments
Export Formats including CSV, STIX, Suricata, Snort, text, RPZ, and hash lists
MITRE ATT&CK Integration via galaxy cluster search and attachment
Bulk Operations for adding multiple IOCs to events in a single call
Correlation Engine for discovering cross-event relationships through shared indicators
Related MCP server: Cyberbro MCP Server
Prerequisites
Node.js 20 or later
A running MISP instance with API access
MISP API key (generated from MISP UI: Administration > List Auth Keys)
Installation
git clone https://github.com/solomonneas/misp-mcp.git
cd misp-mcp
npm install
npm run buildConfiguration
Set the following environment variables:
export MISP_URL=https://misp.example.com
export MISP_API_KEY=your-api-key-here
export MISP_VERIFY_SSL=true # Set to 'false' for self-signed certificatesVariable | Required | Default | Description |
| Yes | - | MISP instance base URL |
| Yes | - | API authentication key |
| No |
| Set |
| No |
| Request timeout in seconds |
Usage
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"misp": {
"command": "misp-mcp",
"env": {
"MISP_URL": "https://misp.example.com",
"MISP_API_KEY": "your-api-key-here",
"MISP_VERIFY_SSL": "false"
}
}
}
}Claude Code
claude mcp add misp \
--env MISP_URL=https://misp.example.com \
--env MISP_API_KEY=your-api-key-here \
--env MISP_VERIFY_SSL=false \
-- misp-mcpAdd --scope user to make it available from any directory instead of only the current project.
OpenClaw
If you're running from a source checkout instead of the npm-installed binary, point command/args at the built dist/index.js:
openclaw mcp set misp '{
"command": "node",
"args": ["/absolute/path/to/misp-mcp/dist/index.js"],
"env": {
"MISP_URL": "https://misp.example.com",
"MISP_API_KEY": "your-api-key-here",
"MISP_VERIFY_SSL": "false"
}
}'Or, with the global npm install:
openclaw mcp set misp '{
"command": "misp-mcp",
"env": {
"MISP_URL": "https://misp.example.com",
"MISP_API_KEY": "your-api-key-here",
"MISP_VERIFY_SSL": "false"
}
}'Then restart the OpenClaw gateway so the new server is picked up:
systemctl --user restart openclaw-gateway
openclaw mcp list # confirm "misp" is registeredHermes Agent
Hermes Agent reads MCP config from ~/.hermes/config.yaml under the mcp_servers key. Add an entry:
mcp_servers:
misp:
command: "misp-mcp"
env:
MISP_URL: "https://misp.example.com"
MISP_API_KEY: "your-api-key-here"
MISP_VERIFY_SSL: "false"Or, when running from a source checkout instead of the global npm install:
mcp_servers:
misp:
command: "node"
args: ["/absolute/path/to/misp-mcp/dist/index.js"]
env:
MISP_URL: "https://misp.example.com"
MISP_API_KEY: "your-api-key-here"
MISP_VERIFY_SSL: "false"Then reload MCP from inside a Hermes session:
/reload-mcpCodex CLI
Codex CLI registers MCP servers via codex mcp add:
codex mcp add misp \
--env MISP_URL=https://misp.example.com \
--env MISP_API_KEY=your-api-key-here \
--env MISP_VERIFY_SSL=false \
-- misp-mcpOr, when running from a source checkout:
codex mcp add misp \
--env MISP_URL=https://misp.example.com \
--env MISP_API_KEY=your-api-key-here \
--env MISP_VERIFY_SSL=false \
-- node /absolute/path/to/misp-mcp/dist/index.jsCodex writes the entry to ~/.codex/config.toml under [mcp_servers.misp]. Verify with:
codex mcp listStandalone
MISP_URL=https://misp.example.com MISP_API_KEY=your-key node dist/index.jsDocker
docker build -t misp-mcp .
docker run -e MISP_URL=https://misp.example.com -e MISP_API_KEY=your-key -e MISP_VERIFY_SSL=false misp-mcpDevelopment
MISP_URL=https://misp.example.com MISP_API_KEY=your-key npm run devTools Reference
Event Tools (6)
Tool | Description |
| Search events by IOC value, type, tags, date range, organization |
| Get full event details including attributes, objects, galaxies, related events |
| Create a new event with threat level, distribution, and analysis status |
| Update event metadata (info, threat level, analysis, publish state) |
| Publish an event to trigger alerts to sharing partners |
| Add or remove tags (TLP, MITRE ATT&CK, custom) from an event |
Attribute Tools (4)
Tool | Description |
| Search IOCs across all events with type, category, and correlation filters |
| Add a single IOC to an event |
| Add multiple IOCs to an event in one operation |
| Soft or hard delete an attribute |
Correlation & Intelligence Tools (3)
Tool | Description |
| Find all events and attributes matching a value, with cross-event correlations |
| Discover events related through shared IOCs |
| Get all available attribute types and category mappings |
Tag & Taxonomy Tools (2)
Tool | Description |
| List available tags with usage statistics |
| Find events or attributes by tag |
Export Tools (2)
Tool | Description |
| Export IOCs in CSV, STIX, Suricata, Snort, text, or RPZ format |
| Export file hashes (MD5, SHA1, SHA256) for HIDS integration |
Sighting & Warninglist Tools (2)
Tool | Description |
| Report a sighting, false positive, or expiration for an IOC |
| Check if a value appears on known benign/false positive lists |
Object Tools (4)
Tool | Description |
| List available MISP object templates (file, domain-ip, email, etc.) |
| Get template details with required/optional attributes |
| Add a structured object (grouped attributes) to an event |
| Delete an object from an event |
Galaxy Tools (4)
Tool | Description |
| List galaxies (MITRE ATT&CK, threat actors, malware, tools, etc.) |
| Get galaxy details with all clusters |
| Search clusters by keyword (find ATT&CK techniques, threat actors) |
| Attach a cluster (ATT&CK technique, etc.) to an event or attribute |
Feed Tools (4)
Tool | Description |
| List configured threat intel feeds |
| Enable or disable a feed |
| Trigger a fetch/pull from a feed |
| Cache feed data locally for correlation |
Organisation Tools (2)
Tool | Description |
| List local and remote sharing partner organisations |
| Get organisation details |
Server & Admin Tools (3)
Tool | Description |
| Get MISP version, permissions, and diagnostics |
| List sharing groups for controlled distribution |
| Delete a MISP event |
Resources
Resource URI | Description |
| All supported attribute types, categories, and their mappings |
| MISP instance statistics |
| Available taxonomies (TLP, MITRE ATT&CK, etc.) |
Prompts
Prompt | Description |
| Deep IOC investigation: search, correlate, check warninglists, summarize threat context |
| Guided event creation from an incident description with IOC ingestion |
| Generate a threat intelligence report from MISP data |
Usage Examples
Search for an IOC
"Search MISP for the IP address 203.0.113.50"
Uses misp_search_events and misp_search_attributes to find all events and attributes referencing this IP.
Investigate a suspicious domain
"Investigate evil-domain.com in MISP"
Triggers the investigate-ioc prompt workflow: searches for the domain, checks correlations, queries warninglists, and provides a structured threat assessment.
Create an incident event
"Create a MISP event for a phishing campaign targeting our finance team. The phishing emails came from attacker@evil.com and linked to https://evil-login.com/harvest"
Uses misp_create_event followed by misp_add_attributes_bulk to create a fully populated event.
Export Suricata rules
"Export all IOCs from the last 7 days as Suricata rules"
Uses misp_export_iocs with format "suricata" and last "7d".
Check for false positives
"Is 8.8.8.8 on any MISP warninglists?"
Uses misp_check_warninglists to verify if the value is a known benign indicator.
Find MITRE ATT&CK techniques
"Search for phishing techniques in MITRE ATT&CK"
Uses misp_search_galaxy_clusters to find relevant ATT&CK techniques, then misp_attach_galaxy_cluster to link them to events.
Add structured objects
"Add a file object to event 1 with filename encrypt.exe, SHA256 hash, and file size"
Uses misp_add_object with the "file" template to create a structured group of related attributes.
Supported Attribute Types
Type | Category | Example |
| Network activity | Source IP address |
| Network activity | Destination IP address |
| Network activity | Domain name |
| Network activity | Hostname |
| Network activity | Full URL |
| Payload delivery | Sender email address |
| Payload delivery | MD5 file hash |
| Payload delivery | SHA1 file hash |
| Payload delivery | SHA256 file hash |
| Payload delivery | File name |
Use misp_describe_types for the complete list of supported types and categories.
Testing
npm test # Unit tests (55 tests, mocked)
npm run test:integration # Integration tests against live MISP (27 tests)
npm run test:watch # Watch mode
npm run lint # Type checkIntegration tests require MISP_URL, MISP_API_KEY, and optionally MISP_VERIFY_SSL=false environment variables.
Project Structure
misp-mcp/
src/
index.ts # MCP server entry point
config.ts # Environment config + validation
client.ts # MISP REST API client
types.ts # MISP API type definitions
resources.ts # MCP resources
prompts.ts # MCP prompts
tools/
events.ts # Event CRUD tools
attributes.ts # Attribute management tools
correlation.ts # Correlation & intelligence tools
tags.ts # Tag and taxonomy tools
exports.ts # Export format tools
sightings.ts # Sighting tools
warninglists.ts # Warninglist checks
objects.ts # Object template & CRUD tools
galaxies.ts # Galaxy & cluster tools (MITRE ATT&CK)
feeds.ts # Feed management tools
organisations.ts # Organisation management tools
servers.ts # Server admin & sharing group tools
tests/
client.test.ts # API client unit tests
tools.test.ts # Tool handler unit tests
integration.test.ts # Live MISP API integration tests
Dockerfile
package.json
tsconfig.json
tsup.config.ts
vitest.config.ts
vitest.integration.config.ts
README.mdLicense
MIT
Available Tools
36 toolsmisp_add_attributeB
Add an IOC/attribute to a MISP event
Inputs: type (required), value (required), eventId (required), tags, +4 more.
misp_add_attributes_bulkB
Add multiple attributes (IOCs) to a MISP event at once
Inputs: eventId (required), attributes (required).
misp_add_objectB
Add a MISP object (structured group of attributes) to an event
Inputs: eventId (required), attributes (required), templateName (required), comment, +1 more.
misp_add_sightingB
Report a sighting of an IOC (confirms it was observed in the wild, marks as false positive, or sets expiration)
Inputs: type (required), value, source, timestamp, +1 more.
misp_attach_galaxy_clusterB
Attach a galaxy cluster (MITRE ATT&CK technique, threat actor, etc.) to an event or attribute
Inputs: targetId (required), targetType (required), galaxyClusterId (required).
misp_cache_feedA
Cache feed data locally for correlation without creating events
Inputs: feedId (required).
misp_check_warninglistsA
Check if an observable value appears on any MISP warninglists (known benign/false positive lists)
Inputs: value (required).
misp_correlateB
Find correlations for a specific observable value across all MISP events
Inputs: value (required).
misp_create_eventA
Create a new MISP event for documenting incidents or threat intelligence. Does not publish - use misp_publish_event separately.
Inputs: info (required), analysis (required), threatLevel (required), distribution (required), +2 more.
misp_delete_attributeB
Delete (soft or hard) an attribute from MISP. Destructive: requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true); hard delete also requires confirmHard:true.
Inputs: attributeId (required), hard, confirm, confirmHard.
misp_delete_eventA
Delete a MISP event (requires appropriate permissions). Destructive: requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true).
Inputs: eventId (required), confirm.
misp_delete_objectA
Delete a MISP object from an event. Destructive: requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true); hard delete also requires confirmHard:true.
Inputs: objectId (required), hard, confirm, confirmHard.
misp_describe_typesA
Get all available MISP attribute types and categories with their mappings
Inputs: no named parameters.
misp_export_hashesA
Export file hashes from MISP for HIDS integration
Inputs: format (required), last, tags.
misp_export_iocsB
Export IOCs from MISP in various formats (CSV, STIX, Suricata, Snort, text, RPZ)
Inputs: format (required), last, tags, type, +1 more.
misp_fetch_feedB
Trigger a fetch/pull of data from a specific MISP feed
Inputs: feedId (required).
misp_get_eventA
Get full details of a specific MISP event including all attributes, objects, tags, and related events
Inputs: eventId (required).
misp_get_galaxyA
Get a specific galaxy with its clusters (e.g., MITRE ATT&CK techniques, threat actor profiles)
Inputs: galaxyId (required).
misp_get_object_templateA
Get details of a specific MISP object template including required and optional attributes
Inputs: templateId (required).
misp_get_organisationB
Get details of a specific MISP organisation
Inputs: orgId (required).
misp_list_feedsB
List configured MISP feeds (threat intel sources, IOC feeds, etc.)
Inputs: enabled.
misp_list_galaxiesA
List available MISP galaxies (MITRE ATT&CK, threat actors, malware families, tools, etc.)
Inputs: search, namespace.
misp_list_object_templatesB
List available MISP object templates (file, domain-ip, email, network-connection, etc.)
Inputs: limit, search.
misp_list_organisationsB
List MISP organisations (local and remote sharing partners)
Inputs: scope.
misp_list_sharing_groupsA
List MISP sharing groups for controlled event distribution
Inputs: no named parameters.
misp_list_tagsB
List available MISP tags with usage statistics
Inputs: limit, search.
misp_publish_eventA
Publish a MISP event, triggering alerts and notifications to sharing partners. State-changing: requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true).
Inputs: eventId (required), confirm.
misp_search_attributesB
Search for specific attributes (IOCs) across all MISP events
Inputs: last, tags, type, limit, +4 more.
misp_search_by_tagB
Search MISP events or attributes by tag (MITRE ATT&CK, TLP, custom tags)
Inputs: tag (required), type.
misp_search_eventsC
Search MISP events by IOC value, type, tags, date range, or organization
Inputs: org, last, page, tags, +8 more.
misp_search_galaxy_clustersA
Search galaxy clusters by keyword (find specific MITRE ATT&CK techniques, threat actors, malware, etc.)
Inputs: search (required), galaxyType.
misp_server_statusA
Get MISP server version, status, and diagnostic information
Inputs: no named parameters.
misp_tag_eventA
Add or remove a tag from a MISP event (TLP, MITRE ATT&CK, custom tags). Removing a tag is destructive and requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true).
Inputs: tag (required), eventId (required), remove, confirm.
misp_toggle_feedB
Enable or disable a MISP feed
Inputs: enable (required), feedId (required).
misp_update_eventA
Update an existing MISP event's metadata (info, threat level, analysis status). Publishing is separate - use misp_publish_event.
Inputs: eventId (required), info, analysis, threatLevel.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 36 tools
Each tool targets a distinct MISP operation (create, delete, search, export, etc.) with no overlap. Even similar tools like misp_search_events and misp_search_attributes are clearly scoped to events vs attributes.
All tools follow the pattern 'misp_verb_noun' in lowercase with underscores, e.g., misp_add_attribute, misp_delete_event, misp_list_feeds. No deviations or mixed conventions.
36 tools is high but appropriate for a comprehensive MISP client covering events, attributes, objects, feeds, galaxies, tags, and more. Slightly heavy but each tool serves a clear purpose.
The tool surface covers the full lifecycle of threat intelligence in MISP: creation, deletion, search, export, feed management, galaxy/tag attachment, and server status. No obvious gaps for typical workflows.
Maintenance
Related MCP Connectors
Enrich, search, assess, and manage threat intelligence through 80+ typed MCP tools.
MCP server for Pentest-Tools.com: run scans, manage findings and reports via your preffered LLM.
Cybersecurity MCP server for URL scanning, threat intelligence, and domain reputation.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that integrates with the MISP (Malware Information Sharing Platform) to provide threat intelligence capabilities to Large Language Models.13-
- AlicenseAqualityBmaintenanceAn MCP server that extracts Indicators of Compromise (IoCs) from unstructured text and checks their reputation across multiple threat intelligence services. It enables real-time analysis of IPs, domains, hashes, and URLs, providing enriched context for security workflows within LLMs.539 PyPI19MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that integrates ThreatBook's threat intelligence API, offering 15 specialized tools for security analysis. It enables AI models to perform IP reputation checks, domain investigations, file sandbox analysis, and vulnerability intelligence lookups.50MIT
- AlicenseAqualityBmaintenanceAn MCP server for the Cortex observable analysis and active response engine. It enables LLMs to automate security investigations by running analyzers on observables like IPs and URLs and executing automated response actions.315 npm1MIT