This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
What's Running MCP
Stop AI agents from reporting dead services as live
Every agent session starts blind. It reads a stale doc or an old transcript, decides your dev server is running, and health-checks a process that died three weeks ago. Model memory is a cache with no invalidation. Five read-only tools answer from the OS instead: live agent sessions (pid, uptime, cwd), every TCP LISTEN socket with its owning process, loaded daemons, and system load/disk. No shell, no writes, no network. MIT and free. macOS first; Linux best-effort.
Hey Product Hunt 👋
I run several coding-agent sessions at once, and the same failure kept happening: a session would tell me a service was live because a doc or an old transcript said so. I'd go check and the process had been dead for weeks. Model memory is a cache with no invalidation — the OS is the only thing that actually knows.
So I wrote a shell script that just asks the machine. It got used at the start of every session, so I wrapped it in MCP.
Five tools:
• whats_running — the whole snapshot in one call, meant for session start
• agent_sessions — which agent processes are actually alive, terminal-attached vs detached/orphan, with pid, uptime and working directory
• listening_ports — every TCP LISTEN socket and the process that owns it
• daemons — launchctl on macOS, systemd --user on Linux
• system_stats — load average, uptime, root-disk free
Constraints I held myself to:
• Read-only by construction. Every call is a fixed binary with fixed flags via execFile — no shell, and nothing the model produces is ever executed. The only model-controlled inputs are a boolean and a substring filter applied in-process.
• Never blocking. 10s timeouts; a failing probe degrades to an empty result instead of erroring the snapshot.
• It does disclose your machine — process names, pids, working directories, ports. That's the entire point, and also why you shouldn't attach it to a client you don't trust. It says so in the README.
MIT and free. No account, no telemetry, no paid tier. macOS is my daily driver so it's strongest there; Linux is best-effort and would really benefit from someone running it in anger.
It's a brand-new repo with zero stars, so what I'm actually after is criticism: what's missing, what would you want a sixth tool to answer, and does the read-only argument hold up when you look at the source?
github.com/stcmain/whats-running-mcp
About What's Running MCP on Product Hunt
“Stop AI agents from reporting dead services as live”
What's Running MCP was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #141 on the daily leaderboard. Every agent session starts blind. It reads a stale doc or an old transcript, decides your dev server is running, and health-checks a process that died three weeks ago. Model memory is a cache with no invalidation. Five read-only tools answer from the OS instead: live agent sessions (pid, uptime, cwd), every TCP LISTEN socket with its owning process, loaded daemons, and system load/disk. No shell, no writes, no network. MIT and free. macOS first; Linux best-effort.
On the analytics side, What's Running MCP competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how What's Running MCP performed against the three products that launched closest to it on the same day.
Who hunted What's Running MCP?
What's Running MCP was hunted by Shift The Culture. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of What's Running MCP including community comment highlights and product details, visit the product overview.
Shift The Culture