Is the mcp-orphan-monitor MCP server actively maintained?

The mcp-orphan-monitor MCP server was last committed today and has 1 contributor. Issue health: 50% of issues resolved. AgentRank freshness score reflects real-time maintenance activity.

mcp-orphan-monitor MCP Server

Name: 41fred/mcp-orphan-monitor
Rating: 3.2 (1 reviews)
Author: 41fred

41fred/mcp-orphan-monitor

Score: 55.1 Rank #20 MCP Server

Are you the maintainer of 41fred/mcp-orphan-monitor? Claim this listing →

Detect and kill orphaned MCP server processes that survive after AI coding tool sessions crash or close uncleanly. macOS LaunchAgent + optional menu bar app.

Add AgentRank to Claude Code Discover and compare tools like 41fred/mcp-orphan-monitor — your AI finds the right one automatically

Get API Access →

claude mcp add agentrank -- npx -y agentrank-mcp-server

Overview

41fred/mcp-orphan-monitor is a Shell MCP server licensed under MIT. Detect and kill orphaned MCP server processes that survive after AI coding tool sessions crash or close uncleanly. macOS LaunchAgent + optional menu bar app.

Ranked #20 out of 116 indexed tools.

Actively maintained with commits in the last week.

Ecosystem

Shell MIT

Score Breakdown

Stars 15% 1

1 stars → early stage

Freshness 25% today

Last commit today → actively maintained

Issue Health 25% 50%

No issues filed → no history to score

Contributors 10% 1

1 contributor → solo project

Dependents 25% 0

No dependents → no downstream usage

npm Downloads N/A

PyPI Downloads N/A

Forks 0

Description Detailed

License MIT

Weights: Freshness 25% · Issue Health 25% · Dependents 25% · Stars 15% · Contributors 10% · How we score →

How to Improve

Contributors medium impact

Single-contributor projects carry bus-factor risk — welcoming contributors boosts confidence

Dependents medium impact

No downstream dependents detected yet — adoption by other projects is the strongest trust signal

Badge all embed codes →

Markdown

[![AgentRank](https://agentrank-ai.com/api/badge/tool/41fred--mcp-orphan-monitor)](https://agentrank-ai.com/tool/41fred--mcp-orphan-monitor/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge)

HTML

<a href="https://agentrank-ai.com/tool/41fred--mcp-orphan-monitor/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge"><img src="https://agentrank-ai.com/api/badge/tool/41fred--mcp-orphan-monitor" alt="AgentRank"></a>

Embed Widget docs →

HTML

<script src="https://agentrank-ai.com/embed.js" data-tool="41fred/mcp-orphan-monitor"></script>

Details

Stars: 1
Forks: 0
Open Issues: 0
Closed Issues: 0
Contributors: 1
Dependents: —
Language: Shell
License: MIT
Last Commit: today

Matched Queries

"mcp server""mcp-server"

From the README

# mcp-orphan-monitor

Detect and kill orphaned MCP server processes that survive after AI coding tool sessions crash or close uncleanly.

If you use Claude Code, Cursor, or any MCP-based AI tool, you probably have zombie node processes running right now:

```bash
ps aux | grep mcp-server | grep -v grep
```

## The problem

MCP (Model Context Protocol) servers run as child node processes — one per configured server, per session. When a session ends cleanly, they get killed. When it doesn't (crash, force-quit, closed terminal), they survive as orphans stuck in event loops with no parent.

Each orphan pegs a CPU core at ~50% doing nothing useful. We found 11 orphaned `mcp-server-cloudflare` processes running simultaneously — 550% combined CPU, the oldest burning cycles for 48+ hours.

This is a [known Claude Code issue](https://github.com/anthropics/claude-code/issues/1935) — open since June 2025, still unresolved. Users have reported it with Cloudflare, Todoist, Heroku, Azure DevOps, and

Read full README on GitHub →