netwitness-mcp-server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
netwitness-mcp-server
A Model Context Protocol (MCP) server that lets an LLM agent (Claude, or any other MCP-compatible client) query a NetWitness environment directly — sessions, meta values, alerts, and incidents — through natural-language requests instead of hand-written queries against the NetWitness UI or REST API.
Built against the NetWitness home lab described in my other repos, mainly to answer a practical question: can an agent actually reason usefully about detection/response data if it's given the right tools, instead of just a raw API wrapper? This is the tool layer that lets it try.
See INSTALL.txt for setup.
What it exposes
Nine tools, each returning a consistent JSON envelope (status, tool,
query, data, metadata, error) so a calling agent can parse results
predictably instead of guessing at response shape:
Tool | Purpose |
| Query session/packet metadata from a Concentrator or Broker |
| List distinct values for a given meta key |
| Query alerts by criteria |
| List available meta keys and their descriptions |
| Return NetWitness query syntax reference |
| Query incidents from the Admin Server / Respond module |
| Get alerts tied to a specific incident |
| Change an incident's status |
| Add a journal entry to an incident |
| Check if an IP, domain, or URL is in threat feeds and has appeared in sessions/incidents |
Related MCP server: CrowdSentinel MCP Server
lookup_indicator — indicator pivot tool (v2)
lookup_indicator(value, value_type) answers one question in a single
call: is this IP, domain, or URL in my threat feeds, has it shown up in
traffic, and is it linked to any open incidents? value_type is one of
ip, domain, or url.
It checks:
Threat feeds — cross-references the URLhaus and Feodo Tracker feeds (see
homelab-iac/threat-intel) over NetWitness's retention windowSession activity — whether the indicator has appeared in network sessions recently, with first/last-seen timestamps
Linked incidents — any open Respond incidents that reference it
Input is validated and sanitized before it's used in a query or returned in a response.
Notes
This talks to NetWitness's own REST APIs the way any external integration would — it doesn't embed or redistribute any NetWitness product code.
Not affiliated with or endorsed by RSA/NetWitness. Built independently against a personal home lab instance.
Related MCP Connectors
Manage tickets, run agents and workflows, query tables, and search workspace knowledge.
Live threat intel for agents: incidents, actors, CVEs with KEV/EPSS, ransomware leak-site victims.
Search log events, investigate anomalies, and manage cases in your Knowledge Grid tenant.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceConnects AI agents with the CrowdStrike Falcon platform to enable intelligent security analysis, providing programmatic access to detections, incidents, threat intelligence, vulnerabilities, and other security capabilities for advanced security operations and automation.277MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language threat hunting and incident response by connecting LLMs to enterprise security data sources like Elasticsearch, EVTX logs, PCAP files, and Velociraptor.58 PyPI204GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Wazuh SIEM for alert querying, threat hunting, vulnerability scanning, and active response actions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to converse in plain language with a Wazuh SIEM deployment, querying and aggregating alerts, hunting threats, triaging vulnerabilities, running compliance checks, and executing or rolling back active responses across multi-cluster environments. Works with both cloud and fully local, air-gapped LLM clients while enforcing scoped, audited access to the security tools.MIT