F
licenseB
qualityC
maintenanceEnables safe scanning and cleaning of macOS developer caches and temporary files, with dry-run support and strict refusal to delete non-whitelisted locations.
3
-
janitor-mcp
Related Servers
Alternatives to janitor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to safely reclaim disk space by deleting build artifact directories like node_modules, .venv, and target, with strong guardrails to prevent accidental or malicious deletion.71 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to capture task-scoped residue evidence during test and build workflows, exposing files, directories, processes, and ports for user-authorized cleanup and post-cleanup verification without deleting or modifying anything itself.Apache 2.0
- AlicenseAqualityDmaintenanceEnables AI assistants to monitor and manage Linux infrastructure including services, logs, processes, disk, memory, ports, cron, nginx, Docker, and system health checks via the Model Context Protocol.10MIT
- FlicenseNot gradedqualityBmaintenanceEnables agents to autonomously diagnose Linux performance issues by exposing production-debugging primitives such as perf, strace, /proc, flamegraphs, and eBPF as safe, structured, budgeted tools.-
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT and MCP clients to safely inspect and operate a Linux host through OAuth-protected, workspace-bounded file, Git, process, systemd, and Docker diagnostics, plus human-approved edits and operations.MIT
TDQS
A4/5.0
Scored across 5 tools
Disambiguation4/5
Each tool has a fairly distinct role: health monitoring, orphan scanning, process termination, cache cleaning, and OOM inspection. The only mild overlap is between janitor_scan_orphans (read) and janitor_sweep_processes with target_type='orphans' (write), but the descriptions make the scan-vs-act split clear.
Naming Consistency5/5
All five tools use a uniform janitor_ prefix followed by a snake_case verb_noun pattern (system_health, scan_orphans, sweep_processes, clean_caches, oom_inspect). The convention is consistent throughout with no style deviations.
Tool Count5/5
Five tools is well-scoped for a system janitor: monitor, scan, terminate, clean, and inspect. Each tool earns its place with no redundant or filler operations.
Completeness4/5
The surface covers the core janitor lifecycle: observe health, find orphans, kill processes, clean caches, and assess OOM priority. Minor gaps exist, such as no general disk-usage reporting beyond tmpfs/swap or a way to list configured cache targets, but core workflows are covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues