What can you do with this server?

This server connects to a MISP (Malware Information Sharing Platform) instance, enabling you to query threat intelligence, investigate indicators, explore the knowledge base, and submit new indicators — all in plain language through any MCP-compatible client. It exposes 18 tools across the following areas: Indicator Lookups * misp_lookup_ioc: Search MISP for sightings of a single IPv4/IPv6, domain, URL, or hash (defanged forms accepted). Returns a verdict with event hits, threat level, and detection-flag status. * misp_lookup_iocs: Batch triage up to 20 indicators in one call with a compact per-IOC summary. * misp_correlate_ioc: Pivot from an IOC to find other indicators appearing in the same MISP event(s) — useful for discovering related infrastructure. Event Investigation * misp_get_event: Fetch full details of a MISP event by ID (metadata, tags, attributes). * misp_search_events: Search events by title keyword, tag, and/or date range. Attribute & Object Access * misp_get_attribute: Fetch a single attribute by ID along with its parent event. * misp_get_object: Retrieve a MISP object (group of related attributes) by ID. * misp_search_attributes: Search attributes by type, category, tag, to_ids status, or event ID. Threat Intelligence Knowledge Base * misp_lookup_galaxy: Look up threat actors, malware families, tools, and ATT&CK techniques by name or synonym. * misp_list_galaxies: List all galaxy types available on the instance. * misp_list_taxonomies: View all taxonomies (TLP, kill-chain, PAP, etc.) and their enabled status. * misp_get_taxonomy: Retrieve a specific taxonomy's tags and their meanings. * misp_search_tags: Find tag definitions by name. Feed & Instance Monitoring * misp_feed_stats: See feed counts and which are enabled. * misp_instance_status: Verify connectivity, authentication, and retrieve MISP/server versions. Audit & Review * misp_review_submissions: Audit recent IOC submissions — what was added, by whom, when, and which are detection-flagged. Indicator Submission (requires write-capable API key) * misp_submit_ioc: Add a single, fully attributed indicator with required fields (reporter, justification, last-seen date, tags, detection flag). Guardrails block private/reserved IPs and first-party infrastructure. * misp_submit_iocs: Bulk validate and add up to 50 indicators; defaults to dry_run=true so you can preview before committing. All operations automatically clean defanged indicators (e.g., hxxp://evil[.]com, 1.2.3[.]4), and write operations enforce rate limiting and security guardrails.

How do I use misp-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@misp-mcp look up 102.130.113.9 in MISP" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

misp-mcp

by indranilroy99

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

This server connects to a MISP (Malware Information Sharing Platform) instance, enabling you to query threat intelligence, investigate indicators, explore the knowledge base, and submit new indicators — all in plain language through any MCP-compatible client. It exposes 18 tools across the following areas:

Indicator Lookups

misp_lookup_ioc: Search MISP for sightings of a single IPv4/IPv6, domain, URL, or hash (defanged forms accepted). Returns a verdict with event hits, threat level, and detection-flag status.
misp_lookup_iocs: Batch triage up to 20 indicators in one call with a compact per-IOC summary.
misp_correlate_ioc: Pivot from an IOC to find other indicators appearing in the same MISP event(s) — useful for discovering related infrastructure.

Event Investigation

misp_get_event: Fetch full details of a MISP event by ID (metadata, tags, attributes).
misp_search_events: Search events by title keyword, tag, and/or date range.

Attribute & Object Access

misp_get_attribute: Fetch a single attribute by ID along with its parent event.
misp_get_object: Retrieve a MISP object (group of related attributes) by ID.
misp_search_attributes: Search attributes by type, category, tag, to_ids status, or event ID.

Threat Intelligence Knowledge Base

misp_lookup_galaxy: Look up threat actors, malware families, tools, and ATT&CK techniques by name or synonym.
misp_list_galaxies: List all galaxy types available on the instance.
misp_list_taxonomies: View all taxonomies (TLP, kill-chain, PAP, etc.) and their enabled status.
misp_get_taxonomy: Retrieve a specific taxonomy's tags and their meanings.
misp_search_tags: Find tag definitions by name.

Feed & Instance Monitoring

misp_feed_stats: See feed counts and which are enabled.
misp_instance_status: Verify connectivity, authentication, and retrieve MISP/server versions.

Audit & Review

misp_review_submissions: Audit recent IOC submissions — what was added, by whom, when, and which are detection-flagged.

