Skip to main content
Glama

misp-mcp is a Model Context Protocol server for MISP, the open-source threat-intelligence sharing platform. It lets an LLM client such as Claude run IOC lookups, manage events, discover cross-event correlations, and export indicators directly against your own MISP instance. Unlike a generic HTTP wrapper, it ships 42 purpose-built tools, MISP-aware resources and prompts, and a confirmation gate that refuses destructive writes (delete, publish, untag) unless you explicitly approve them.

What it does

misp-mcp connects an AI agent to a MISP (Malware Information Sharing Platform & Threat Intelligence Sharing) instance over MISP's REST API and exposes it as Model Context Protocol tools, resources, and prompts. Point it at your MISP server with an API key and an LLM can search threat-intelligence events, look up and add indicators of compromise (IOCs), correlate indicators across events, attach MITRE ATT&CK galaxy clusters, check warninglists for false positives, and export IOCs as Suricata, Snort, STIX, CSV, RPZ, or hash lists. The server is read-only by default: every tool that changes MISP state refuses to run until the operator names it in MISP_ALLOWED_MUTATIONS. Destructive and publishing operations (delete, publish, untag, disabling a feed, false-positive and expiration sightings) additionally need a per-call confirmation flag, and bulk writes need confirmation above a small size.

  • 42 MCP tools covering events, attributes, correlations, tags, exports, sightings, warninglists, objects, galaxies, feeds, organisations, and server administration.

  • 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.

  • Read-only by default: state-changing tools run only when listed in MISP_ALLOWED_MUTATIONS; each also accepts dryRun: true to preview a call without sending it.

  • Confirmation-gated destructive actions: delete, publish, untag, feed disable, and false-positive/expiration sightings refuse to run without confirm: true (and confirmHard: true for permanent deletes).

  • Untrusted-data fencing: MISP content returned to the model is wrapped in <untrusted_misp_data> markers, and every tool declares MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint).

  • MITRE ATT&CK integration via galaxy cluster search and attachment.

  • Export formats including CSV, STIX, Suricata, Snort, text, RPZ, and hash lists.

  • SSL flexibility for the self-signed certificates common in on-prem MISP deployments.

Related MCP server: Cyberbro MCP Server

Quickstart

No checkout required. With Node.js 20+ installed, register the published package with any MCP client. For 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 \
  -- npx -y misp-mcp

Add --scope user to make it available from any directory instead of only the current project.

The server starts read-only. To let the agent write, add --env MISP_ALLOWED_MUTATIONS=misp_create_event,misp_add_attribute (the tools you want enabled) or --env MISP_ALLOWED_MUTATIONS='*'; see Mutation gate and destructive action safety.

Before wiring a client, verify that the package can reach MISP with the same environment:

MISP_URL=https://misp.example.com \
MISP_API_KEY=your-api-key-here \
MISP_VERIFY_SSL=false \
npx -p misp-mcp mispctrl status

This calls /servers/getVersion and prints the MISP version, recommended PyMISP version, TLS setting, and target URL. If this fails, fix the URL, API key, or TLS setting before debugging the MCP client.

MCP client config (copy-paste)

For Claude Desktop, Cursor, or any client that reads a JSON mcpServers block, add:

{
  "mcpServers": {
    "misp": {
      "command": "npx",
      "args": ["-y", "misp-mcp"],
      "env": {
        "MISP_URL": "https://misp.example.com",
        "MISP_API_KEY": "your-api-key-here",
        "MISP_VERIFY_SSL": "false"
      }
    }
  }
}

Claude Desktop reads this from ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Restart the client after editing.

Prerequisites

  • Node.js 20 or later.

  • A running MISP instance with API access.

  • A MISP API key (MISP UI: Administration > List Auth Keys).

Configuration

Variable

Required

Default

Description

MISP_URL

Yes

-

MISP instance base URL. Must be https://; plain http:// is accepted only for localhost, 127.0.0.1, and [::1]. Credentials, query strings, and fragments are rejected.

MISP_API_KEY

Yes

-

API authentication key

MISP_VERIFY_SSL

No

true

Set false (or 0) for self-signed certs. Accepts true, 1, false, 0, case-insensitive.

MISP_TIMEOUT

No

30

Request timeout in seconds (positive integer, 1–3600)

