All servers / Security / Security Detections MCP server
Security Detections MCP server
Advanced MCP server for security detections with Detection Engineering Intelligence, Knowledge Graph (Tribal Knowledge), Elicitation, and Resource Subscriptions
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 3.3.4. Package: security-detections-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.3 seconds including download)
- Tools offered: 81
- Last published: 2026-11-04
- Weekly downloads (npm): 977
- License: Apache-2.0 · Direct dependencies: 4
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
search3 of 3 parameters describedFull-text search across all detection fields (name, description, query, MITRE IDs, tags, CVEs, analytic stories, process names, file paths, registry paths)
get_by_id2 of 2 parameters describedGet a single detection by its ID
get_raw_yaml2 of 2 parameters describedGet the original YAML content for a detection
list_all2 of 2 parameters describedList all detections with pagination. Use for browsing the detection index.
list_by_source3 of 3 parameters describedList detections filtered by source type
list_by_mitre3 of 3 parameters describedList detections that map to a specific MITRE ATT&CK technique
list_by_logsource5 of 5 parameters describedList Sigma detections filtered by logsource (category, product, or service)
list_by_severity3 of 3 parameters describedList detections filtered by severity level
list_by_cve3 of 3 parameters describedList detections that cover a specific CVE vulnerability
list_by_analytic_story3 of 3 parameters describedList Splunk detections that belong to a specific analytic story (e.g., "Ransomware", "Data Destruction")
list_by_process_name3 of 3 parameters describedList detections that reference a specific process name (e.g., "powershell.exe", "w3wp.exe", "cmd.exe")
list_by_detection_type3 of 3 parameters describedList detections by type (TTP, Anomaly, Hunting, Correlation)
list_by_data_source3 of 3 parameters describedList detections that use a specific data source (e.g., "Sysmon", "Windows Security", "process_creation")
list_by_mitre_tactic3 of 3 parameters describedList detections by MITRE ATT&CK tactic (e.g., "execution", "persistence", "credential-access")
list_by_kql_category3 of 3 parameters describedList KQL detections filtered by category (e.g., "Defender For Endpoint", "Azure Active Directory", "Threat Hunting")
list_by_kql_tag3 of 3 parameters describedList KQL detections filtered by tag (e.g., "ransomware", "hunting", "ti-feed")
list_by_kql_datasource3 of 3 parameters describedList KQL detections that use a specific Microsoft data source (e.g., "DeviceProcessEvents", "SigninLogs", "EmailEvents")
get_statsno parametersGet statistics about the indexed detections and stories
get_technique_ids3 of 3 parameters describedGet ONLY unique MITRE technique IDs (lightweight - no full detection data). Use this for Navigator layer generation or coverage analysis.
analyze_coverage1 of 1 parameter describedGet coverage analysis with stats by tactic, top covered techniques, and weak spots. Returns summary data, not raw detections. Use this instead of listing detections and processing manually.
identify_gaps2 of 2 parameters describedIdentify detection gaps based on a threat profile (ransomware, apt, initial-access, persistence, credential-access, defense-evasion). Returns prioritized gaps with recommendations.
suggest_detections2 of 2 parameters describedGet detection suggestions for a specific technique. Returns existing detections, required data sources, and detection ideas.
generate_navigator_layer5 of 5 parameters describedGenerate a MITRE ATT&CK Navigator layer JSON from detection coverage. Returns valid Navigator JSON ready for import at https://mitre-attack.github.io/attack-navigator/. Filter by source, tactic, or severity.
analyze_procedure_coverage3 of 3 parameters describedAnalyze procedure-level coverage for a MITRE technique. Goes beyond "we cover T1059.001" to show WHICH specific behaviors/procedures your detections actually catch (e.g., encoded commands, download cradles, AMSI bypass). Shows covered and uncovered procedures with detection names.
compare_procedure_coverage2 of 2 parameters describedCompare procedure-level detection coverage across sources for a technique. Shows which source catches which specific behaviors — two orgs can both tag T1059.001 but detect completely different procedures. Returns a matrix of source × procedure.
get_detection_list3 of 3 parameters describedGet a lightweight list of detection names and IDs matching a search query. Returns ONLY name, id, source, mitre_ids - no queries or raw yaml. Use this when you need a simple list.
compare_sources2 of 2 parameters describedCompare detection coverage between sources (Sigma vs Splunk vs Elastic vs KQL) for a topic. Returns a clean breakdown with counts and names per source.
count_by_source1 of 1 parameter describedGet quick counts of detections by source for a topic. Returns just the numbers, no detection details.
list_by_name_pattern2 of 2 parameters describedList detections whose NAME matches a pattern, grouped by source. Returns just name + ID pairs.
smart_compare1 of 1 parameter describedCompare detections across sources, tactics, or techniques for a given topic. Returns breakdown by source, tactic, and severity.
get_coverage_summary1 of 1 parameter describedGet a lightweight coverage summary (~200 bytes) with tactic percentages. Use this for quick overviews instead of full analyze_coverage.
get_top_gaps1 of 1 parameter describedGet just the top 5 gaps (~300 bytes) for a threat profile. Use this for quick gap checks.
get_technique_count1 of 1 parameter describedGet just the detection count for a technique (~50 bytes). Use this for quick coverage checks.
analyze_actor_coverage3 of 3 parameters describedAnalyze detection coverage against a specific threat actor. Shows which of the actor's known MITRE ATT&CK techniques have detections, coverage percentage, and prioritized gaps. Requires STIX data (ATTACK_STIX_PATH env var).
list_actors2 of 2 parameters describedList all known MITRE ATT&CK threat actors with aliases and technique counts. Requires STIX data (ATTACK_STIX_PATH env var).
compare_actor_coverage2 of 2 parameters describedCompare detection coverage across multiple threat actors. Shows shared technique gaps and unique risks per actor. Requires STIX data (ATTACK_STIX_PATH env var).
get_actor_profile1 of 1 parameter describedGet full threat actor dossier: description, aliases, known techniques, software employed, and detection coverage status. Requires STIX data (ATTACK_STIX_PATH env var).
search_stories2 of 2 parameters describedSearch analytic stories by narrative, description, or name. Stories provide rich context about threat campaigns and detection strategies.
get_story1 of 1 parameter describedGet detailed information about a specific analytic story by name
list_stories2 of 2 parameters describedList all analytic stories with pagination
list_stories_by_category3 of 3 parameters describedList analytic stories by category (e.g., "Malware", "Adversary Tactics", "Abuse")
save_query4 of 4 parameters describedSave a query result for quick retrieval later. Useful for caching frequently needed data.
get_saved_query1 of 1 parameter describedRetrieve a previously saved query result by name.
list_saved_queries1 of 1 parameter describedList all saved queries, optionally filtered by type.
rebuild_index2 of 2 parameters describedForce re-index all detections and stories from configured paths. WARNING: This is a destructive operation that deletes the current index.
save_template3 of 3 parameters describedSave a reusable query template with {{placeholders}}. Templates can contain SQL queries or tool-chain definitions for future execution.
run_template2 of 2 parameters describedExecute a saved query template with the provided parameters. Returns the query results.
list_templates2 of 2 parameters describedList all saved query templates with their names, descriptions, and usage statistics.
get_template1 of 1 parameter describedGet the full details of a saved query template including the template string and parameters.
delete_template1 of 1 parameter describedDelete a saved query template by name.
create_table3 of 3 parameters describedCreate a new custom table to store analysis data. Use this to persist findings, research results, or any structured data you want to retrieve later. Pre-built tables available: gap_analyses, source_comparisons, threat_actor_profiles, detection_recommendations
insert_row3 of 3 parameters describedInsert a row of data into a dynamic table. Data is validated against the table schema.
query_table6 of 6 parameters describedQuery data from a dynamic table with optional filtering, sorting, and pagination. Filter examples: - Exact match: {"status": "completed"} - LIKE match: {"name": "%ransomware%"} - Multiple conditions: {"status": "pending", "priority": "high"}
list_tables1 of 1 parameter describedList all dynamic tables created by the LLM, including pre-built analysis tables and their statistics.
drop_table2 of 2 parameters describedRemove a dynamic table and all its data. Use with caution - this is irreversible.
describe_table1 of 1 parameter describedGet detailed schema information and statistics for a dynamic table.
create_entity2 of 2 parameters describedCreate a knowledge entity representing a security concept. Use this to build the knowledge graph with threat actors, techniques, detections, campaigns, tools, vulnerabilities, and data sources. Entity types: - threat_actor: APT groups, criminal gangs (e.g., "APT29", "STORM-0501") - technique: MITRE ATT&CK techniques (e.g., "T1059.001 PowerShell") - detection: Security detection rules (e.g., "Suspicious PowerShell Execution") - campaign: Attack campaigns (e.g., "SolarWinds Compromise") - tool: Attack tools or malware (e.g., "Cobalt Strike", "Mimikatz") - vulnerability: CVEs (e.g., "CVE-2024-1234") - data_source: Log sources (e.g., "Windows Security Events")
create_relation5 of 5 parameters describedCreate a relationship between two entities WITH reasoning explaining WHY they're connected. This is the core of tribal knowledge - capturing not just the connection but the insight behind it. Relation types: - uses: Threat actor uses technique/tool (e.g., APT29 uses Cobalt Strike) - targets: Threat actor targets sector/system - detects: Detection covers technique - covers: Detection provides coverage for technique - mitigates: Control mitigates technique - exploits: Campaign exploits vulnerability - attributed_to: Campaign attributed to threat actor - depends_on: Detection depends on data source - related_to: General relationship IMPORTANT: The reasoning field is critical - explain WHY this connection exists.
add_observation4 of 4 parameters describedAdd a fact or observation about an entity. Observations capture point-in-time knowledge that can be queried later. Examples: - "APT29 has been active since at least 2008" - "This detection has high false positives in development environments" - "T1059.001 is commonly used for initial access in ransomware"
delete_entity1 of 1 parameter describedRemove an entity from the knowledge graph. This also removes all relations and observations associated with the entity.
delete_observation1 of 1 parameter describedRemove a specific observation by its ID. Use open_entity first to find observation IDs.
search_knowledge2 of 2 parameters describedSearch across all knowledge types: entities, relations, observations, decisions, and learnings. Uses full-text search to find relevant tribal knowledge. Search examples: - "PowerShell execution" - Find everything related to PowerShell - "credential theft" - Find credential-related knowledge - "APT29" - Find all knowledge about this threat actor
read_graph2 of 2 parameters describedRead the entire knowledge graph or a filtered subgraph. Returns entities, relations, and observations. Use this to: - Get an overview of all stored knowledge - Filter by entity type to focus on specific concepts - Understand the structure of captured tribal knowledge
open_entity1 of 1 parameter describedGet complete information about a specific entity including all its relations and observations. This is the detailed view of a single knowledge node.
log_decision7 of 7 parameters describedRecord WHY a significant decision was made. This is the gold of tribal knowledge - capturing the reasoning process so future agents can understand past decisions. Decision types: - gap_identified: A detection gap was found - detection_recommended: A specific detection was recommended - coverage_mapped: Coverage was analyzed and mapped - priority_assigned: A priority decision was made - false_positive_tuning: FP tuning recommendation - threat_assessment: Threat level assessment - data_source_selected: Data source was chosen IMPORTANT: Be detailed in the reasoning - this helps future analysis.
add_learning5 of 5 parameters describedStore a pattern or insight derived from analysis for future reference. Learnings are reusable knowledge that can help future sessions. Learning types: - detection_pattern: A pattern for writing effective detections - gap_pattern: A recurring type of detection gap - user_preference: User preferences for analysis style - false_positive_pattern: Common FP patterns to avoid - threat_pattern: Recurring threat behaviors - correlation_insight: Insights about technique correlations - data_quality_insight: Insights about data source quality Examples: - "STORM-0501 consistently uses native tools before deploying ransomware" - "Detections for T1059.001 need process parent filtering to reduce FPs" - "User prefers prioritizing detections by MITRE tactic stage"
get_relevant_decisions4 of 4 parameters describedGet past decisions relevant to the current context. Uses full-text search to find tribal knowledge that applies to your current analysis. Use this to: - See how similar situations were handled before - Understand reasoning behind past recommendations - Maintain consistency with previous decisions
get_learnings4 of 4 parameters describedGet applicable learnings for the current task. Returns patterns and insights that may help with the current analysis. Use this to: - Apply proven patterns to new situations - Remember user preferences - Avoid known pitfalls
auto_analyze_coverage4 of 4 parameters describedAutomatically analyze detection coverage, identify gaps across threat profiles, and store findings for future reference. This tool: 1. Runs coverage analysis across all detections 2. Identifies gaps for specified threat profiles (ransomware, apt, etc.) 3. Stores results in the gap_analyses dynamic table 4. Logs decisions about significant findings in the knowledge graph Use this for comprehensive, stored analysis that persists across sessions.
auto_gap_report5 of 5 parameters describedGenerate a comprehensive gap report comparing detection coverage across sources (Sigma, Splunk ESCU, Elastic, KQL) and threat profiles. This tool: 1. Analyzes all threat profiles for gaps 2. Compares detection coverage across different sources 3. Creates prioritized recommendations based on severity and coverage 4. Stores the complete report in dynamic tables Use this for executive-level reporting on detection posture.
auto_compare_sources4 of 4 parameters describedAutonomously compare detection coverage across different sources (Sigma, Splunk ESCU, Elastic, KQL) with detailed reasoning and analysis. This tool: 1. Compares detection counts and coverage across all available sources 2. Analyzes technique-level coverage differences between sources 3. Identifies which source has best coverage for specific tactics/techniques 4. Provides reasoned recommendations for source selection 5. Stores comparison results and logs decision reasoning Use this to understand the strengths/weaknesses of different detection sources and make informed decisions about which to use.
llm_enhanced_analysis4 of 4 parameters describedRequest LLM-enhanced analysis of security detection data using MCP sampling. This tool leverages MCP sampling to request the client's LLM to analyze security data with expert reasoning. Unlike the auto_* tools that perform direct analysis, this tool asks the LLM to provide contextual insights. Note: Requires client to support MCP sampling capability. If not supported, falls back to structured data output. Use cases: - Get expert reasoning about coverage gaps - Generate detection recommendations with context - Compare sources with nuanced analysis - Understand threat profile implications
check_sampling_statusno parametersCheck if MCP sampling is available for LLM-enhanced analysis. Sampling allows the server to request LLM completions from the client, enabling richer autonomous analysis. Not all MCP clients support this feature. Use this tool to check capability before using llm_enhanced_analysis.
get_query_patterns2 of 2 parameters describedGet common query patterns for a MITRE technique based on existing detections. Returns SPL structure, common fields, macros used, and example queries. Use this before writing a detection to learn the conventions.
get_field_reference1 of 1 parameter describedGet available fields for a Splunk data model with usage examples. Use this to understand what fields are available when writing a detection query.
get_macro_reference1 of 1 parameter describedGet common Splunk macros and their usage patterns. Essential for writing detections that follow repository conventions.
find_similar_detections4 of 4 parameters describedFind existing detections similar to what you want to create. Use this to learn from existing detection logic and structure.
suggest_detection_template5 of 5 parameters describedGenerate a detection template based on technique, learned patterns, and conventions. Returns YAML structure ready for customization.
generate_rba_structure4 of 4 parameters describedGenerate RBA (Risk-Based Alerting) structure for a detection based on learned patterns and best practices.
extract_patterns1 of 1 parameter describedExtract and store patterns from all indexed detections. Run this to populate the pattern database for template generation.
learn_from_feedback4 of 4 parameters describedStore user preference or correction to improve future suggestions. Call this when user modifies generated content to build tribal knowledge.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.