Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
See which process holds a port, find free ports, and stop a dev server safely.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"portcheck": {
"command": "npx",
"args": [
"-y",
"portcheck-cli",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add portcheck -- npx -y portcheck-cli mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"portcheck": {
"command": "npx",
"args": [
"-y",
"portcheck-cli",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"portcheck": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"portcheck-cli",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account roystondwork-dev, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.11.0) reached the registry 12 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, AvaHR
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
portcheck
See what's using your ports, find free ones, free them up, and check remote hosts.
One static binary for macOS, Linux and Windows.
npx portcheck-cli kill 3000
portcheck shows what holds the port and who started it, asks, then stops it gently (and never touches system processes). It's a safer kill-port, with nothing to install first.
Fixes for the error you're seeing: Node.js, Next.js, Vite · Python, Django, Flask · Docker · Rails, Spring Boot, Go, .NET, PHP · macOS · Windows · Linux
| Command | ||
|---|---|---|
| 🔍 | portcheck list -l | Every listening socket with its process, PID and user |
| ✅ | portcheck 3000 | Is the port free? If not, who holds it? Exit code 0 or 1 for scripts |
| 🆓 | portcheck free 3000-3999 -n 3 | Free ports, verified by actually binding them |
| 🛑 | portcheck kill 8080 | Graceful SIGTERM, then SIGKILL; refuses PID 1, your shell and system processes |
| 🧹 | portcheck servers --older-than 1d | The dev servers you forgot: your listening processes with their project and uptime, oldest first; --stop to clean up |
| 📡 | portcheck scan db.internal -p 5432 | Rate-limited TCP connect checks of remote hosts. No root needed |
| ⏳ | portcheck wait db:5432 -t 60s | Block until services accept connections, or until a port is free. Built for CI |
| ▶️ | portcheck run --port 3000 --next -- npm run dev | Start a command on a free port ($PORT, {port}); take the next one or stop the holder |
| 🩺 | portcheck doctor | Check the ports listed in .portcheck.yaml and get a fix for each problem |
| 🖥️ | portcheck | Live, sortable, filterable TUI. Stop processes without leaving it |
| 🌐 | Browser extension | Edge (and Chrome): which process serves a localhost tab, off when nothing listens, stop it from the popup (guide) |
| 🧩 | VS Code extension | "Port in use" errors in the terminal become one-click fixes; listening ports in the sidebar (guide) |
| 🤖 | portcheck mcp | AI assistants (Claude Code, Cursor, Copilot…) check and free ports themselves (guide) |
| ⌨️ | Raycast | Search Ports, Check Port, Kill Port and Find Free Port from the Mac launcher |
| ✍️ | Neovim | :Portcheck picker, check/kill/free, and "port in use" in :terminal → stop it |
| 🔌 | Menu bar / tray app | Your listening ports in the macOS menu bar or Windows/Linux tray: stop, open, copy in two clicks |
| 🧠 | JetBrains plugin | IntelliJ IDEA, WebStorm, PyCharm, GoLand…: "port in use" in Run/Debug → Stop it and rerun; a Ports tool window |
When a dev server fails because its port is taken, the extension says who holds it and fixes it: stop it and re-run, or re-run on the next free port.
Install Portcheck - Port in Use Fixer from the VS Code Marketplace (search "portcheck" in VS Code) or Open VSX (VSCodium, Cursor, Windsurf). portcheck is built in.
In IntelliJ IDEA, WebStorm, PyCharm, GoLand and the other JetBrains IDEs, when a run configuration fails because its port is taken, a notification names the process and offers Stop it and rerun; the Ports tool window lists every listening port.
Install portcheck-jetbrains- .zip from the latest release (Settings → Plugins → ⚙ → Install Plugin from Disk…); it is in review on JetBrains Marketplace (guide).
On every localhost tab, a badge names the process serving it, or says off when nothing is listening; the popup shows who started it and stops it safely.
Install Portcheck - Localhost Port Inspector from Microsoft Edge Add-ons, then run portcheck browser install once. For Chrome, Brave and Chromium, load the zip from the latest release (guide).
lsof -i, netstat -ano, ss -ltnp and kill.--json follows a versioned schema, exit codes are stable, and results go to stdout while messages go to stderr.kill tells you how to stop it there instead of killing the proxy.pkg/.# Homebrew (macOS, Linux)
brew install roystondwork-dev/tap/portcheck
winget install roystondwork-dev.portcheck
scoop bucket add portcheck https://github.com/roystondwork-dev/scoop-bucket scoop install portcheck
npx portcheck-cli 3000
pipx install portcheck-tool
go install github.com/roystondwork-dev/portcheck/cmd/portcheck@latest
.deb, .rpm, .apk and archives for amd64/arm64 are on the releases page. The checksum file covering every artifact is signed with cosign (keyless), and releases ship SBOMs and SLSA provenance; see verifying downloads.
$ portcheck 3000
PORT PROTO STATUS PID PROCESS USER 3000 tcp in-use 42379 node alice
$ portcheck kill 3000 About to terminate: PID 42379 node (port 3000) Proceed? [y/N] y PID PROCESS RESULT DETAIL 42379 node terminated
$ portcheck free 3000-3999 -n 2 -o plain PORT 3000 3001
$ portcheck list -l --json | jq '.data.sockets[] | {port: .localPort, name: .process.name}'
📖 Documentation: https://roystondwork-dev.github.io/portcheck/ (quickstart · guides · CLI reference · permissions by OS · FAQ)
res, err := inspect.NewSystem().List(ctx, inspect.Filter{Ports: portspec.Single(3000), ListeningOnly: true})
if err != nil { log.Fatal(err) } for _, s := range res.Sockets { if s.Process != nil { // nil when the owner is hidden from your user fmt.Println(s.PID, s.Process.Name) } }
See the library guide for portspec, inspect, freeport, killer, scan, waitfor and containers.
portcheck scan makes ordinary TCP connections and has no stealth features. Only scan hosts and networks you own or are authorized to test.
Contributions are welcome! See CONTRIBUTING.md for setup and standards (every change is tested on Linux, macOS and Windows, with a 100% coverage gate on the library), and TASKS.md for the roadmap and status. Please follow the Code of Conduct, and report vulnerabilities privately as described in SECURITY.md.
MIT © 2026 Royston D and portcheck contributors