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 Cursor?
Cursor's Agent mode turns Healthchecks.io into an in-editor superpower. Ask Cursor to generate code using live data from Healthchecks.io and it fetches, processes, and writes. all in a single agentic loop. 13 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Healthchecks.io in Cursor
Healthchecks.io and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Healthchecks.io to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
X Ads (Twitter)
8 toolsManage your X Ads campaigns — audit accounts, line items, and analytics via AI.

MeasureSquare CRM
11 toolsManage flooring and construction project estimates, client relationships, and job tracking for specialty contractors.

GatherContent
12 toolsManage structured content projects, track items, and oversee workflows via AI agents with GatherContent.

Mailjet
8 toolsSend transactional emails and manage marketing campaigns via the Mailjet REST API.
