nano-investigator MCP
Turn Claude Code or any MCP client into a SOC analyst workstation with @nano-rs/investigator-mcp-server: search, triage and hunt in plain language.
Connect your MCP client to nano to search logs, triage alerts, investigate cases, hunt threats, and author parsers in natural language. @nano-rs/investigator-mcp-server exposes these analyst surfaces to your coding agent over stdio.
The server registers tools, prompts, and resources, then proxies each call to your nano API and search service.
{
"mcpServers": {
"nano-investigator": {
"command": "npx",
"args": ["-y", "@nano-rs/investigator-mcp-server"],
"env": {
"NANOSIEM_API_URL": "https://your-nano.example.com",
"NANOSIEM_API_KEY": "your-api-key"
}
}
}
}Add this to your MCP config (~/.claude/settings.json, or a project .mcp.json), restart your agent, and run /mcp to confirm it's connected. npx fetches the published package on first launch — nothing to clone or build.
What you can ask
> how many alerts fired today?
> investigate alert 456
> what do we know about 10.5.2.40?
> search for failed logins in the last 24 hours
> who are the riskiest entities right now?
> create a case for the DNS exfil from 10.5.2.40
> hunt for lateral movement in the last 7 days
> build a parser for these logsConfiguration
The server reads exactly three environment variables:
| Variable | Required | Notes |
|---|---|---|
NANOSIEM_API_URL | Yes | nano API URL. On a unified (install.sh) deployment, this is your base URL. |
NANOSIEM_API_KEY | Yes | Sent as the X-API-Key header on every request. |
NANOSIEM_SEARCH_URL | No | Split-port deployments only (search on :3002); falls back to NANOSIEM_API_URL. |
How it differs from nanodac
nanodac writes detection rules; nano-investigator operates the SIEM — search, triage, investigate, hunt, and build parsers. They run side by side as separate MCP servers sharing the same environment variables. nano-investigator reads detections but never edits them (that's nanodac's job), and it's read-first overall. Its writes are cases, notebooks, dashboards, saved searches, parsers and source configs, source credentials, hunt profiles, and entity risk resets.
Troubleshoot
Need help with these checks? Contact support with the affected deployment, request ID and time with timezone.
The server does not connect
Check NANOSIEM_API_URL and NANOSIEM_API_KEY, restart your client, and run /mcp to verify the connection. Split-port deployments also need the correct search URL. See Setup.
A generated query uses legacy field names
The documented 0.1.16 release still includes legacy prompts and resources. Ask the agent to use OCSF 1.9 paths and check the field mapping.
What's next
- Investigator overview — the full tool surface and what writes vs reads
- Setup — config, API key permissions, and verification
- Triage · Investigate · Hunt — work the queue and run investigations
- Tool Reference — every tool, prompt, and resource
nanodac CLI
Manage nano detections as version-controlled YAML with @nano-rs/dac-cli — validate, test, diff, and sync detection rules from your terminal or CI
Add a SIEM to Your Ludus Cyber Range
Send logs from your Ludus cyber range into nano SIEM, then search them and run detections against the attacks you launch in the lab.