Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
See which process holds a port, find free ports, and stop a dev server safely.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"portcheck": {
"command": "npx",
"args": [
"-y",
"portcheck-cli",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add portcheck -- npx -y portcheck-cli mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"portcheck": {
"command": "npx",
"args": [
"-y",
"portcheck-cli",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"portcheck": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"portcheck-cli",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 roystondwork-dev 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.11.0)于12天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Whisper
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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