MISP_ALLOWED_MUTATIONS

No

empty (read-only)

Comma-separated list of state-changing tools the server may run (for example misp_create_event,misp_add_attribute), or * for all of them. Unknown names fail at startup.

MISP_MAX_RESPONSE_BYTES

No

16777216

Strict cap on one MISP response body, in bytes (1024–268435456). Larger responses are aborted.

MISP_ALLOW_DESTRUCTIVE

No

false

Accepts true, 1, false, 0, case-insensitive; any other value stops the server at startup. Set true to pre-authorize destructive tools so the per-call confirm flag is not required for tools that are already enabled by MISP_ALLOWED_MUTATIONS. Permanent (hard) deletes still require confirmHard.

Boolean variables (MISP_VERIFY_SSL, MISP_ALLOW_DESTRUCTIVE) share one parser: true, 1, false, 0, case-insensitive after trimming; unset or empty means the default. Any other value is rejected at startup with an error that names the variable. The MCP guard and the CLI gate use the same parser, so MISP_ALLOW_DESTRUCTIVE=1 means the same thing in both.

Mutation gate and destructive action safety

The server starts read-only. Read tools always work. A tool that changes MISP state returns a Refused: error and sends no request unless the operator lists it in MISP_ALLOWED_MUTATIONS (or sets it to *). The allowlist is read from the server's environment, so a model cannot change it.

MISP_ALLOWED_MUTATIONS=misp_create_event,misp_add_attribute,misp_tag_event

State-changing tools (gated by MISP_ALLOWED_MUTATIONS): misp_create_event, misp_update_event, misp_add_event_report, misp_publish_event, misp_tag_event, misp_delete_event, misp_add_attribute, misp_update_attribute, misp_add_attributes_bulk, misp_delete_attribute, misp_add_sighting, misp_add_object, misp_delete_object, misp_attach_galaxy_cluster, misp_toggle_feed, misp_fetch_feed, misp_cache_feed.

Every one of them accepts dryRun: true. A dry run validates the arguments, reports whether the tool is currently allowed, and sends nothing to MISP, so it works in read-only mode too.

Also require confirm: true (or MISP_ALLOW_DESTRUCTIVE=true):

  • misp_delete_event

  • misp_delete_attribute

  • misp_delete_object

  • misp_publish_event

  • misp_tag_event when remove: true

  • misp_toggle_feed when enable: false

  • misp_add_sighting with type 1 (false positive) or 2 (expiration)

  • misp_add_attributes_bulk with more than 10 attributes

Setting MISP_ALLOW_DESTRUCTIVE=true pre-authorizes the confirmations above so the per-call confirm flag can be omitted (useful for trusted automation). It does not enable any tool by itself; the tool must also be in MISP_ALLOWED_MUTATIONS.

Permanent hard deletes (hard: true on misp_delete_attribute / misp_delete_object) require a second confirmation, confirmHard: true, in addition to confirm: true. The env opt-in does not bypass confirmHard.

Future destructive CLI commands use the same policy: MISP_ALLOW_DESTRUCTIVE=true plus --confirm --destructive, with --confirm-hard still required for permanent deletes.

Untrusted MISP content

Event titles, comments, IOC values, tags, export bodies, and similar fields are written by other organizations. Tool results wrap them in <untrusted_misp_data> markers, the JSON resources carry them under an untrusted_misp_data key beside a notice so they stay valid JSON, any marker-like text inside the content is escaped, and tool descriptions and the server instructions tell the model to treat the content as data. Prompt arguments are delimited the same way.

Bounds

  • Responses are read through a strict byte cap (MISP_MAX_RESPONSE_BYTES) and the request timeout stays active until the body is fully read.

  • misp_add_attributes_bulk takes at most 100 attributes and stops after five consecutive failures; the result lists succeeded, failed, and skipped items and warns about partial updates.

  • Search tools take an integer limit from 1 to 500 and an integer page from 1; fractional, zero, negative, and oversized values are rejected. When a page comes back full, the result ends with a note that more results may exist and names the next page.

  • misp_get_related_events accepts maxAttributes up to 50 and perAttributeLimit up to 500. Tag lists are capped at 20 and object attribute lists at 100.

  • Upstream error bodies are not returned to the model. Errors carry the status class, and for 4xx responses a short, redacted message field. The API key is redacted from every error.

