Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 0
- 4 1
- 3 1
- 2 3
- 1 0
Trust in production
- Trust it - 0%
- With caveats - 60%
- Wouldn't - 40%
40% would recommend this server
How reviewers scored it
- Setup & docs 2.6
- Auth experience 2.2
- Reliability 3.0
- Maintainer responsiveness 3.4
Why it got a D
A GPL-3.0 Swift command-line tool for macOS 14+ whose "kilobat mcp" command is a local stdio server with about 80 tools. Most only read: live traffic by app, Wi-Fi signal and channels, DNS, routes, speed and latency tests, VPN leak checks. About fifteen change the Mac: DNS servers, per-app allow and block rules, the VPN kill switch, data budgets, AirDrop visibility, and keep-awake. Their descriptions tell the model to get your explicit confirmation first, but that is an instruction, not a control, so keep tool approval on. Some tools need the separate, proprietary Kilobat menu-bar app, or administrator approval. No advisories on record. Biggest deduction: it works by running macOS command-line utilities, some with hosts and URLs the model picks (passed as arguments, not through a shell). There is no auth layer, and one person maintains it.
How to connect
// ~/.cursor/mcp.json
{ "mcpServers": { "kilobat": { "command": "kilobat", "args": ["mcp"] } } }claude mcp add kilobat -- kilobat mcp// claude_desktop_config.json (use the full path from: /usr/bin/which kilobat)
{ "mcpServers": { "kilobat": { "command": "/opt/homebrew/bin/kilobat", "args": ["mcp"] } } }Is Kilobat CLI MCP Server safe?
Is Kilobat CLI MCP Server safe to use?
Kilobat CLI MCP Server grades D (notable weaknesses - review closely). There is no login: anything that can start or reach it gets its full access. Upkeep is hard to verify (closed source or a single maintainer), so pin the version you tested. It shells out to helper programs or serves HTTP without enforced TLS, so keep it local and isolated.
Does Kilobat CLI MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Kilobat CLI MCP Server support authentication?
No. It has no login of its own, so limit who and what can start it.
Alternatives in Developer Tools
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
- A Dynatrace Remote MCP ServerDynatrace's hosted MCP server, running inside your Dynatrace SaaS environment, to run and explain DQL, look into problems, vulnerabilities and Kubernetes events, and forecast time series.
- A GitHub MCP ServerOfficial GitHub server for repos, issues, pull requests, Actions, and code security, hosted or local.
- A GitLab MCP ServerGitLab's built-in MCP server for projects, merge requests, work items, code, and CI pipelines, on GitLab.com or your own instance.
Embed this badge
[](https://trustedmcp.io/servers/kilobat-cli)<a href="https://trustedmcp.io/servers/kilobat-cli"><img src="https://trustedmcp.io/badge/kilobat-cli.svg" alt="TrustedMCP grade D" height="80"></a>Community reviews
Too many sharp edges
Gave it a fair shot over two weeks. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. There is no auth layer, so whatever can reach it can use it. I keep it local only.
Used for Automating release notes
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Fine for a demo, not for prod
Not what I expected from the description. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Keeping it to local experiments for now.
Used for Keeping project tickets in sync with code changes
- Setup & docs 2/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Does the job, docs could be better
I like it, with reservations. There is no auth layer, so whatever can reach it can use it. I keep it local only. Fine in production if you sandbox it.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 4/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Too much access for my comfort
Setup was rough and the result was flaky. Releases come often and the changelog is clear. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list.
Used for Scripting routine maintenance tasks
- Setup & docs 1/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 2/5
Better than the DIY script it replaced
Tried it on a side project first, then rolled it out at work. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. Updates land regularly, and nothing broke when I upgraded. Recommended, with sensible guardrails.
Used for Code review summaries for pull requests
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.