Bring Cron Jobs
to VS Code Copilot
Learn how to connect Healthchecks.io to VS Code Copilot and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 VS Code Copilot?
GitHub Copilot Agent mode brings Healthchecks.io data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 13 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Healthchecks.io in VS Code Copilot
Healthchecks.io and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Healthchecks.io to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Public Suffix Extractor
1 toolsExtract the true root domain, TLD, and subdomain from any URL using the official Mozilla Public Suffix List.
FatSecret Platform
6 toolsManage your nutritional research — audit food records and recipes via AI.
Chess.com Global Intelligence
12 toolsThe definitive server for Chess.com — track player ratings, historical games, and daily puzzles via AI.
OpenTHC
12 toolsAutomate cannabis compliance via OpenTHC — track plants, manage inventory, query lab results, and handle B2B/B2C transactions directly from any AI agent.