DashyNMS MCP privacy policy
Last updated 18 October 2026
The short version
DashyNMS MCP doesn’t collect, store or share any of your data. There’s no DashyNMS account, no analytics, no advertising and no tracking. It runs on a machine of yours, reads from your own servers, and hands its answers to the AI app you connected it to. Nothing goes to us.
Who the server talks to
- Your LibreNMS server, at the address you give it, and its backup address if you set one. This is where almost every answer comes from.
- Your Unimus and Graylog servers, only if you set them up.
- The AI app that started it, such as Claude Desktop or Claude Code. The two talk directly on the same machine, with nothing in between.
That’s all. It doesn’t check for updates or contact DashyNMS or anyone else. To get it, Docker downloads the container image from GitHub, the same as any other download.
Where your answers go
This is the part worth reading twice. What the server returns, such as device names, addresses, alerts, log lines and config, goes to your AI app. Your AI app then sends it to whichever AI model it uses, as it does with anything else you ask. What happens to it there is covered by that app’s and model provider’s own privacy terms, not this one.
To keep that to a minimum:
- Secrets are redacted first. SNMP communities, passwords and hashes, RADIUS, TACACS, IPsec, NTP and OSPF keys, API and licence keys, private keys and similar are removed from config backups and diffs before they leave the server.
- You can keep config text out entirely. Set
MCP_CONFIG_TEXT=summaryto only say whether a config changed, when, and by how much, oroffto leave Unimus out altogether. - Answers are kept small. Each one is capped (16 KB by default) and says when something was left out.
What the server keeps
Nothing on disk. It holds a short-lived copy of things like your device list in memory to answer questions quickly, and forgets it all when it stops. With Docker’s --rm, as in the set-up instructions, even the container is removed when your AI app closes it.
Its log goes to your AI app, which may keep it. The log notes which LibreNMS server and version it connected to, and the name of any tool that failed. It never includes your tokens or passwords.
Your tokens and passwords
Your LibreNMS and Unimus tokens and your Graylog password are read from your settings when the server starts. They’re never logged, never included in an answer, and only ever sent to the server they belong to. If one of your servers is on plain http, it warns you at startup, because the token or password would cross your network unencrypted.
Children
The server isn’t aimed at children and doesn’t knowingly collect anything from anyone.
Changes
If this policy changes, the new version will be posted here with a new date.
Contact
Questions? Email dashynms@pckp.net, or open an issue on GitHub. For a security problem, see the security policy.