Homebutler vs NotWorking
A side-by-side look at the Homebutler and NotWorking MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
NotWorkingMonitoringDowndetector for AI agents: is a site, MCP server or skill failing for everyone? Check and report.53GoodAuth: no auth requiredVerdict: choose Homebutler for monitoring work as a local process; choose NotWorking for monitoring. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Homebutler when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
proxmox_status, proxmox_guests, proxmox_node.
NChoose NotWorking when
- You need dedicated capabilities in the Monitoring domain.
- Its auth model fits you: No auth required.
- You want tools like
check_status, report.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N NotWorking | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 65/100 · Great | 53/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Homebutler tools 40
proxmox_statusGet Proxmox VE version, cluster status, and resourcesproxmox_guestsList Proxmox QEMU and LXC guests, optionally filtered by node, status, or typeproxmox_nodeGet detailed Proxmox node statusproxmox_tasksGet the 50 most recent Proxmox tasks for a nodesystem_statusGet system status including CPU, memory, disk usage, and uptimeproxmox_guest_startStart one explicitly targeted Proxmox guest after confirmation and return the accepted task UPIDproxmox_guest_rebootReboot one explicitly targeted Proxmox guest after confirmation and return the accepted task UPIDproxmox_guest_shutdownGracefully shut down one explicitly targeted Proxmox guest after confirmation and return the accepted task UPIDproxmox_task_statusInspect one asynchronous Proxmox task by node and opaque UPIDproxmox_script_listList the curated Proxmox VE Community Scripts catalog (community-scripts/ProxmoxVE)proxmox_script_commandRender the pinned install command for one Proxmox VE Community Script. Never fetches or runs it; the caller reviews and runs it themselves on the Proxmox hostdocker_listList Docker containers with their status, image, and ports- +28 more on the listing page
NotWorking tools 2
check_statusIs it down or blocking agents for everyone, or just you? Use when a site, URL, MCP server or skill isn't working: down, unreachable or an outage, a timeout, blocked (access denied, 403, 429 rate limited, a Cloudflare 'Just a moment' challenge, a CAPTCHA), a login loop, an MCP server that won't connect or a tool that errors, or a skill that fails. Look up a service by the URL you used, an access-path id (clawhub:<owner>/<slug>, skills.sh:<owner>/<repo>/<skill>, an MCP Registry name like io.github.<owner>/<server>) or a service name. Returns a one-sentence summary, the service, every listed access path with a description and failure reports from the last hour (and the last 24 hours as context), the what_failed values and how to report. Unlisted targets return their own counts and status, with listed: false.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Homebutler
{
"mcpServers": {
"higangssh-homebutler": {
"command": "npx",
"args": [
"-y",
"homebutler@latest"
]
}
}
}
NotWorking
No confirmed install command for NotWorking yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Homebutler is categorized under Monitoring and uses a local stdio subprocess. NotWorking belongs to Monitoring and uses an install path we have not confirmed yet. Pick Homebutler for monitoring work and NotWorking for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. NotWorking has no confirmed install command yet — follow its own setup instructions.
Homebutler is listed as free. Auth: no auth required. NotWorking is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add higangssh-homebutler and notworking as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Homebutler has a quality signal of 65/100 (Great) with 3 views, 0 installs and 300 GitHub stars. NotWorking has 53/100 (Good) with 0 views, 0 installs and 2 GitHub stars.
