Investigator
nano-investigator: an MCP server that turns a coding agent into a SOC analyst workstation over your nano data
Connect nano-investigator to search, triage alerts, investigate cases, hunt, and build parsers from your coding agent. The local MCP server runs over stdio and calls nano’s API and search service for each operation.
The server registers 91 tools, five MCP prompts, and MCP resources.
It is published to npm as @nano-rs/investigator-mcp-server. These pages describe version 0.1.16.
A typical session looks like a conversation against your data:
- "how many alerts fired today?" runs
get_alert_counts - "what do we know about 10.5.2.40?" runs
get_entity_contextplus a scoped search - "investigate alert 456" runs the
investigate_alertprompt - "who are the riskiest entities right now?" runs
get_risky_entities - "build a parser for these logs" runs the
build_parserprompt
How it differs from nanodac
nano-investigator and nanodac sit on opposite sides of the detection lifecycle and run side by side as separate MCP servers, sharing the same environment variables.
| nanodac | nano-investigator | |
|---|---|---|
| Role | Detection-as-code authoring | SOC operations + parser authoring |
| Work | Write, validate, and deploy detection rules | Search, triage, investigate, hunt, build parsers |
| Detections | Reads and writes | Reads only |
| Default posture | Writes to the SIEM | Read-first; writes cases, notebooks, and parsers |
Detection-rule editing stays in nanodac. nano-investigator only reads detections; for the authoring side, see Detection-as-Code.
Log-source parsers can be authored two ways, and neither uses nanodac's tools (nanodac is detection-only). The version-controlled path drafts a parser.yaml against the nano-rs/parsers repo and validates it with the vector vrl CLI, then ships by PR or UI import — see Authoring parsers. The interactive path, new here, authors and deploys a parser directly against a live nano deployment over MCP — see Build parsers.
The surface at a glance
| Area | Tools | Access |
|---|---|---|
| Search and schema | 9 | Read, plus save_search and create_shared_search |
| Alerts | 3 | Read-only |
| Cases | 13 | Read, plus 8 write tools (merge_cases is destructive) |
| Notebooks | 9 | Read, plus 5 write tools |
| Dashboards | 7 | Read, plus create and update |
| Detections and MITRE | 5 | Read-only |
| Risk | 5 | Read, plus reset_entity_risk (destructive) |
| Enrichment | 2 | Read-only |
| Prevalence | 3 | Read-only |
| System | 4 | Read-only |
| Parsers | 23 | Read, plus author, publish and import |
| Onboarding | 4 | Credentials and pull-source transports |
| Recon | 4 | Estate census and hunt drafts |
Most of the surface reads. The tools that write:
- Cases: create, update, change status, assign, attach alerts, post wall entries, merge notebooks into cases, and merge cases.
- Notebooks: create, append entries, add references, update and share.
- Dashboards: create and update.
- Risk:
reset_entity_riskclears an entity's risk score. - Parsers: create, update, publish, deploy and undeploy log-source parsers, import from a parser repository and wire routing.
- Onboarding: store credentials and create pull-source transports.
import_credential_from_filereads a file from the machine the server runs on. - Search:
save_searchandcreate_shared_search.
Alerts can't be changed. There's no acknowledge, close or assign tool for alerts; triage happens by adding an alert to a case. Detections are read-only here; author them with nanodac.
Alongside the tools, the server registers:
- 5 MCP prompts:
investigate_alert,hunt_entity,hunt_campaign,morning_briefingandbuild_parser. These are workflows the agent follows, not callable tools. - MCP resources: an nPL reference, a VRL parser guide, seven investigation playbooks, and a UDM schema and SQL guide. See Tool Reference.
Troubleshoot
Need help with these checks? Contact support with the request ID and time with timezone.
A tool returns 403
The error names the endpoint. Add the matching permission from the tool reference to the key.
What's next
Setup
Install the MCP server and wire it into your agent.
Triage
Work the alert queue and turn alerts into cases.
Investigate
Run an alert investigation end to end.
Hunt
Hunt entities and campaigns across the data.
Build parsers
Author, validate, test, and deploy log-source parsers over MCP.
Tool Reference
All 91 tools, prompts and resources.