World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Inspect, create and adjust Healthchecks cron and uptime checks, and read why one failed
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Healthchecks. Follow https://mcp.popnx.com/i/ni-c-healthchecks-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Healthchecks key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Healthchecks for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "healthchecks": { "command": "npx", "args": [ "-y", "healthchecks-mcp" ], "env": { "HEALTHCHECKS_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For HEALTHCHECKS_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Healthchecks tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
SettingsDeveloperEdit Config
{
"mcpServers": {
"healthchecks": {
"command": "npx",
"args": [
"-y",
"healthchecks-mcp"
],
"env": {
"HEALTHCHECKS_API_KEY": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Healthchecks and tell me what you can do for me, then show me one thing✓ If Claude says it is using Healthchecks or shows a Healthchecks tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
HEALTHCHECKS_URL Site root of a self-hosted instance, e.g. https://hc.example.net (default: https://healthchecks.io)HEALTHCHECKS_READ_ONLY Set to true to register only the read tools (default: false)HEALTHCHECKS_ALLOW_TOOLS Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)HEALTHCHECKS_DENY_TOOLS Comma-separated tool names or list_* prefixes to remove from whatever the allow list leftHEALTHCHECKS_INSECURE_TLS Set to true to accept a self-signed certificate from a self-hosted instance (default: false)Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Healthchecks yet
Healthchecks runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Healthchecks
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Healthchecks key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Healthchecks for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user healthchecks --env HEALTHCHECKS_API_KEY=your-value -- npx -y healthchecks-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For HEALTHCHECKS_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Healthchecks tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user healthchecks --env HEALTHCHECKS_API_KEY=your-value -- npx -y healthchecks-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Healthchecks listed as connected
Use Healthchecks and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Healthchecks or shows a Healthchecks tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
HEALTHCHECKS_URL Site root of a self-hosted instance, e.g. https://hc.example.net (default: https://healthchecks.io)HEALTHCHECKS_READ_ONLY Set to true to register only the read tools (default: false)HEALTHCHECKS_ALLOW_TOOLS Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)HEALTHCHECKS_DENY_TOOLS Comma-separated tool names or list_* prefixes to remove from whatever the allow list leftHEALTHCHECKS_INSECURE_TLS Set to true to accept a self-signed certificate from a self-hosted instance (default: false)Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Healthchecks key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Healthchecks for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "healthchecks": { "command": "npx", "args": [ "-y", "healthchecks-mcp" ], "env": { "HEALTHCHECKS_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For HEALTHCHECKS_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Healthchecks tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Healthchecks settings, HEALTHCHECKS_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Healthchecks and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Healthchecks or shows a Healthchecks tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
HEALTHCHECKS_URL Site root of a self-hosted instance, e.g. https://hc.example.net (default: https://healthchecks.io)HEALTHCHECKS_READ_ONLY Set to true to register only the read tools (default: false)HEALTHCHECKS_ALLOW_TOOLS Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)HEALTHCHECKS_DENY_TOOLS Comma-separated tool names or list_* prefixes to remove from whatever the allow list leftHEALTHCHECKS_INSECURE_TLS Set to true to accept a self-signed certificate from a self-hosted instance (default: false)Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Healthchecks key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Healthchecks for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "healthchecks": { "type": "stdio", "command": "npx", "args": [ "-y", "healthchecks-mcp" ], "env": { "HEALTHCHECKS_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For HEALTHCHECKS_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Healthchecks tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Healthchecks settings, HEALTHCHECKS_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Healthchecks and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Healthchecks or shows a Healthchecks tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
HEALTHCHECKS_URL Site root of a self-hosted instance, e.g. https://hc.example.net (default: https://healthchecks.io)HEALTHCHECKS_READ_ONLY Set to true to register only the read tools (default: false)HEALTHCHECKS_ALLOW_TOOLS Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)HEALTHCHECKS_DENY_TOOLS Comma-separated tool names or list_* prefixes to remove from whatever the allow list leftHEALTHCHECKS_INSECURE_TLS Set to true to accept a self-signed certificate from a self-hosted instance (default: false)Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user healthchecks --env HEALTHCHECKS_API_KEY=your-value -- npx -y healthchecks-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"healthchecks": {
"command": "npx",
"args": [
"-y",
"healthchecks-mcp"
],
"env": {
"HEALTHCHECKS_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"healthchecks": {
"command": "npx",
"args": [
"-y",
"healthchecks-mcp"
],
"env": {
"HEALTHCHECKS_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"healthchecks": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"healthchecks-mcp"
],
"env": {
"HEALTHCHECKS_API_KEY": "your-value"
}
}
}
}HEALTHCHECKS_API_KEY secret required envHEALTHCHECKS_URL envHEALTHCHECKS_READ_ONLY envHEALTHCHECKS_ALLOW_TOOLS envHEALTHCHECKS_DENY_TOOLS envHEALTHCHECKS_INSECURE_TLS envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: healthchecks-mcpoci: ghcr.io/ni-c/healthchecks-mcp:0.3.0Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account ni-c, which owns the repo
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for healthchecks-mcp@0.3.0
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/ni-c-healthchecks-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: HEALTHCHECKS_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (0.3.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Healthchecks | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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: HEALTHCHECKS_ALLOW_TOOLS=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.
It reads the ping bodies. get_ping_body 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 ping_url, no channels — a 40-character unique_key instead. This server addresses checks by either, and get_api_key_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.
It knows where this API is sharp. timeout and schedule cannot be combined because the upstream silently discards one of them; tags are validated against their space separator and keywords against their comma; a new check is given every integration unless you say otherwise, because the API's own default is a check that alerts nobody.
| Variable | Required | Description |
|---|---|---|
HEALTHCHECKS_API_KEY | yes | Project API key. A read-only key works for part of the tool surface — see below |
HEALTHCHECKS_URL | no | Site root of a self-hosted instance, e.g. https://hc.example.net. Default https://healthchecks.io |
HEALTHCHECKS_READ_ONLY | no | true registers only the read tools |
HEALTHCHECKS_ALLOW_TOOLS | no | Comma-separated tool names, list_* prefixes, or essential for a curated preset |
HEALTHCHECKS_DENY_TOOLS | no | Same syntax; removed from whatever HEALTHCHECKS_ALLOW_TOOLS left |
HEALTHCHECKS_INSECURE_TLS | no | true accepts self-signed certificates (scoped to this connection) |
ELICITATION | no | false replaces the approval dialog with the two-call token. Not prefixed |
HEALTHCHECKS_URL is the site root, not the API root: https://hc.example.net, not https://hc.example.net/api/v3. Both are accepted — the suffix is trimmed — because the API documentation spells every example the long way.
Use `https://`. Over plain http the API key travels unencrypted; the server
prints a warning unless the host is local. For self-signed certificates prefer a
proper internal CA over
HEALTHCHECKS_INSECURE_TLS.
Without an API key the server still starts and lists its tools (so registries and inspectors can introspect it), but every call except get_status fails with setup instructions instead of reaching the API.
Read-only keys. Healthchecks gates three tools that only read — list_pings, get_ping_body and list_integrations — behind a read-write key anyway. With a read-only key those fail, along with all five write tools.
The failure does not look like a permission problem: the API answers 401 {"error": "wrong api key"}, which reads as if the key were wrong or missing. It is not — those three tools translate it into what actually happened. get_api_key_info reports which kind of key is configured, and HEALTHCHECKS_DENY_TOOLS is the tidy way to stop offering them at all.
HEALTHCHECKS_ALLOW_TOOLS and HEALTHCHECKS_DENY_TOOLS take comma-separated tool names; a trailing * matches a whole family. essential is a curated preset — list_checks, get_check, list_pings, list_flips, create_check, update_check and resume_check — marked as such in the tool reference.
HEALTHCHECKS_ALLOW_TOOLS=essential
HEALTHCHECKS_ALLOW_TOOLS=list_*,get_check HEALTHCHECKS_DENY_TOOLS=delete_check,pause_check
An entry that matches no tool aborts startup and names it, so a typo cannot silently hide a tool — an absent tool is not something anyone traces back to an environment variable. A filtered tool is never registered, so it is absent from tools/list and unknown to tools/call alike, exactly like a write tool under HEALTHCHECKS_READ_ONLY.
If you run several of these servers at once, mcp-hub is the other answer — its /hub endpoint replaces every server's tools with six meta-tools.
claude mcp add healthchecks-mcp -- npx -y healthchecks-mcp
{
"mcpServers": { "healthchecks-mcp": { "command": "npx", "args": ["-y", "healthchecks-mcp"], "env": { "HEALTHCHECKS_API_KEY": "…" } } } }
[mcp_servers.healthchecks-mcp]
command = "npx" args = ["-y", "healthchecks-mcp"] env = { HEALTHCHECKS_API_KEY = "…" }
docker run --rm -i \
-e HEALTHCHECKS_API_KEY=… \ ghcr.io/ni-c/healthchecks-mcp
Add -e HEALTHCHECKS_URL=https://hc.example.net for a self-hosted instance.
A client that cannot spawn a local process — ChatGPT connectors, Claude on the web, Cursor, LibreChat — reaches healthchecks-mcp through mcp-hub: one container serves many stdio MCP servers over Streamable HTTP, with an OAuth 2.1 login behind a single password and long-lived tokens for the clients that cannot do OAuth. Its /hub endpoint puts every server behind six meta-tools, so one connector reaches all of them without N×tool schemas in the model's context, and it speaks both protocol revisions — a question this server asks travels through it to the person at the far end.
Its /config/mcp.json uses Claude Code's format, so the entry is the one you already have:
{
"mcpServers": { "healthchecks-mcp": { "command": "npx", "args": ["-y", "healthchecks-mcp"], "env": { "HEALTHCHECKS_URL": "https://hc.example.net", "HEALTHCHECKS_API_KEY": "…", "HEALTHCHECKS_ALLOW_TOOLS": "essential" }, "denyTools": ["delete_check,pause_check"] } } }
allowTools and denyTools there are the hub's own per-server filter, which is not the same thing as *_ALLOW_TOOLS in env — the difference, and the mistake it invites, are in the client guide.
Read tools are always registered. 🔑 marks the ones Healthchecks requires a read-write key for even though they only read; 👤 marks the ones that ask for a confirmation token before acting.
| Tool | Description |
|---|---|
list_checks | Checks in the project, with tag, slug and status filters |
get_check | One check with every field, by UUID or unique_key |
list_pings 🔑 | Recent pings of a check, newest first |
get_ping_body 🔑 | The body a job POSTed with one ping — its output |
list_flips | Up/down transitions of a check, with a time window |
list_integrations 🔑 | Notification integrations and the UUIDs the write tools accept |
list_badges | Status badge URLs, per tag and for the project |
get_status | Whether the instance is reachable — needs no API key at all |
get_api_key_info | Which instance, which kind of key, and what that key cannot do |
Write tools are registered unless HEALTHCHECKS_READ_ONLY=true.
| Tool | Description |
|---|---|
create_check | Creates a check. Notifies every integration unless channels says otherwise |
update_check | Changes the given fields. channels replaces the list rather than adding to it; an empty list is refused |
pause_check | Stops the check expecting pings — and alerting. resume_check puts it back |
| resume_check | Puts a paused check back into the new state