F
licenseNot graded
qualityD
maintenanceEnables AI assistants to interact with MISP threat intelligence platforms through natural language, supporting event search, creation, user management, and report generation.
12
-
agentic-misp-mcp
by hdyrawan
Related Servers
Alternatives to agentic-misp-mcp
No user-submitted related servers found.
Related Servers
- 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.3611 npm2MIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents access to the VirusTotal v3 API so they can analyze files, URLs, IPs, and domains and return detection reports alongside pivotable relationships such as contacted hosts, dropped files, and resolutions. It also supports corpus searches, sandbox behaviour summaries, threat-actor and malware-family collections, and cursor-based paging across 100+ relationship types.MIT
- 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 assistants to search and retrieve threat-intelligence collections—including leaks, malware, attacks, suspicious IPs, threats, and group profiles—through indicator queries, filtered pagination, update tracking, and WHOIS enrichment.Apache 2.0
TDQS
C2.7/5.0
Scored across 25 tools
Disambiguation2/5
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.
Naming Consistency5/5
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.
Tool Count3/5
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.
Completeness3/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues