← Back to directory
C

Crowdsentinel MCP Server

Community
AI-powered threat hunting & incident response MCP server for Elasticsearch/OpenSearch.
GitHub source repository ↗
★ 206 Stars Category · Database Very popular Source revision bfca612f4672
59FMRS · C
Reliability
8/20
Security and permissions
12/20
Maintenance
13/20
Documentation
12/20
Setup experience
14/20

CrowdSentinel MCP Server provides comprehensive AI-driven threat hunting and incident response capabilities for Elasticsearch/OpenSearch, with a rich set of tools, extensive detection rules, and multi-source integration. However, its development status, security configuration defaults, and potential sensitive data access make it better suited for research and testing environments rather than production.

Read the FMRS scoring method →

CrowdSentinel MCP Server is an open-source threat hunting orchestrator that connects large language models to enterprise security data via the Model Context Protocol (MCP). It provides 139 MCP tools for natural language threat hunting, detection rule execution (6,060 built-in rules), endpoint forensics (Velociraptor), host forensics (osquery), EVTX log analysis (Chainsaw), and PCAP network analysis (Wireshark). It supports multiple security frameworks (Cyber Kill Chain, Pyramid of Pain, Diamond Model, MITRE ATT&CK) and features persistent investigation state, cross-tool IoC correlation, and encoded-command deobfuscation. The server is intended for security testing, research, and educational purposes only, and is not production-ready.

Tools

The tool list has not been reviewed yet.

Setup

Install via pip: pip install crowdsentinel-mcp-server. Run 'crowdsentinel setup' to download detection rules and tools. Set environment variables (ELASTICSEARCH_HOSTS, etc.) and run the server via uvx. Optional extras: velociraptor and deobf. For standard MCP clients use stdio transport; for web clients use SSE or HTTP.

claude_desktop_config.json
{
  "mcpServers": {
    "crowdsentinel": {
      "command": "uvx",
      "args": [
        "crowdsentinel-mcp-server"
      ],
      "env": {
        "ELASTICSEARCH_HOSTS": "https://localhost:9200",
        "ELASTICSEARCH_API_KEY": "your_api_key",
        "VERIFY_CERTS": "false"
      }
    }
  }
}

Fit and risk

Best for

  • Security analysts conducting threat hunting in Elasticsearch or OpenSearch environments
  • Incident responders needing AI-assisted investigation workflows
  • Red teams/security testers analyzing attack simulation data
  • Researchers using cyber range environments like crowdsentinel-range

Not for

  • Production environments (explicitly warned not for production)
  • Users without security background (targets DFIR professionals)
  • Users needing Splunk integration (still on roadmap)
  • Users relying on a single data source (integrates with multiple)

Required permissions

  • Requires Elasticsearch/OpenSearch credentials (API key or username/password)
  • Can read and write Elasticsearch indices (can be restricted via DISABLE_HIGH_RISK_OPERATIONS)
  • Optional API keys for external threat intelligence services (VirusTotal, Shodan, etc.)
  • Requires local system permissions to run tools like osquery and tshark
  • Requires Velociraptor API configuration for endpoint forensics

Risks and side effects

  • High-risk operations: can create/delete indices, documents, data streams, and aliases
  • Potential sensitive data exposure: searches may return documents containing PII or sensitive security data
  • TLS verification disabled by default (VERIFY_CERTS default false), risk of man-in-the-middle attacks
  • External service dependencies: requires access to threat intelligence APIs, may incur costs or rate limits
  • Active development status: APIs may change, not suitable for production

Troubleshooting

  1. Ensure ELASTICSEARCH_HOSTS or ELASTICSEARCH_CLOUD_ID is set
  2. Verify credentials are correct (API key or username/password)
  3. If using self-signed certificates, set VERIFY_CERTS to true and configure ELASTICSEARCH_CA_CERT
  4. Run 'crowdsentinel doctor' to check configuration readiness
  5. For system dependencies (like tshark), ensure they are installed
  6. For Velociraptor, set the VELOCIRAPTOR_API_CONFIG environment variable

Use cases

Search Elasticsearch for threats using natural language
Execute detection rules and map MITRE ATT&CK techniques
Collect endpoint forensic artifacts using Velociraptor
Analyze PCAP files for C2 beaconing
Hunt EVTX logs with Chainsaw and Sigma rules
Correlate IoCs across SIEM and endpoint sources

Supported clients

Claude CodeFull support
Claude DesktopFull support
VS Code CopilotFull support
CursorFull support
Roo CodeFull support
5ireFull support