agentic-misp-mcp
Related Servers
Alternatives to agentic-misp-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with MISP threat intelligence platforms through natural language, supporting event search, creation, user management, and report generation.12-
- AlicenseAqualityAmaintenanceAn 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.3610 npm2MIT
- FlicenseNot gradedqualityDmaintenanceProvides real-time threat intelligence for AI agents, enabling checks on IPs, domains, URLs, hashes, CVEs, prompt-injection payloads, and malicious AI-skill/MCP-tool definitions against a free database of 890K+ IOCs.-
- FlicenseNot gradedqualityDmaintenanceA 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.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform security alert triage by ingesting raw logs, extracting IOCs, querying threat intelligence sources, and generating structured NIST/MITRE assessments with reasoning traces.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query and manage OpenCTI threat intelligence data, including indicators, observables, reports, malware, and more, with read-only and optional write operations.MIT
TDQS
Scored across 25 tools
Several tools have fuzzy boundaries: summarize_event, explain_event_context, generate_event_report, and generate_markdown_event_report all produce event interpretations/reports, and IOC investigation/report generation tools overlap heavily. Descriptions differentiate them somewhat, but an agent could easily select the wrong report or investigation tool.
All tool names follow a consistent snake_case verb_noun pattern, with a clear with_approval suffix on write operations and consistent prefixes like get_, search_, generate_, propose_, and find_. The naming is predictable and uniform despite the large tool count.
25 tools sits at the heavy end of the acceptable range. The breadth is justified by MISP's read/analysis/reporting and approval-gated write workflows, but the many near-duplicate reporting and investigation tools make the set feel larger and more redundant than necessary.
The read, search, analysis, and feed-health side is well covered, and approval-gated write tools exist for publishing, tagging, sightings, and IOC submission. However, there is no real create/update/delete event or attribute lifecycle beyond proposals and IOCs, leaving notable workflow gaps for an agent trying to manage MISP data end-to-end.