A guarded call returns an error (isError: true) with a Refused: message and performs no MISP request.

Tools

Verified against the server source (42 tools, registered in src/tools/).

Event tools (6)

Tool

Description

misp_search_events

Search events by IOC value, type, tags, date range, organization. limit 1-500, page from 1; a full page adds a note naming the next page

misp_get_event

Get full event details including attributes, objects, galaxies, related events

misp_create_event

Create a new event with threat level, distribution, and analysis status

misp_update_event

Update event metadata (info, threat level, analysis, publish state)

misp_publish_event

Publish an event to trigger alerts to sharing partners (requires confirm:true)

misp_tag_event

Add or remove tags (TLP, MITRE ATT&CK, custom) from an event (removal requires confirm:true)

Event report tools (3)

Tool

Description

misp_list_event_reports

List the reports attached to an event (no content). The request is scoped to the event on the MISP side and the result is bounded by limit (default 50, max 500)

misp_get_event_report

Read one report with its Markdown content (cut at 50,000 characters, and the result says so)

misp_add_event_report

Add a Markdown report to an event (name, content up to 1 MB, optional distribution 0-3, or 5 to inherit from the event; omit it to use the server default). Additive, no confirm flag, runs only when enabled in MISP_ALLOWED_MUTATIONS

Attribute tools (6)

Tool

Description

misp_search_attributes

Search IOCs across all events with type, category, and correlation filters. limit 1-500, page from 1; a full page adds a note naming the next page

misp_get_attribute

Get one attribute by ID with its tags

misp_update_attribute

Edit an attribute in place (value, type, category, toIds, comment, disableCorrelation, distribution); at least one field required, no confirm flag, runs only when enabled in MISP_ALLOWED_MUTATIONS

misp_add_attribute

Add a single IOC to an event

misp_add_attributes_bulk

Add multiple IOCs to an event in one operation

misp_delete_attribute

Soft or hard delete an attribute (requires confirm:true; hard delete also requires confirmHard:true)

Correlation & intelligence tools (3)

Tool

Description

misp_correlate

Find all events and attributes matching a value, with cross-event correlations

misp_get_related_events

Discover events related through shared IOCs

misp_describe_types

Get all available attribute types and category mappings

Tag & taxonomy tools (2)

Tool

Description

misp_list_tags

List available tags with usage statistics

misp_search_by_tag

Find events or attributes by tag

Export tools (2)

Tool

Description

misp_export_iocs

Export IOCs in CSV, STIX, Suricata, Snort, text, or RPZ format

misp_export_hashes

Export file hashes (MD5, SHA1, SHA256) for HIDS integration

Sighting & warninglist tools (3)

Tool

Description

misp_list_sightings

List the sightings recorded on an event (limit default 100, max 500; the result says when it was truncated)

misp_add_sighting

Report a sighting, false positive, or expiration for an IOC

misp_check_warninglists

Check if a value appears on known benign/false positive lists

Object tools (4)

Tool

Description

misp_list_object_templates

List available MISP object templates (file, domain-ip, email, etc.)

misp_get_object_template

Get template details with required/optional attributes

misp_add_object

Add a structured object (grouped attributes) to an event

misp_delete_object

Delete an object from an event (requires confirm:true; hard delete also requires confirmHard:true)

Galaxy tools (4)

Tool

Description

misp_list_galaxies

List galaxies (MITRE ATT&CK, threat actors, malware, tools, etc.)

misp_get_galaxy

Get galaxy details with all clusters

misp_search_galaxy_clusters

Search clusters by keyword (find ATT&CK techniques, threat actors)

misp_attach_galaxy_cluster

Attach a cluster (ATT&CK technique, etc.) to an event or attribute

Feed tools (4)

Tool

Description

misp_list_feeds

List configured threat intel feeds

misp_toggle_feed

Enable or disable a feed

misp_fetch_feed

Trigger a fetch/pull from a feed

misp_cache_feed

Cache feed data locally for correlation

Organisation tools (2)

Tool

Description

misp_list_organisations

List local and remote sharing partner organisations

misp_get_organisation

Get organisation details

Server & admin tools (3)

Tool

Description

misp_server_status

