What is the main functional difference between Healthchecksio MCP and NotWorking?

Healthchecksio MCP 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 Healthchecksio MCP for monitoring work and NotWorking for monitoring.

How do I install Healthchecksio MCP or NotWorking in Claude Desktop, Cursor, or Windsurf?

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.

Are Healthchecksio MCP and NotWorking free to use, or do they require API keys?

Healthchecksio MCP has no declared pricing — check the project's own site. 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.

Can I run both Healthchecksio MCP and NotWorking at the same time in my AI client?

Yes. MCP clients support multiple servers: add healthchecksio-mcp and notworking as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Healthchecksio MCP has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. NotWorking has 53/100 (Good) with 0 views, 0 installs and 2 GitHub stars.

Healthchecksio MCP vs NotWorking

Healthchecksio MCP vs NotWorking | AllMCPs

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	Healthchecksio MCP	N NotWorking
Category	Monitoring	Monitoring
Quality signal	51/100 · Good	53/100 · Good
Install command	Confirmed	Not confirmed yet
Transport	Local subprocess (stdio)	—
Auth	Not declared	No auth required
Pricing	Not declared	Free
Required env vars	`HEALTHCHECKS_API_KEYHEALTHCHECKS_API_URLHEALTHCHECKS_PING_URL`	None listed
Verified owner	Community listing	Community listing
GitHub stars	0	2
Directory activity	0 views 0 installs 0 upvotes	0 views 0 installs 0 upvotes
Tools	8	2
Full listing	View Healthchecksio MCP	View NotWorking

Tools & capabilities

Healthchecksio MCP tools 8

list_checkslist checks, filter by tag/status
get_checkget a single check's details
create_checkcreate a new check
update_checkupdate a check
list_check_flipsup/down status history
list_channelsnotification channels
list_badgesbadge URLs
pingsend a heartbeat ping (success/fail/start/log)

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.
reportReport that an access path failed for you. Use the access-path id from check_status, or the URL you used. Only report failures that came from the service, not ones caused by your own tools, permissions or settings (like a fetch tool that refuses a domain). Anonymous. Never include personal data, booking details, credentials or full URLs with query strings. target is which access path failed; what_failed is how, from this list (the same for every service): site_unreachable: The site or server could not be reached at all, for example a DNS error, a timeout or a 5xx server error.; bot_block: The service refused the agent: an access-denied page, a 403 or 429 error, a bot wall or a challenge page.; captcha: A CAPTCHA or 'are you human?' check stopped the agent.; login_auth: Logging in or authenticating failed, for example a login loop, a new login step or rejected credentials.; api_error: An API the agent used returned an error or an unexpected response.; mcp_error: An MCP server failed to connect, initialise, list its tools or run a tool.; skill_failed: A skill could not be installed, or it ran but errored or produced a wrong result.; payment: A payment or checkout step failed or was blocked.; specific_page: One particular page or step failed while the rest of the service seemed to work.; other: Something else went wrong.

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.