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 CrewAI?
When paired with CrewAI, Healthchecks.io becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Healthchecks.io tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Healthchecks.io in CrewAI
Healthchecks.io and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Healthchecks.io to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Arbox
14 toolsRun your fitness studio or gym with member management, class scheduling, and payment processing in one connected platform.

Apache Superset
7 toolsConnect your AI to Apache Superset. Explore BI dashboards, extract chart data, and run live SQL Lab analytics directly from your terminal.

Keap
11 toolsManage CRM contacts, marketing campaigns, and sales automation via Keap.

Healthchecks.io
13 toolsMonitor cron jobs and background tasks via Healthchecks.io — list checks, track pings, and manage alerts directly from any AI agent.