Get MISP version, permissions, and diagnostics

misp_list_sharing_groups

List sharing groups for controlled distribution

misp_delete_event

Delete a MISP event (requires confirm:true)

Resources

Resource URI

Description

misp://types

All supported attribute types, categories, and their mappings

misp://statistics

MISP instance statistics

misp://taxonomies

Available taxonomies (TLP, MITRE ATT&CK, etc.)

Prompts

Prompt

Description

investigate-ioc

Deep IOC investigation: search, correlate, check warninglists, summarize threat context

create-incident-event

Guided event creation from an incident description with IOC ingestion

threat-report

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 suspicious-domain.example 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@phish.example and linked to https://harvest.phish.example/login"

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 192.0.2.123 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

ip-src

Network activity

Source IP address

ip-dst

Network activity

Destination IP address

domain

Network activity

Domain name

hostname

Network activity

Hostname

url

Network activity

Full URL

email-src

Payload delivery

Sender email address

md5

Payload delivery

MD5 file hash

sha1

Payload delivery

SHA1 file hash

sha256

Payload delivery

SHA256 file hash

filename

Payload delivery

File name

Use misp_describe_types for the complete list of supported types and categories.

Other clients & local development

From source

git clone https://github.com/lidless-labs/misp-mcp.git
cd misp-mcp
npm install
npm run build

Then point any client's command/args at node /absolute/path/to/misp-mcp/dist/mcp-bin.js instead of npx -y misp-mcp.

Claude Code (source checkout)

claude 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/mcp-bin.js

OpenClaw

openclaw mcp set misp '{
  "command": "npx",
  "args": ["-y", "misp-mcp"],
  "env": {
    "MISP_URL": "https://misp.example.com",
    "MISP_API_KEY": "your-api-key-here",
    "MISP_VERIFY_SSL": "false"
  }
}'

For a source checkout, use "command": "node" with "args": ["/absolute/path/to/misp-mcp/dist/mcp-bin.js"]. Then restart the gateway and confirm registration:

systemctl --user restart openclaw-gateway
openclaw mcp list   # confirm "misp" is registered

Codex CLI

codex mcp add misp \
  --env MISP_URL=https://misp.example.com \
  --env MISP_API_KEY=your-api-key-here \
  --env MISP_VERIFY_SSL=false \
  -- npx -y misp-mcp

Codex writes the entry to ~/.codex/config.toml under [mcp_servers.misp]. Verify with codex mcp list.

Hermes Agent

Hermes Agent reads MCP config from ~/.hermes/config.yaml under mcp_servers:

mcp_servers:
  misp:
    command: "npx"
    args: ["-y", "misp-mcp"]
    env:
      MISP_URL: "https://misp.example.com"
      MISP_API_KEY: "your-api-key-here"
      MISP_VERIFY_SSL: "false"

Then /reload-mcp inside a Hermes session.

Docker

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-mcp

The image runs as the unprivileged node user. Application files under /app are owned by root and are read-only. Its writable home is /run/misp-mcp, and /tmp also remains writable. The image does not make the entire filesystem read-only.

The build and runtime stages use the same official node:22-slim image pinned by digest.

The Proxmox installer creates a misp-mcp system user with no login shell. The service runs with a read-only filesystem, a private temporary directory, and a writable /run/misp-mcp directory with mode 0700. Application files in /opt/misp-mcp remain owned by root. Credentials are stored in /etc/misp-mcp/environment with root ownership and mode 0600, inside a root-only directory. The systemd manager reads that file before starting the unprivileged service. Edit it as root and restart the service when credentials change.

Reviewed Proxmox installer inputs

Before running the installer, review a local copy of the script and set these immutable inputs. There are no defaults:

  • MISP_SOURCE_COMMIT: the full 40-character hexadecimal commit reviewed for installation from https://github.com/lidless-labs/misp-mcp.git.

  • NODE_VERSION: an exact Node 22 version at least 22.12.0, without a v prefix.

  • NODE_ARCH: x64 or arm64, matching the guest architecture.

  • NODE_SHA256: the 64-character SHA-256 of that version's node-v<VERSION>-linux-<ARCH>.tar.xz archive.

