runZero MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 17 Sep 2026.
Every runZero query, plus a local SQLite copy of your whole attack surface that diffs over time
What the code does
We read the source, 20 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
cacheFile := filepath.Join(c.cacheDir, c.cacheKey(path, params)+".json")
select {
case <-time.After(interval + jitter):
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to runZero MCP
same job, measured the same wayEvery SuperOps PSA+RMM entity in your terminal, plus a local SQLite mirror that answers
Every Domotz endpoint, plus a local SQLite fleet mirror that answers cross-site questions.
Every Huntress endpoint, plus a local SQLite mirror that delivers fleet-wide incident, coverage
Every Autotask entity at the command line, plus a local SQLite mirror that answers ticket-aging
Sync your whole Datto BCDR fleet into local SQLite and answer the questions the per-appliance
Every ImmyBot endpoint typed, plus a local SQLite mirror that answers the cross-tenant questions
Every Xero Accounting read plus a local SQLite ledger - aging, reconciliation, and GL tie-out
Every Atera RMM + PSA endpoint, plus a local SQLite mirror that answers fleet-health, SLA, and
runZero MCP — questions
Answers built from our own checks of this server.