MCP.Market

Healthchecks MCP server

by ni-c·io.github.ni-c/healthchecks-mcp·v0.3.0
No reviews yet

Inspect, create and adjust Healthchecks cron and uptime checks, and read why one failed

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

0 stars33 downloads/wk

Reviews

Write one

Nobody has reviewed Healthchecks yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Healthchecks tools (14, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • create_checkwrite action

    Creates a check. Pass either timeout (a simple period) or schedule (a

  • delete_checkwrite action

    Deletes a check permanently. Its UUID is not recoverable, so every

  • get_api_key_info

    Reports which instance is configured, whether the API key works, and

  • get_check

    Fetches one check with all its fields, including the description and

  • get_ping_body

    Returns the body that was POSTed with one ping — usually the output of

  • get_status

    Checks that the configured Healthchecks instance is reachable and its

  • list_badges

    Lists the status badge URLs of the project, one entry per tag plus "*"

  • list_checks

    Lists the checks in the project the API key belongs to, newest state

  • list_flips

    Lists the up/down transitions of a check — the history behind its

  • list_integrations

    Lists the notification integrations of the project, with the UUIDs that

  • list_pings

    Lists recent pings of a check, newest first. The instance caps this at

  • pause_check

    Pauses a check: it stops expecting pings and stops alerting.

  • resume_check

    Resumes a paused check and puts it back into the "new" state, waiting

  • update_checkwrite action

    Updates a check. Fields that are not given stay unchanged. Two

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • Code scan29 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Healthchecks compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Tools
14
the typical server has 7
Tools that change things
21%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
33
more than 22% of 12,191 servers with a package

What its tools let an agent do: 11 read · 1 create · 1 change · 1 delete

Install Healthchecks in Claude Code, Cursor or VS Code

Runs npx -y healthchecks-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add healthchecks-mcp -- npx -y healthchecks-mcp
Add to Cursor

What the publisher says

From the Healthchecks repository's README, as published. We do not edit it. Read it on GitHub

healthchecks-mcp

<!-- badges: start -->

<!-- badges: end -->

A Model Context Protocol (MCP) server for Healthchecks, the dead man's switch for cron jobs and scheduled tasks — it alerts you when a job stops checking in. Works against the hosted service and against a self-hosted instance alike.

Lets MCP clients like Claude Code, Claude Desktop or Codex see which scheduled jobs are healthy, read the output the failing one reported, and create or adjust checks — with the irreversible operations behind a confirmation token and the write tools switchable off entirely.

Fourteen tools is the ceiling, not the floor: HEALTHCHECKSALLOWTOOLS=essential registers a curated seven instead, and a model picks the right tool far more reliably from seven than from fourteen — see choosing which tools load.

What makes it different

It reads the ping bodies. getpingbody returns what a job actually printed when it reported failure. Every other question — which check is down, since when, how often — is one step away from that one, and it is the endpoint the other Healthchecks MCP servers leave out.

Read-only API keys work properly. Healthchecks hands a read-only key a different object: no uuid, no pingurl, no channels — a 40-character uniquekey instead. This server addresses checks by either, and getapikey_info tells you up front which kind of key you configured and which tools it cannot reach, rather than leaving you with a 401 missing api key for a key that was sent.

It never pings a check. Pinging is how a job reports that it ran. A tool that could ping would let a model make a dead job look alive, which is the one thing monitoring must not allow — see Not exposed, on purpose.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Healthchecks: common questions

Is Healthchecks MCP server safe?
Mostly: it is graded B (83/100). Read the Healthchecks safety report
How do I install Healthchecks?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Healthchecks need an API key?
Yes. The registry entry asks for HEALTHCHECKS_API_KEY.
Is Healthchecks maintained?
The last commit was 20 days ago (2026-10-15). The latest release is v0.3.0.
How does Healthchecks compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 14 (the typical server has 7); tools that change things 21% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from ni-c →