Skip to content
Back to search

NETWORK-WALKS-W3-HexStrike-MCP-Setup

Set up HexStrike AI’s MCP server with Claude Desktop on Kali Linux — and fixed a disk-space problem that cascaded into three unrelated-looking Python errors before confirming the connection with a live health check. NetworkWalks Week 3.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/philip-ajik--network-walks-w3-hexstrike-mcp-setup/badge.svg)](/listings/philip-ajik--network-walks-w3-hexstrike-mcp-setup)

HTML

<a href="/listings/philip-ajik--network-walks-w3-hexstrike-mcp-setup"><img src="/api/listings/philip-ajik--network-walks-w3-hexstrike-mcp-setup/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

The lab guide installs the unofficial Debian build of Claude Desktop from `aaddrick/claude-desktop-debian` via a GPG key and apt repository.

curl -fsSL https://pkg.claude-desktop-debian.dev/KEY.gpg | sudo gpg --dearmor -o /usr/share/keyrings/claude-desktop.gpg
echo "deb [signed-by=/usr/share/keyrings/claude-desktop.gpg arch=amd64,arm64] https://pkg.claude-desktop-debian.dev stable main" | sudo tee /etc/apt/sources.list.d/claude-desktop.list
sudo apt update
sudo apt install claude-desktop

