PAGES
← all tools
◆ Exploitation & C2

mcp-kali-server

open-source

API bridge connecting MCP clients to a Kali Linux terminal, enabling AI-assisted penetration testing and CTFCTFCapture The Flag — a competitive hacking challenge format where participants exploit intentionally vulnerable systems or puzzles to retrieve hidden strings, used by cyber tools to practice and demonstrate offensive and defensive techniques. solving via tools like Nmap, Metasploit, and sqlmap

Summary

mcp-kali-server is an open-source API bridge, free to use, that connects MCP clients such as Claude Desktop or 5ire to a Kali Linux machine so an AI model can execute terminal commands and offensive security tools like Nmap, Metasploit, sqlmap, Hydra, and WPScan directly on it. It runs as a service on the Kali box, started locally or bound to a chosen interface and port, with clients connecting to it either locally or remotely. It is aimed at penetration testers and CTF players who want an AI model to suggest and run recon or exploitation commands in real time rather than typing them by hand. It sits in the emerging space of AI-driven offensive tooling built on the Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface., rather than replacing any single existing scanner. First committed in 2025, the project has five contributors and 23 commits in the past year, though its one tracked release is now 500 days old.

API bridge connecting MCP clients to a Kali Linux terminal, enabling AI-assisted penetration testing and CTF solving via tools like Nmap, Metasploit, and sqlmap

How mcp-kali-server helps

Which service on a target host is actually vulnerable, and how do I get in?

the model calls Nmap or Metasploit through the bridge, reads the output, and chains a follow-up exploitation command from those results without you retyping anything into a terminal

Is this web application's login or admin panel crackable?

Hydra or WPScan runs against the target through the API and the model interprets the results to suggest the next command, such as a targeted John the Ripper run on any recovered hashes

Where does this target's directory structure or hidden content leak information?

Dirb, gobuster, or Nikto is run against the target and the raw output is returned to the model for interpretation and follow-up

What accounts and shares does this Windows or Samba host expose?

enum4linux runs against the host and returns user, group, and share enumeration output for the model to act on

Can a raw command I think of be run on the Kali box right now, mid-conversation?

the bridge exposes a controlled API that executes arbitrary terminal commands and returns structured output, so any command the model or you type gets run without switching to a separate shell

Languages

Not documented

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for mcp-kali-server, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail mcp-kali-server puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Nothing shipped since we started watching. Releases and docs updates land here as they happen.

last release Apr 8, 2025 · watching since Jun 24, 2026

Project health

Issue, contributor and maintainer activity in Wh0am123/MCP-Kali-Server, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

  1. Contributors 4 +3 vs prior 12 months
  2. Maintainers 2 +2 joined · −1 left, last 12 months
  3. Bus factor 1 committers behind half the commits
  4. Community-filed 100% of issues opened, last 12 months
  5. Median time to close 19 days first maintainer reply 3.8 days
  6. Open backlog 3 of 22 issues ever filed
  1. Issues opened / month 0 · 0 communitymaintainers
  2. Open backlog 3
  3. Contributors / month 0
  4. Commits / month 0
  5. Stars 825
Issue themes, last 12 months
  • other 100%

Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

Libraries its release ships

What its latest release locks, checked against known advisories.

None of its release's images build from a lockfile we can read.

Add the badge to your README

Maintain this project? The badge links readers straight to this page, so they can follow every release here.

Tracked by Cyber Toolchain Choose a badge style and copy the code →
browse all tools → score card for your toolchain →