Indicator Submission (requires write-capable API key)

misp_submit_ioc: Add a single, fully attributed indicator with required fields (reporter, justification, last-seen date, tags, detection flag). Guardrails block private/reserved IPs and first-party infrastructure.
misp_submit_iocs: Bulk validate and add up to 50 indicators; defaults to dry_run=true so you can preview before committing.

All operations automatically clean defanged indicators (e.g., hxxp://evil[.]com, 1.2.3[.]4), and write operations enforce rate limiting and security guardrails.

misp-mcp connects MISP to any MCP client (Claude Desktop, Claude Code, Cursor, and others). You ask in plain language, the client calls MISP, you get the answer. No MISP UI, no REST calls by hand.

It exposes 21 tools: 19 read (indicators, events, feeds, the galaxy / taxonomy / tag knowledge base, warninglist checks, worker/job health) and 2 gated write (add indicators, single + bulk); a 22nd optional enrichment bridge registers only when TI_LOOKUP_URL is set. Every call runs under your own MISP key - the server holds no credential of its own.

How it works

flowchart LR
    C["MCP client<br/>Claude · Cursor · any"] -->|"X-MISP-Key: your key"| S["misp-mcp<br/>stdio or HTTP"]
    S -->|"read (19 tools)"| M[("your MISP")]
    S -->|"write (2 tools, gated)"| M
    S -. "optional (TI_LOOKUP_URL)" .-> E["enrichment service"]
    M -. "authorizes + attributes<br/>every call to you" .-> S

Your key is the credential. It rides in a header; MISP validates it on the real call and attributes the query to you. No shared account.
Read by default, writes gated. A read-only key can look things up; adding indicators needs a write-capable key (held by the security team).
Enrichment is optional. Set TI_LOOKUP_URL to bridge to a MISP-first enrichment service; unset, the tool stays hidden and this is a pure MISP client.

Related MCP server: misp-mcp

Get started

Two ways to use it. If you have your own MISP, run it locally (below). If your org already hosts misp-mcp, skip to Connect to a hosted server.

Run it locally

Your MCP client launches misp-mcp as a local process (stdio) that talks to your own MISP with your key. One user (you), nothing to host.

flowchart LR
    A["Your MCP client<br/>Claude Desktop/Code · Cursor"] -->|"launches (stdio)"| B["misp-mcp<br/>your key in env"]
    B -->|"HTTPS"| M[("your MISP")]

Where's your MISP? MISP_URL is your MISP's address, wherever it runs - a local Docker instance (https://localhost), one on your network (https://misp.lan), or a cloud-hosted one (https://misp.yourco.com). Only the URL changes. For a local or self-signed instance, also set MISP_VERIFY_TLS=false. misp-mcp just needs to be able to reach that URL - join your VPN first if the MISP is private.

Install it from source:
```
git clone https://github.com/indranilroy99/misp-mcp.git
cd misp-mcp
./install.sh
```
install.sh checks your environment, installs the misp-mcp binary, and can auto-write your client config. Manual steps are in ONBOARDING.md.
Point your client at it. Add a stdio server with two env vars - MISP_URL and your MISP_API_KEY. Claude Code, one command:
```
claude mcp add misp --scope user \
  -e MISP_URL=https://misp.example.com \
  -e MISP_API_KEY=YOUR_KEY_HERE \
  -- misp-mcp
```
Other clients: add an mcpServers entry running the misp-mcp command with those two env vars, then fully restart the app.
Try it. Ask your assistant "Is MISP healthy?" or "Look up 8.8.8.8 in MISP." If it answers from MISP, you're set.

Prefer Docker or a team deployment? See Host it for a team.

Connect to a hosted server

If your org runs misp-mcp behind a URL, there's nothing to install - point your client at it with your own key. You must be on the network / VPN that can reach it.

Get your MISP key (one time): open MISP → My Profile → Auth Keys → Add authentication key, comment it misp-mcp <your-name>, copy it (shown once). A read-only key is enough for lookups. Keep it private - every query runs as you.

Add the server - any MCP client that speaks streamable HTTP with custom headers works. It needs three things: transport http, the URL, and two headers.

{
  "mcpServers": {
    "misp": {
      "type": "http",
      "url": "https://misp.example.com/mcp",
      "headers": {
        "X-MISP-Key": "YOUR_KEY_HERE",
        "X-MISP-User": "you@example.com"
      }
    }
  }
}

Check it works: this should print 401 (endpoint reachable, auth required):

curl -s -o /dev/null -w '%{http_code}\n' -X POST https://misp.example.com/mcp

Claude Code (one terminal command):

claude mcp add --transport http misp https://misp.example.com/mcp \
  --scope user \
  --header "X-MISP-Key: YOUR_KEY_HERE" \
  --header "X-MISP-User: you@example.com"

Claude Desktop / Cursor / Windsurf - add the mcpServers block above to the client's MCP JSON config, then fully restart the app.

VS Code (Copilot MCP) - in .vscode/mcp.json or user settings, under "servers", use the same type/url/headers shape.

Cline / Continue / Zed / Goose and others - same URL, http transport, and the two X-MISP-* headers, in whatever config format the client uses. Any client that cannot send custom HTTP headers is not supported (the key must ride in X-MISP-Key).

MCP clients cache the tool list at connect time. If tools are wrong or the server was updated, fully quit and reopen the app (an in-app reconnect or a new chat is often not enough). Still stale: remove the misp server, save, reopen, add it back, reopen again.

Claude Code:

claude mcp remove misp
# then re-add (see above) and fully restart Claude Code

What you can ask

"Look up 102.130.113.9 in MISP."
"Triage these 30 IOCs from the report."
"What else showed up in the same event as evil[.]com?"
"Review the last 30 days of IOC submissions - who added what."
"Is MISP healthy? How many feeds are on?"

Paste indicators however you have them - defanged forms (1.2.3[.]4, hxxp://evil[.]com) are cleaned up automatically; private/reserved IPs are rejected. Behind the scenes a tool returns structured JSON, e.g. a lookup:

{
  "ioc": "102.130.113.9", "ioc_type": "ipv4", "total_hits": 6,
  "summary": { "seen_in_misp": true, "detection_flagged": true,
               "max_threat_level": "Medium", "restricted_hits": 0 },
  "hits": [ { "event_id": "16989", "event_info": "Tor exit nodes feed",
              "value": "102.130.113.9", "to_ids": true, "restricted": false } ]
}

Tools

Tool		What it does
`misp_lookup_ioc`	read	Sightings of one IPv4/IPv6, domain, URL, or hash, with a verdict
`misp_lookup_iocs`	read	Triage many indicators in one call
`misp_correlate_ioc`	read	Other indicators in the same event, for pivoting
`misp_get_event`	read	One event: info, tags, attributes
`misp_search_events`	read	Search events by title, tag, or date
`misp_feed_stats`	read	How many feeds exist and which are on
`misp_instance_status`	read	Reachability + auth check; run first when a tool fails
`misp_review_submissions`	read	Audit recent submissions: what was added, by whom
`misp_lookup_galaxy`	read	Threat actors, malware, tools, ATT&CK techniques by name or synonym
`misp_list_galaxies`	read	Galaxy types available on the instance
`misp_list_taxonomies`	read	Taxonomies (TLP, kill-chain, PAP) and whether each is enabled
`misp_get_taxonomy`	read	One taxonomy's tags and their meanings
`misp_search_tags`	read	Find tag definitions by name
`misp_get_object`	read	One MISP object (grouped attributes, e.g. a file object)
`misp_get_attribute`	read	One attribute by id, with its event
`misp_search_attributes`	read	Search attributes by type, category, tag, to_ids, or event (paginated)
`misp_check_warninglist`	read	Flag IOCs that hit known-good / noise lists (false-positive control)
`misp_worker_status`	read	Background worker / queue health (admin key)
`misp_jobs`	read	Recent background jobs + failures and why (admin key)
`misp_submit_ioc`	write	Add a new indicator (needs a write-capable key)
`misp_submit_iocs`	write	Bulk: validate + add many indicators (dry-run preview first)
`misp_enrich_ioc`	enrich	Optional: combined verdict via a MISP-first enrichment service (`TI_LOOKUP_URL`); may auto-record confirmed-bad IOCs

Security

Your key is the authorization. MISP checks it on every call and attributes the action to you. A read-only key cannot write; only write-capable keys can add indicators.
Guarded write path. Submissions are rate-limited, well-known / first-party infrastructure can never be submitted (anti-poisoning safelist), and the submitter is read from MISP itself, not a value the caller sets.
Fail-closed TLP. With server-side redaction on, an event whose tags can't be read is treated as restricted, never revealed.
Keys stay private. No shared key on the server; the key rides in a header over TLS. Logs never contain keys or IOC values.

Report a vulnerability privately: SECURITY.md.

Host it for a team

Run misp-mcp as an HTTP server so a whole team can use it, each with their own MISP key. It holds no credential - every request carries the caller's X-MISP-Key, which MISP validates and attributes.

flowchart LR
    U1["Analyst A"] --> LB
    U2["Analyst B"] --> LB
    LB["TLS proxy / load balancer<br/>ingress: your VPN CIDRs only"] -->|"HTTP :8080 (private)"| S["misp-mcp (HTTP)<br/>no stored key"]
    S -->|"HTTPS"| M[("your MISP")]

Run it somewhere that can reach your MISP - the same VPC/network if your MISP is cloud-hosted or private, or alongside it (set MISP_URL to its address, as above). TLS terminates at the load balancer; misp-mcp serves plain HTTP on :8080 behind it (or give the process its own cert). Keep ingress scoped to your caller networks - the endpoint is not public. Pick a path:

Path	Use it for	Guide
Docker	Fastest single host	see below
Self-host (VM + systemd)	A team, your own box	DEPLOY.md
Cloud (AWS / GCP / Azure)	Any provider, hand steps	CLOUD.md
AWS Terraform	One `terraform apply`, ALB + TLS	deploy/terraform/

Docker (bind stays on localhost; front it with your own TLS proxy for remote use - the key is a bearer credential):

docker run -d -p 127.0.0.1:8080:8080 \
  -e MCP_TRANSPORT=http -e MCP_HOST=0.0.0.0 \
  -e MISP_URL=https://misp.example.com \
  -e MISP_MCP_ALLOW_INSECURE_BIND=true \
  ghcr.io/indranilroy99/misp-mcp:latest
# or: MISP_URL=https://misp.example.com docker compose up -d

The Terraform modules ship two flavors sharing one networking module: Fargate (serverless, no VM) or EC2 (managed VM, SSM access), each behind an internal ALB with TLS.

Setting	Mode	Default	Meaning
`MISP_URL`	both	required	MISP base URL
`MISP_API_KEY`	local	required	your key (local/stdio mode)
`MCP_TRANSPORT`	both	`stdio`	`stdio` for local, `http` for hosted
`MCP_HOST`	hosted	`127.0.0.1`	bind address
`MCP_PORT`	hosted	`8080`	port
`MISP_VERIFY_TLS`	both	`true`	set `false` only for a self-signed lab
`MISP_MCP_SHOW_RESTRICTED`	both	`true`	`false` turns on server-side TLP hiding
`MISP_SUBMISSION_EVENT_ID`	both	required for writes	event that `misp_submit_ioc` writes to
`MISP_MCP_PROTECTED_DOMAINS`	both	empty	your own domains that can never be submitted
`MISP_MCP_SUBMIT_RATE`	both	`20`	max submissions per key per minute
`MISP_MCP_KEYID_SECRET`	both	random	HMAC secret for the internal key-id (rate-limit/log). Set it to keep ids stable across restarts/replicas; unset uses a per-process random secret
`MISP_MCP_TLS_CERT` / `MISP_MCP_TLS_KEY`	hosted	none	serve HTTPS directly
`MISP_MCP_ALLOW_INSECURE_BIND`	hosted	`false`	allow a public plain-HTTP bind (TLS on a proxy)
`TI_LOOKUP_URL`	both	unset	optional enrichment endpoint (enables `misp_enrich_ioc`)
`TI_LOOKUP_TIMEOUT`	both	`30`	seconds to wait on the enrichment endpoint (floor 5)

python3 -m venv .venv
.venv/bin/pip install -e '.[dev]'
.venv/bin/python -m pytest tests/ -q            # full suite, fully offline

misp_mcp/
  server.py      the tools and the MCP server
  client.py      talks to the MISP REST API (read + write)
  config.py      reads settings from the environment
  http_app.py    hosted mode: header auth + web server
  context.py     carries your identity through one request
  validators.py  cleans, checks, and safelists indicators

Dependencies are pinned in pyproject.toml: mcp, httpx, pydantic, uvicorn, starlette. Licensed under Apache-2.0 (LICENSE). Contributions welcome - see CONTRIBUTING.md.

Available Tools

10 tools

misp_correlate_iocA

Read-onlyIdempotent

List other indicators that appear in the same MISP event(s) as the given IOC - useful for pivoting from one indicator to related infrastructure (an event's other IPs, domains, hashes).

Returns JSON: {"ioc": str, "events_checked": int, "related": [{"event_id", "event_info", "attribute_type", "value"}]}. Attributes from TLP:AMBER/RED events are skipped entirely unless the operator has opted in to restricted content.

Inputs: params (required). Returns: result

misp_feed_statsA

Read-onlyIdempotent

Summarize the instance's threat feeds.

Returns JSON: {"total": int, "enabled": int, "enabled_feeds": [{"id", "name", "provider"}]}.

Inputs: no named parameters. Returns: result

misp_get_eventA

Read-onlyIdempotent

Fetch one MISP event by numeric ID: metadata, tags, and its attributes (up to max_attributes).

Returns JSON: {"id", "info", "date", "threat_level", "analysis", "creator_org", "tags": [str], "attribute_count": int, "attributes": [{"type", "value", "category", "to_ids"}]}. If the event is TLP:AMBER/RED (or its tags cannot be read) and the operator has not opted in, only {"id", "restricted": true, "note"} is returned.

Inputs: params (required). Returns: result

misp_instance_statusA

Read-onlyIdempotent

Check that MISP is reachable with the configured key and report both the MISP version and this server's version - a connectivity/auth smoke test to run first when other tools fail.

Returns JSON: {"reachable": bool, "misp_version": str, "server_version": str} or an error string explaining what to fix (key, network/VPN).

Inputs: no named parameters. Returns: result

misp_lookup_iocA

Read-onlyIdempotent

Search MISP for sightings of an indicator (IP, domain, URL, or file hash).

Returns JSON: {"ioc", "ioc_type", "total_hits", "summary": {"seen_in_misp", "event_count", "detection_flagged", "max_threat_level", "restricted_hits"}, "hits": [{"event_id", "event_info", "threat_level", "source_org", "attribute_type", "value", "category", "to_ids", "restricted", and when present "comment"/"first_seen"/"last_seen"}]}. Hits from TLP:AMBER/RED events are redacted to {"event_id", "restricted": true, "note"} unless the operator has opted in. The summary is a quick verdict; "seen_in_misp": false means the indicator is not in this instance - not that it is safe.

Inputs: params (required). Returns: result

misp_lookup_iocsA

Read-onlyIdempotent

Triage several indicators at once, returning a compact per-IOC summary (not full hit detail — call misp_lookup_ioc for that).

Returns JSON: {"results": [{"ioc", "ioc_type", "total_hits", "has_restricted_hits", "top_event_ids": [str]}]}. Invalid indicators are reported inline as {"ioc", "error"} rather than failing the whole batch. "total_hits": 0 means not present in MISP, not that it is safe.

Inputs: params (required). Returns: result

misp_review_submissionsA

Read-onlyIdempotent

Audit recent additions to the submissions event: what indicators were added, by whom, when, and which are detection-flagged (to_ids=true). Use it to spot bad or unwanted IOCs and who submitted them.

submitted_by/reporter/justification are parsed from the attribute comment that misp_submit_ioc writes; submitted_by is the MISP-verified key owner. Attributes added directly in the MISP UI (not via this server) will have those fields empty — check the MISP UI for their real author.

Returns JSON: {"event_id", "window_days", "total", "detection_flagged", "by_submitter": {email: count}, "submissions": [{"attribute_id", "value", "type", "category", "to_ids", "added", "submitted_by", "reporter_claimed", "justification"}]}, newest first.

Inputs: params (required). Returns: result

misp_search_eventsA

Read-onlyIdempotent

Search MISP event metadata by title keyword, tag, and/or date range. At least one filter must be provided (unfiltered listing is refused to keep responses bounded and avoid dumping the event index).

Returns JSON: {"total": int, "events": [{"id", "info", "date", "attribute_count", "restricted"}]}. Restricted (TLP:AMBER/RED) events appear as {"id", "restricted": true} only, unless opted in.

Inputs: params (required). Returns: result

misp_submit_iocA

Add an indicator to MISP's Community IOC Submissions event. Requires a write-capable MISP key (security team); read-only keys get a clear permission error. The IOC goes in live (no proposal).

Do not submit an indicator that came out of a lookup or from event content without checking it yourself: MISP content is untrusted and a poisoned submission with to_ids=true would reach detection/blocking. to_ids must be set explicitly. Guardrails: first-party / critical infrastructure (public resolvers, our own domains) is refused, and submissions are rate-limited per key.

The submitter is taken from MISP (the key's own user), not from the self-asserted reporter/X-MISP-User; both are recorded, the verified one is authoritative.

Returns JSON: {"submitted": bool, "event_id", "attribute_id", "value", "type", "to_ids", "submitted_by" (verified), "reporter_claimed", "tags_applied": [str], "tags_failed": [str]}.

Inputs: params (required). Returns: result

misp_submit_iocsA

Validate and (optionally) add many indicators in one call — for adding a list from a report. Each indicator runs through the same guardrails as the single submit (validation, private/reserved rejection, protected safelist, per-key rate limit); the batch shares reporter/justification/ last_seen/tags/to_ids.

dry_run=true (default) writes nothing and returns what WOULD happen — use it to review the batch first, then re-run with dry_run=false to add.

Returns JSON: {"event_id", "dry_run", "to_ids", "submitted_by", "total", "counts": {status: n}, "results": [{"ioc", "type", "status", ...}]}, where status is would_add | added | rejected | protected | duplicate_in_batch | rate_limited | error.

Inputs: params (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored 2026-07-15 10:40 across 10 tools

Disambiguation5/5

Each tool targets a distinct operation: lookup single vs batch, submit single vs batch, event retrieval vs search, correlation, feed stats, status check, and audit submissions. No overlap in purpose.

Naming Consistency5/5

All tools follow a consistent `misp_<verb>_<object>` pattern in snake_case (e.g., `misp_lookup_ioc`, `misp_submit_iocs`). Singular/plural variations are appropriate for batch operations.

Tool Count5/5

10 tools cover the core MISP IOC operations (lookup, submit, correlate) plus event reading, feed stats, and status checks. The count is well-scoped for a focused threat intelligence server.

Completeness4/5

Core workflows (IOC lookup, submission, correlation, event retrieval) are covered. Minor gaps like tag management or event creation for general use are missing but not critical for the server's apparent purpose.

Maintenance

ActivityInactive

ResponsivenessNo recent community issues

Resources

Related MCP Connectors

DacticA
io.dactic
Connect AI clients to your Dactic work context through a hosted MCP service.
Workplace & Productivity Project Management
341
https://mcp.app.dactic.io/mcp
Crimson Crawler
com.crimsoncrawler
Enrich, search, assess, and manage threat intelligence through 80+ typed MCP tools.
Security Search Research & Data
1
https://crimsoncrawler.com/mcp/v1
Midkernel Threat IntelA
com.midkernel
Free, read-only public-source threat intel over MCP. No account or API key.
Security Open Data Research & Data
61
https://www.midkernel.com/security/app/mcp/threat-intel
mcp-server
com.pentest-tools
MCP server for Pentest-Tools.com: run scans, manage findings and reports via your preffered LLM.
Penetration Testing Security
24
https://mcp.pentest-tools.com/mcp

Related MCP Servers

MISP-MCP-SERVER
Security Monitoring Search
bornpresident
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.
Updated 2 years ago (2025-04-09 06:26 UTC)
13
-
misp-mcp
Security Search Research & Data
lidless-labs
A
license
A
quality
B
maintenance
An MCP server that enables LLMs to interact with MISP for threat intelligence sharing, IOC lookups, and event management. It provides tools for investigating indicators, discovering correlations, and exporting intelligence in formats like STIX and Suricata.
Updated 17 days ago (2026-10-29 05:28 UTC)
36
33 npm
2
MIT
MISP MCP Server
Security Search
DarkAngel-agents
F
license
Not graded
quality
D
maintenance
A Model Context Protocol server that connects AI assistants to MISP threat intelligence platforms. It enables threat intelligence search, IOC lookup, and event analysis through natural conversation.
Updated 7 months ago (2026-04-21 00:29 UTC)
-
UltraProbe
Databases Security
ppcvote
A
license
A
quality
C
maintenance
MISP (Malware Information Sharing Platform) MCP server with built-in prompt injection defense via prompt-defense-audit
Updated 13 days ago (2026-11-02 14:43 UTC)
8
2
MIT

Appeared in Searches

Mantis Zugriff - Access and Login Information for Mantis Bug Tracker

How it works

Get started

Run it locally

Connect to a hosted server

What you can ask

Tools

Security

Host it for a team

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

MISP-MCP-SERVER

misp-mcp

MISP MCP Server

UltraProbe

Appeared in Searches