healthchecks-mcp

MCPattested
v0.3.0io.github.ni-cMITUpdated 22d agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
22d agoLast update
Needs 1 credential before it runs
  • HEALTHCHECKS_API_KEYAPI keyrequired

    Project API key, exactly 32 characters, from Project Settings → API Access

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.ni-c
LicenseMIT
Version0.3.0
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 331b4af
Dependencies✓ 7 resolved · none vulnerable
Tool surface15 tools · 1 privileged
Security scan✓ Cleanv0.3.0 · todayHow well does this scan work?
EvalsNone
IndexedAug 30, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · 1 privileged
Statically extracted from the published packagev0.3.0 · 21h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

get_statusChecks that the configured Healthchecks instance is reachable and its

Checks that the configured Healthchecks instance is reachable and its

No input schema was published for this tool.

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

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

No input schema was published for this tool.

healthchecks-mcpInspect, create and adjust Healthchecks cron and uptime checks, and read why one failed

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

15 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-29 — observed resolution, not a publisher declaration.

7 packages resolved · 6 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.