Compatible with every major AI agent and IDE
What is the Healthchecks.io MCP Server?
Connect your Healthchecks.io account to any AI agent to monitor and manage your cron jobs, background tasks, and scheduled services through natural conversation.
What you can do
- Check Management — List, create, update, and delete monitoring checks for your infrastructure
- Ping History — Inspect recent pings and payloads to debug failed tasks or verify successful executions
- Status Monitoring — Pause or resume checks and track status 'flips' (up/down transitions) over time
- Integration Overview — List configured notification channels to ensure your team is alerted correctly
- Deep Inspection — Fetch specific check metadata and ping bodies to understand exactly why a service is failing
How it works
- Subscribe to this server
- Enter your Healthchecks.io API Key
- Start monitoring your background jobs from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps Engineers — quickly verify the health of scheduled tasks and investigate downtime without leaving the terminal
- Software Developers — check if background workers are running correctly during development and debugging
- SRE Teams — automate the auditing of monitoring coverage and integration status
Built-in capabilities (13)
Use the unique field to upsert if it already exists. Create a new check
Delete a check
Get a single check by UUID or unique key
Get the body of a specific ping
Check the Healthchecks.io service status
io status badges. List all status badges for the project
Can be filtered by tags or slug. List all checks in the project
List status changes (flips) for a check
List all integrations (channels) in the project
List recent pings for a check
Pause a check
Resume a check
Update an existing check
Why Claude Desktop?
Claude Desktop is the definitive way to connect Healthchecks.io to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 13 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Healthchecks.io in Claude Desktop
Healthchecks.io and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Healthchecks.io to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Healthchecks.io in Claude Desktop
The Healthchecks.io MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 13 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Healthchecks.io for Claude Desktop
Every tool call from Claude Desktop to the Healthchecks.io MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see the specific data sent during a ping to debug a failure?
Yes. Use the get_ping_body tool with the check UUID and ping number to retrieve the exact payload or logs sent by your script during that execution.
How can I see the history of when my service went down?
You can use the list_flips tool. It provides a history of status changes (from 'up' to 'down' and vice versa) for any specific check within a given timeframe.
Is it possible to silence a check without deleting it?
Absolutely. Use the pause_check tool to stop monitoring and alerts for a specific check. You can later use resume_check to start monitoring again.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Standard Notes
10 toolsConnect your AI to the Standard Notes encrypted ecosystem. Sync items natively, modify protected notes, and manage tags seamlessly.

Plausible
10 toolsMonitor website analytics via Plausible — track visitors, pageviews, and bounce rates directly from any AI agent.

Bounsel
9 toolsManage your contract lifecycle via Bounsel — list documents, automate templates, and request signatures directly from any AI agent.

Timezone Offset Engine
1 toolsCalculate the exact offset between two timezones at any moment, with full DST awareness. Powered by Luxon.