Obtain the archive checksum from the official release's signed SHASUMS256.txt.asc. Verify its signature with a separately trusted Node release keyring using the official binary verification instructions before supplying the checksum. Do not copy a checksum from the same unverified download as the archive.

The installer rejects missing or malformed pins before any host command or LXC creation. It downloads only from https://nodejs.org/dist/v<VERSION>/, checks the archive against the supplied checksum before extraction, then fetches the reviewed source commit from the canonical repository and checks its exact hash before npm ci --ignore-scripts or the build. Node is installed in /usr/local, including the service executable /usr/local/bin/node. Ubuntu template and apt prerequisites still follow their upstream repositories. This does not freeze the whole OS or provide a reproducible apt snapshot. An interrupted install leaves its guest for operator inspection. A retry refuses an existing container ID.

Standalone

MISP_URL=https://misp.example.com MISP_API_KEY=your-key node dist/mcp-bin.js
MISP_URL=https://misp.example.com MISP_API_KEY=your-key node dist/cli.js status

Development

MISP_URL=https://misp.example.com MISP_API_KEY=your-key npm run dev

Testing

npm test                  # Unit tests (mocked)
npm run test:integration  # Integration tests against a live MISP instance
npm run test:watch        # Watch mode
npm run lint              # Type check

Integration tests require MISP_URL, MISP_API_KEY, and optionally MISP_VERIFY_SSL=false environment variables.

Project structure

misp-mcp/
  src/
    cli.ts                # mispctrl CLI entry point
    mcp-bin.ts            # MCP stdio entry point
    mcp-server.ts         # Shared MCP server factory
    index.ts              # Library export surface
    config.ts             # Environment config + validation
    client.ts             # MISP REST API client
    guards.ts             # Mutation allowlist + destructive-action confirmation guards
    tool-specs.ts         # Per-tool annotations and mutation flags
    tool-registry.ts      # Tool registration: gate, fence, error redaction
    untrusted.ts          # <untrusted_misp_data> fencing helpers
    limits.ts             # Bulk and fan-out maxima
    types.ts              # MISP API type definitions
    resources.ts          # MCP resources
    prompts.ts            # MCP prompts
    tools/                # One module per tool family (events, attributes, ...)
  tests/                  # Unit + integration tests
  Dockerfile
  package.json

Contributing

Issues and pull requests are welcome. See CONTRIBUTING.md for the contribution path and SECURITY.md for how to report a vulnerability privately. By participating you agree to the Code of Conduct.

Why not the MISP web UI or raw API?

The MISP web UI and PyMISP are excellent for analysts working a console. misp-mcp is for the case where the operator is an LLM agent, not a human at a browser. It gives the model a typed, named tool for each common MISP operation, validates inputs with Zod, and shapes responses so a model can reason over them, rather than handing the model a raw REST endpoint and an OpenAPI dump. It also adds a guardrail layer the bare API does not: destructive operations fail closed unless the caller opts in, so an over-eager agent cannot publish or delete intelligence by accident. If you want a human-driven console, use the MISP UI. If you want PyMISP scripting, use PyMISP. Use misp-mcp when you want a chat or agent client to drive MISP safely.

What misp-mcp is not

  • Not a MISP server. It talks to an existing MISP instance over the REST API; it does not store, host, or replace MISP.

  • Not a general HTTP proxy. It exposes a curated set of MISP operations as MCP tools, not arbitrary passthrough to every MISP endpoint.

  • Not a SIEM, EDR, or alerting system. It reads and writes threat intelligence; it does not collect logs or generate alerts on its own.

  • Not a credential vault. It reads MISP_URL and MISP_API_KEY from the environment; manage and rotate those keys with your own secrets tooling.

  • Not an autonomous deleter. Destructive and publishing actions are confirmation-gated by design.

Container root access

The installer creates no guest root password and locks password login after starting the container. Manage the guest from its Proxmox host with pct enter. Service API credentials continue to use protected stdin delivery and root-only storage.

License

MIT


Available Tools

36 tools
misp_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

    A3.7/5.0

    Scored across 36 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that integrates with the MISP (Malware Information Sharing Platform) to provide threat intelligence capabilities to Large Language Models.
      13
      -
    • A
      license
      A
      quality
      B
      maintenance
      An 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.
      5
      39 PyPI
      19
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      50
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An 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.
      31
      5 npm
      1
      MIT