I opened Claude Desktop for the first time and signed in.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 431 lines
  1. <div align="center">
  2. # 🩸 Wiring an AI Agent to a Red Team Toolkit: HexStrike MCP + Claude Desktop
  3. **Optional Week 3 lab — installing Claude Desktop and the HexStrike AI MCP server on Kali Linux, and everything that broke on the way**
  4. </div>
  5. <p align="center">
  6. <img src="https://img.shields.io/badge/Tool-HexStrike%20AI%20MCP-1679A7?style=flat-square" />
  7. <img src="https://img.shields.io/badge/Role-AI%20Agent%20Tooling%20Setup-C00000?style=flat-square" />
  8. <img src="https://img.shields.io/badge/Result-MCP%20Server%20Healthy-C8570A?style=flat-square" />
  9. <img src="https://img.shields.io/badge/Phase-Recon%20%26%20Exploitation%20Tooling-238F89?style=flat-square" />
  10. <img src="https://img.shields.io/badge/NetworkWalks-B082-C00000?style=flat-square" />
  11. </p>
  12. ---
  13. ## 📌 Project Overview
  14. This is an **optional but important** Week 3 lab from the Networkwalks Cybersecurity internship: **How to set up the HexStrike MCP Server (Practice Lab)**. The task is to connect **Claude Desktop** to **HexStrike AI**, an MCP (Model Context Protocol) server that exposes a large set of offensive-security tools (recon, exploitation, password, network, forensics, and more) so an AI agent can call them directly, on a **Kali Linux** machine.
  15. I followed the lab's own steps: install Claude Desktop from the `aaddrick/claude-desktop-debian` GitHub repo, clone `0x4m4/hexstrike-ai`, set up its Python virtual environment, and point Claude Desktop's MCP config at the HexStrike bridge script. I ran this on 19 November 2026, start to finish, across about two and a half hours.
  16. Almost none of it worked on the first try. One real problem, running out of space while installing HexStrike's Python dependencies, cascaded into several more confusing errors before I reached a clean install, and the lab's own example configuration pointed at a username that wasn't mine. I used an AI assistant throughout to help read the errors and suggest the next command; I'm documenting what it told me to run and why, alongside what I actually typed.
  17. | 🔎 Item | ✅ Result |
  18. | ------- | --------- |
  19. | Claude Desktop | Unofficial Debian build (`aaddrick/claude-desktop-debian`), installed via `apt` |
  20. | HexStrike AI | Cloned from `0x4m4/hexstrike-ai`, Python virtual environment, Flask API on port 8888 |
  21. | Root cause of most errors | `/tmp` filling up during `pip install`, which left several packages partially/incorrectly installed |
  22. | Config issue | The lab's sample `claude_desktop_config.json` uses `/home/kali/...`; my actual home directory is `/home/philip/...` |
  23. | Final state | HexStrike AI extension shows **Running** in Claude Desktop; a live health check reports the server healthy with 8/8 essential tools and 58/1000 tools installed overall |
  24. ---
  25. ## 🎯 Objectives
  26. - Install Claude Desktop on Kali Linux from a community-maintained Debian package
  27. - Clone and set up HexStrike AI's Python environment and dependencies
  28. - Point Claude Desktop's MCP configuration at the HexStrike bridge script
  29. - Diagnose and fix a disk-space problem that broke several unrelated-looking imports
  30. - Correct a hardcoded path in the lab's sample configuration
  31. - Confirm the integration actually works by asking Claude to check the server's own health
  32. ---
  33. ## 🛡️ Why This Matters for Security
  34. MCP servers like HexStrike are becoming a real part of how AI-assisted offensive security work gets done: instead of a human typing every command, the AI agent can call recon, exploitation, and OSINT tools directly, reason about the output, and chain them together. Setting one up safely and correctly, including understanding exactly what gets installed, where it listens, and what it can reach, is itself a skill worth practicing before relying on it in real engagements.
  35. This lab is also a good exercise in something less glamorous: reading a wall of Python tracebacks calmly, finding the one root cause underneath several different-looking symptoms, and fixing environment problems (disk space, package versions, hardcoded paths) that have nothing to do with "hacking" but stop every tool from working regardless.
  36. > ⚠️ **Important:** HexStrike AI's own startup banner warns "This is a development server. Do not use it in a production deployment." This setup is for a personal practice lab only, running on `localhost`, with no tools pointed at any system I don't own or have permission to test.
  37. ---
  38. ## ⚙️ Lab Configuration
  39. | 🧩 Component | ⚙️ Configuration |
  40. | ------------ | ---------------- |
  41. | 🖥️ Platform | Kali Linux VM (VirtualBox) |
  42. | 🖥️ AI Client | Claude Desktop (`aaddrick/claude-desktop-debian`, unofficial build) |
  43. | 🛠️ MCP Server | HexStrike AI (`0x4m4/hexstrike-ai`), Python virtual environment, Flask API on `127.0.0.1:8888` |
  44. | 🔑 Config file | `~/.config/Claude/claude_desktop_config.json` |
  45. | 🧰 Tools exposed | 1000 possible tools across categories (Essential, Network, Password, Web security, Forensics, OSINT, Binary, Exploitation, Vulnerability scanning, and more); 58 actually installed on this machine |
  46. | 🏆 Scoring | None; success is a healthy, connected MCP server |
  47. ---
  48. # 🪜 Lab Procedure
  49. ## Step 1. Install Claude Desktop
  50. The lab guide installs the unofficial Debian build of Claude Desktop from `aaddrick/claude-desktop-debian` via a GPG key and apt repository.
  51. ![GitHub repo and README](screenshots/hex-01-claude-desktop-github-readme.png)
  52. ```bash
  53. curl -fsSL https://pkg.claude-desktop-debian.dev/KEY.gpg | sudo gpg --dearmor -o /usr/share/keyrings/claude-desktop.gpg
  54. echo "deb [signed-by=/usr/share/keyrings/claude-desktop.gpg arch=amd64,arm64] https://pkg.claude-desktop-debian.dev stable main" | sudo tee /etc/apt/sources.list.d/claude-desktop.list
  55. sudo apt update
  56. sudo apt install claude-desktop
  57. ```
  58. ![Repository added, apt update running](screenshots/hex-02-claude-desktop-apt-repo-added.png)
  59. ![Package installing](screenshots/hex-03-claude-desktop-installing.png)
  60. I opened Claude Desktop for the first time and signed in.
  61. ![First launch](screenshots/hex-04-claude-desktop-first-launch.png)
  62. ![Signed in](screenshots/hex-05-claude-desktop-signed-in.png)
  63. ## Step 2. Clone HexStrike AI and set up its environment
  64. ```bash
  65. git clone https://github.com/0x4m4/hexstrike-ai.git
  66. cd hexstrike-ai
  67. python3 -m venv hexstrike-env
  68. source hexstrike-env/bin/activate
  69. pip3 install -r requirements.txt
  70. ```
  71. ![HexStrike AI GitHub repo](screenshots/hex-06-hexstrike-github-repo.png)
  72. ![Repo cloned, venv created](screenshots/hex-07-clone-repo-and-venv.png)
  73. ## Step 3. The dependency install fails: "No space left on device"
  74. The first `pip install -r requirements.txt` stopped partway through with `ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device`, while a later line adds "This error originates from a subprocess, and is likely not a problem with pip."
  75. ![No space left on device](screenshots/hex-08-pip-install-no-space-left-error.png)
  76. I asked an AI assistant to help read the error. It suggested checking actual disk usage first with `df -h` and `df -i`, since "no space left" can also mean the filesystem is out of inodes, not just bytes.
  77. ```bash
  78. df -h
  79. df -i
  80. ```
  81. The disk itself had plenty of room (about 6.4 GB free, `/dev/sda1` at 72%), but the assistant pointed out that `/tmp` is its own small filesystem (a `tmpfs` capped well under 1 GB in this VM) and that `pip` extracts and builds large packages there by default; a big package like `angr` can fill a small `/tmp` even when the real disk is nowhere near full.
  82. ![Checking disk space with df](screenshots/hex-09-checking-disk-space-df.png)
  83. ## Step 4. Chasing the disk-space problem
  84. Following the assistant's suggestions, I checked how much space the pip cache and `/tmp` were actually using, and cleared what I could.
  85. ```bash
  86. du -sh ~/.cache/pip
  87. du -sh /tmp
  88. ```
  89. ![Clearing pip cache and checking /tmp](screenshots/hex-10-clearing-pip-cache-and-tmp.png)
  90. ![pip cache size check](screenshots/hex-11-pip-cache-size-check.png)
  91. Along the way, a `du -sh /tmp` as root (to see past some permission-denied systemd directories) needed a `quota -s` check the assistant suggested for a fuller picture of my disk limits, which wasn't installed.
  92. ```bash
  93. quota -s
  94. ```
  95. ![quota: command not found](screenshots/hex-12-quota-not-found-prompt.png)
  96. ```bash
  97. sudo apt install quota
  98. ```
  99. ![quota installed](screenshots/hex-13-quota-installed.png)
  100. ## Step 5. The real fix: redirect pip's temp directory
  101. The assistant's actual fix, once the small `/tmp` was confirmed as the likely culprit, was to point `pip`'s temporary directory at my home folder instead, which has much more free space, and to install without using the pip cache:
  102. ```bash
  103. grep -nE 'angr|pyvex|python' requirements.txt # confirm what's actually pulling in the big packages
  104. python -m pip check # "No broken requirements found" at this point
  105. mkdir -p ~/pip-tmp
  106. TMPDIR="$HOME/pip-tmp" python -m pip install --no-cache-dir -r requirements.txt
  107. ```
  108. ![Confirming the angr requirement; pip check clean](screenshots/hex-14-grep-angr-version-pip-check-clean.png)
  109. ![TMPDIR pip install retry](screenshots/hex-15-tmpdir-pip-install-retry.png)
  110. ![Packages downloading successfully](screenshots/hex-16-pip-downloading-packages.png)
  111. This time the install ran all the way through, over a hundred packages including `angr`, `pyvex`, `cffi`, `mitmproxy`, and `pwntools`.
  112. ![Install completed successfully](screenshots/hex-17-pip-install-completed.png)
  113. ## Step 6. The same root cause, three more symptoms
  114. With the install finally complete, I expected to just run the server. Instead, importing the tools failed three more times in a row, each with a different error. These were not three separate bugs: they were all fallout from packages that had been partially or incorrectly installed during the earlier disk-space failure, and each needed a specific package version reinstalled.
  115. **First: `angr` itself failed to import**, with a long traceback through its dependency chain.
  116. ```bash
  117. python -c "import angr, flask, fastmcp; print('HexStrike dependencies verified!')"
  118. ```
  119. ![angr import error](screenshots/hex-18-angr-import-error.png)
  120. **Second: that traceback bottomed out in `bitstring`**, with `AttributeError: module 'bitstring' has no attribute 'ConstBitStream'`. The assistant explained that `bitstring` 5.x removed the older `ConstBitStream` API that `pyvex` (one of `angr`'s dependencies) still expects, and that the fix was to pin an older, compatible release.
  121. ![bitstring AttributeError](screenshots/hex-19-bitstring-attribute-error.png)
  122. ```bash
  123. python -m pip install "bitstring>=4.2,<5"
  124. ```
  125. ![Installing a compatible bitstring version](screenshots/hex-20-installing-bitstring.png)
  126. **Third: a new, different error appeared from `cffi`/`pycparser`**, `AttributeError: property 'filename' of 'CLexer' object has no setter`, after `bitstring` was fixed. The assistant identified this as a separate, unrelated version mismatch: a newer `pycparser` had changed how its lexer handles the `filename` property, which an older `cffi` (a `pyvex` dependency) wasn't expecting.
  127. ![bitstring fixed, cffi/pycparser error appears](screenshots/hex-21-bitstring-installed-still-failing.png)
  128. ![cffi/pycparser AttributeError](screenshots/hex-22-cffi-pycparser-attribute-error.png)
  129. ```bash
  130. python -m pip install "pycparser==2.21"
  131. ```
  132. ![Reinstalling pycparser 2.21](screenshots/hex-23-reinstalling-pycparser.png)
  133. With both `bitstring` and `pycparser` pinned to compatible versions, the verification line finally printed clean, and `hexstrike_server.py` started up with its full HEXSTRIKE banner.
  134. ```bash
  135. cd ~/hexstrike-ai
  136. source hexstrike-env/bin/activate
  137. python3 hexstrike_server.py
  138. ```
  139. ![Dependencies verified, server starts](screenshots/hex-24-dependencies-verified-server-starts.png)
  140. ## Step 7. Configure Claude Desktop to use HexStrike as an MCP server
  141. With the server running, I opened Claude Desktop's settings to add HexStrike as a local MCP server.
  142. ![Claude settings, no MCP servers yet](screenshots/hex-25-claude-settings-no-mcp-servers.png)
  143. ![Edit Config prompt](screenshots/hex-26-claude-settings-edit-config-prompt.png)
  144. ![Claude config folder](screenshots/hex-27-claude-config-folder.png)
  145. The lab guide's sample `claude_desktop_config.json` uses the path `/home/kali/hexstrike-ai/...`, matching the lab's own demo VM where the user is literally called `kali`. My own Kali VM's user is `philip`, so that path doesn't exist on my machine.
  146. ```json
  147. {
  148. "mcpServers": {
  149. "hexstrike-ai": {
  150. "command": "/home/kali/hexstrike-ai/hexstrike-env/bin/python",
  151. "args": [
  152. "/home/kali/hexstrike-ai/hexstrike_mcp.py",
  153. "--server",
  154. "http://localhost:8888"
  155. ]
  156. }
  157. }
  158. }
  159. ```
  160. ![Config file with the lab's default /home/kali path](screenshots/hex-28-config-json-default-kali-path.png)
  161. ![Still showing the kali path before editing](screenshots/hex-29-config-json-still-kali-path.png)
  162. I edited the paths to match my actual home directory.
  163. ![Config edited to /home/philip](screenshots/hex-30-config-json-edited-to-philip-path.png)
  164. ![Claude settings still showing no servers added](screenshots/hex-31-claude-settings-no-servers-added.png)
  165. ![Extensions panel](screenshots/hex-32-claude-extensions-panel.png)
  166. ## Step 8. Confirm everything actually connects
  167. Before assuming the path fix alone would work, I checked that the bridge script genuinely existed where the config pointed, and that the config file itself now held the corrected paths.
  168. ```bash
  169. ls -l /home/philip/hexstrike-ai/hexstrike_mcp.py
  170. grep -nE '"command"|hexstrike_mcp.py|localhost:8888' ~/.config/Claude/claude_desktop_config.json
  171. ```
  172. ![Confirming hexstrike_mcp.py exists](screenshots/hex-33-confirming-hexstrike-mcp-py-exists.png)
  173. ![grep confirming the corrected config paths](screenshots/hex-34-grep-confirming-config-paths.png)
  174. I then checked whether the Flask API was actually listening on port 8888, and what it returned.
  175. ```bash
  176. ss -tln | grep 8888
  177. curl -i http://localhost:8888
  178. ```
  179. ![Checking port 8888](screenshots/hex-35-checking-port-8888-listening.png)
  180. `curl` returned `HTTP/1.1 404 NOT FOUND`, which looked alarming at first glance, but the assistant pointed out this actually confirms the Flask server **is** running and answering; it simply has no route defined at the bare root path `/`.
  181. ![curl to localhost:8888 returns 404, meaning the server is alive](screenshots/hex-36-curl-localhost-8888-404.png)
  182. I double-checked the `hexstrike_server.py` process was genuinely running, then ran the MCP bridge script itself in the foreground to watch it connect live.
  183. ```bash
  184. ps -fp <pid>
  185. cd ~/hexstrike-ai
  186. ./hexstrike-env/bin/python hexstrike_mcp.py
  187. ```
  188. ![Confirming the server process is running](screenshots/hex-37-checking-server-process-running.png)
  189. ![Running hexstrike_mcp.py manually, connecting to the API](screenshots/hex-38-running-hexstrike-mcp-manually.png)
  190. It connected successfully: "Successfully connected to HexStrike AI API server," reported a healthy status, and sat ready to serve requests.
  191. ![Full corrected config.json](screenshots/hex-39-full-config-json-contents.png)
  192. ![Claude's log directory](screenshots/hex-40-claude-logs-directory.png)
  193. Claude Desktop's own logs then showed the MCP server registering successfully.
  194. ```bash
  195. grep -i mcp ~/.config/Claude/logs/main.log | tail
  196. ```
  197. ![MCP server registered in Claude's logs](screenshots/hex-41-mcp-server-registered-in-logs.png)
  198. ![Confirming the registration line](screenshots/hex-42-grep-mcp-registered-confirmation.png)
  199. ## Step 9. Final checks and confirmation
  200. I ran a few more sanity checks: confirming Claude Desktop's own processes, listing its installed binary, and running its built-in `--doctor` diagnostic command.
  201. ```bash
  202. ps aux | grep -i claude
  203. ls -la /usr/lib/claude-desktop-unofficial/
  204. claude-desktop-unofficial --doctor
  205. ```
  206. ![Claude Desktop processes](screenshots/hex-43-ps-aux-claude-desktop-processes.png)
  207. ![Install directory listing](screenshots/hex-44-claude-desktop-install-dir-listing.png)
  208. ![--doctor diagnostics: install, display server, sandbox, MCP config all PASS](screenshots/hex-45-claude-desktop-doctor-diagnostics.png)
  209. ![Diagnostics continued: disk space, cowork mode (KVM not available, non-blocking)](screenshots/hex-46-doctor-diagnostics-continued.png)
  210. I restarted Claude Desktop to pick up the corrected config.
  211. ![Restarting Claude Desktop](screenshots/hex-47-restart-claude-desktop.png)
  212. The HexStrike AI extension now shows as **Running**, with the corrected command and arguments visible in its own settings panel.
  213. ![hexstrike-ai extension Running](screenshots/hex-48-hexstrike-ai-extension-running.png)
  214. ## Step 10. Ask Claude to check the server's own health
  215. As a final, meaningful test rather than just a green status dot, I asked Claude directly to check the health of the HexStrike MCP server it was now connected to.
  216. ![Asking Claude for a health check](screenshots/hex-49-asking-claude-for-health-check.png)
  217. Claude used the live MCP connection to report back: the server (v6.0.0) was healthy, had been running about 55 minutes, all 8 essential tools were available, and gave live resource and cache figures.
  218. ![Health check: resources and cache](screenshots/hex-50-health-check-resources-report.png)
  219. It then broke down tool availability by category (58 of 1000 possible tools actually installed) and flagged a low overall command success rate as something worth investigating.
  220. ![Tool availability by category](screenshots/hex-51-health-check-tool-categories.png)
  221. ![Things to look at: low success rate, missing cloud/web tools](screenshots/hex-52-health-check-things-to-look-at.png)
  222. **The HexStrike MCP server is confirmed connected, healthy, and genuinely usable by Claude Desktop.**
  223. ---
  224. # 📊 Results
  225. | # | 🎯 Step | ✅ Result |
  226. | - | ------- | --------- |
  227. | 1 | Install Claude Desktop | Installed and signed in (unofficial Debian build) |
  228. | 2 | Install HexStrike AI | Cloned, venv created, dependencies eventually installed cleanly |
  229. | 3 | Fix disk-space failure | `/tmp` was the real bottleneck, not the disk; fixed with `TMPDIR` redirected to home and `--no-cache-dir` |
  230. | 4 | Fix knock-on dependency errors | Pinned `bitstring>=4.2,<5` and `pycparser==2.21` |
  231. | 5 | Fix Claude Desktop config | Corrected `/home/kali/...` to `/home/philip/...` in `claude_desktop_config.json` |
  232. | 6 | Confirm connection | `hexstrike-ai` extension shows **Running**; Claude's own health check confirms the server is up with 8/8 essential tools |
  233. *Footnote: this is a setup lab with no scored task or flag; success is the HexStrike MCP server being connected, healthy, and genuinely callable by Claude Desktop, which the final health check confirms.*
  234. ### Timeline (19 November 2026)
  235. | ⏱️ Time | 🔄 What happened |
  236. | ------- | ---------------- |
  237. | 05:00–05:11 | Claude Desktop installed and signed in |
  238. | 05:11–05:26 | HexStrike cloned; first `pip install` fails with "No space left on device" |
  239. | 05:26–06:17 | Disk-space diagnosis (`df`, `du`, `quota`); fixed with `TMPDIR` redirect; full install completes |
  240. | 06:20–06:28 | Three chained import errors (`angr` → `bitstring` → `cffi`/`pycparser`), each fixed in turn |
  241. | 06:31 | `hexstrike_server.py` starts cleanly with the full HEXSTRIKE banner |
  242. | 06:34–07:00 | Claude Desktop MCP config edited from `/home/kali/...` to `/home/philip/...` |
  243. | 07:00–07:20 | Verifying the fix: process checks, port checks, manual bridge run, `--doctor` diagnostics |
  244. | 07:24 | `hexstrike-ai` extension shows **Running** |
  245. | 07:26 | Claude's own health check confirms the server is healthy and usable |
  246. ---
  247. # 🔭 Observations Beyond the Task Questions
  248. 1. **"No space left on device" did not mean the disk was full.** The real disk had 6.4 GB free; the actual bottleneck was a size-capped `/tmp` tmpfs that `pip` uses for temporary build files. This is worth remembering for any VM with a small `/tmp`.
  249. 2. **`pip check` reported "No broken requirements found" even while imports kept failing.** `pip check` only verifies that installed packages' declared version requirements are mutually satisfiable; it does not catch packages that were only partially written to disk or whose compiled extensions silently mismatch at import time.
  250. 3. **A `404 Not Found` from `curl` can mean success, not failure.** It confirmed the Flask server was alive and answering HTTP requests; it just had no route at `/`. Reading what an error code actually means for the specific server mattered more than reacting to "404" as a generic failure.
  251. 4. **The lab's own health check flagged real gaps worth knowing about.** Only 58 of 1000 possible tools are actually installed on this machine, cloud-security tooling (prowler, trivy, kube-hunter, scout-suite) is missing entirely, and Metasploit showing as unavailable while `msfconsole`/`msfvenom` show as present suggests it's just installed under a different binary name, not actually missing.
  252. 5. **HexStrike's own startup banner is explicit that this is a development server, not for production use.** That matches the lab's framing: a practice environment on `localhost`, not a deployed tool.
  253. ---
  254. # 🐞 Challenges Encountered
  255. * **Issue: `pip install -r requirements.txt` failed with "No space left on device", which then broke three unrelated-looking imports.** All of this traced back to one root cause: `/tmp` filling up mid-install, which left `angr` and several of its dependencies (`bitstring`, `pycparser`/`cffi`) partially or incorrectly installed. Fixing the actual disk problem first (`TMPDIR` pointed at a larger filesystem, `--no-cache-dir`) and then pinning the two packages whose APIs had drifted (`bitstring>=4.2,<5`, `pycparser==2.21`) resolved all three symptoms in turn.
  256. **What I'll do differently:** Check `df -h` and the size of `/tmp` specifically before running any large `pip install`, rather than after the first failure.
  257. * **Issue: Claude Desktop's MCP config pointed at `/home/kali/...`, a path that doesn't exist on my machine.** The lab's sample config matches the instructor's own demo VM, where the Linux username happens to be `kali`. My VM's username is `philip`.
  258. **Resolution:** Edited `claude_desktop_config.json` to use my actual home directory, then verified the bridge script's real path with `ls -l` and the config's contents with `grep` before trusting it would work.
  259. **What I'll do differently:** Treat any sample config with a hardcoded path as a template, not a literal value, and check `whoami`/`$HOME` before copying it in.
  260. * **No blockers once both issues were fixed.** The server started cleanly, the extension showed Running, and Claude's own health check confirmed the connection worked end to end.
  261. ---
  262. # 💡 Key Learnings
  263. 1. One root cause can produce several different-looking error messages. Before chasing each traceback separately, it's worth asking whether they share a common origin.
  264. 2. "No space left on device" can mean a specific, small filesystem like `/tmp`, not the disk as a whole; `df -h` on the specific path matters more than a general sense of free space.
  265. 3. A clean `pip check` is not proof that every package actually imports correctly; partial installs from an earlier failure can still be sitting on disk.
  266. 4. Reading what an HTTP status code actually means for the server in front of you (a 404 at `/` rather than a connection refusal) avoids chasing a non-problem.
  267. 5. Any lab's sample configuration file is written for the instructor's own environment. Usernames, paths, and hostnames need to be checked against your own machine before use.
  268. 6. A green "Running" status is a good sign, but asking the AI agent to actually use the connected tool (here, a live health check) is a more meaningful confirmation than a status indicator alone.
  269. ---
  270. # 🔐 Security & Ethical Use
  271. This lab is a personal setup/practice exercise. HexStrike AI's server ran only on `localhost` for this session, and no tool it exposes was pointed at any system I don't own or don't have permission to test. HexStrike's own startup output explicitly warns it is a development server and should never be exposed in a production deployment. The same caution applies to any of the offensive-security tools it can call: they should only ever be used within an authorized, permitted scope.
  272. ---
  273. # 🔗 Tools & Resources
  274. - **Claude Desktop (unofficial Debian build):** https://github.com/aaddrick/claude-desktop-debian
  275. - **HexStrike AI:** https://github.com/0x4m4/hexstrike-ai
  276. - **NetworkWalks:** https://networkwalks.com
  277. ---
  278. # 👤 Author
  279. **Philip Ajik**
  280. Cybersecurity Student (Batch B082) — Networkwalks Academy
  281. LinkedIn: https://www.linkedin.com/in/philip-ajik-a22944384
  282. ---
  283. ## 📌 Project Information
  284. **Program Name:** Cybersecurity at Networkwalks | **Task:** Week 3 Optional Lab | **Project:** HexStrike MCP Server Setup with Claude Desktop | **Repository:** GitHub

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.