NinjaOne MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 11 Sep 2026.
Every NinjaOne report, plus a local store that answers fleet-wide questions no single API call can
We read the source, 2 d ago · rules 995398eba69f
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.
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.
Every KnowBe4 KMSAT reporting feature plus a local SQLite store that answers the cross-client
Every ThreatDown OneView API, plus fleet-wide stale-endpoint, health and seat reports across all
LynxMCP: 100% local MCP server for the code questions grep can't answer: call graph, hybrid search
Ask a codebase a question, get back the source that answers it — every block cited to file:line.
Checks an answer's citations at the registries that issue them. Every check files a signed report.
Give your Muse a phone number. BotPhone answers your business line and reports every call back.
App Store Connect API as MCP: apps, TestFlight, subscriptions, localizations, reports. JWT auth.
Give any AI agent a phone number. BotPhone answers your business line and reports every call back.
Answers built from our own checks of this server.