portview MCP server
io.github.Mapika/portview·v2.1.0·59 starsSee what's on your ports, the processes behind them, and diagnose conflicts and leaks.
59 stars
Reviews
Write oneNobody has reviewed portview yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
portview tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How portview compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- GitHub stars
- 59
- more than 95% of 28,688 servers
Install portview in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the portview repository's README, as published. We do not edit it. Read it on GitHub
portview
portview lists ports and the processes using them on Linux, macOS, and Windows. It shows process names, commands, memory usage, and uptime. You can inspect a port, stop its process, or monitor changes in an interactive terminal UI.
It also supports Docker, remote hosts over SSH, and an MCP server for coding agents.
Install
Homebrew:
brew install mapika/tap/portviewLinux / macOS:
curl -fsSL https://raw.githubusercontent.com/mapika/portview/main/install.sh | shWindows (PowerShell):
irm https://raw.githubusercontent.com/mapika/portview/main/install.ps1 | iexOr use cargo install portview, or download a binary from Releases.
What it does
portview # list all listening ports
portview 3000 # inspect port 3000 in detail
portview node # find ports by process name
portview watch # interactive TUI with live refresh
portview watch --docker # TUI with Docker containers as rows
portview kill 3000 --force # terminate the process using port 3000
portview doctor # diagnose port conflicts and issues
portview ssh user@server # inspect ports on a remote host
portview ssh user@server watch # remote TUI over SSH
portview ssh user@server --agentless # no portview needed on the remote
portview mcp # run as an MCP server for AI agentsFeatures
Scan
$ portview
╭──────┬───────┬─────┬──────────────┬──────┬────────────┬────────┬────────┬────────────────────────────╮
│ PORT │ PROTO │ PID │ ADDR │ USER │ PROCESS │ UPTIME │ MEM │ COMMAND │
├──────┼───────┼─────┼──────────────┼──────┼────────────┼────────┼────────┼────────────────────────────┤
│ 3000 │ TCP │ 8 │ 127.0.0.1 │ root │ node │ 7s │ 44 MB │ node /opt/app/web.js │
│ 5000 │ TCP │ 11 │ 127.0.0.1 │ root │ python3.12 │ 7s │ 18 MB │ python3 /opt/app/worker.py │
│ 6380 │ TCP │ 12 │ 127.0.0.1 │ root │ node │ 7s │ 1.2 GB │ node /opt/app/cache.js │
│ 7000 │ TCP │ 10 │ 127.0.0.1 │ root │ node │ 7s │ 45 MB │ node /opt/app/ingest.js │
│ 8080 │ TCP │ 9 │ 127.0.0.1 │ root │ node │ 7s │ 44 MB │ node /opt/app/api.js │
╰──────┴───────┴─────┴──────────────┴──────┴────────────┴────────┴────────┴────────────────────────────╯--all includes non-listening connections, with one row per connection. --wide shows full commands. --json produces JSON output for scripts.
Ports whose owner can't be resolved are still listed, with - in the columns that can't be filled. That happens for another user's process without sudo, and for sockets like TIME_WAIT that outlive the process that opened them.
The scan, doctor, and MCP examples below are real output, captured by demo/record.sh inside an isolated namespace — which is why the user is root and the paths are /opt/app. The Docker example is illustrative, since it needs a running daemon.
MCP server (for AI agents)
portview mcp provides port queries, diagnostics, and process termination over the Model Context Protocol using stdio. To register it with Claude Code:
claude mcp add portview -- portview mcpOr configure it manually:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
portview: common questions
- Is portview MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the portview safety report
- Does portview need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is portview maintained?
- The last commit was 44 days ago (2026-09-21). The latest release is v2.1.0.
- How does portview compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); github stars 59 (more than 95% of 28,688 servers). Full comparison.