Compatible with every major AI agent and IDE
What is the Gatus (Health Dashboard) MCP Server?
Connect your Gatus health dashboard to any AI agent to monitor your services and infrastructure through natural conversation.
What you can do
- Global Visibility — List all monitored endpoints and their current health status across your entire infrastructure.
- Deep Health Inspection — Drill down into specific services to see recent results and status history using slugified keys.
- Performance Statistics — Retrieve performance metrics for individual endpoints to identify latency or reliability issues.
- Metrics Export — Access raw Prometheus-compatible metrics for deep technical analysis and custom reporting.
How it works
- Subscribe to this server
- Enter your Gatus instance URL
- Start monitoring your system health from Claude, Cursor, or any MCP-compatible client.
No more manual dashboard checking. Your AI acts as a 24/7 SRE assistant, providing instant insights into your service availability.
Who is this for?
- DevOps Engineers — quickly audit service health and retrieve raw metrics without leaving the terminal or IDE.
- SRE Teams — investigate performance regressions and endpoint history through natural language queries.
- Product Owners — get high-level status reports on system availability during incidents.
Built-in capabilities (4)
Get health status and recent results for a specific endpoint
Get performance statistics for a specific endpoint
Get Prometheus-compatible metrics from Gatus
Get all monitored endpoints and their current status
Why CrewAI?
When paired with CrewAI, Gatus (Health Dashboard) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Gatus (Health Dashboard) 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
Gatus (Health Dashboard) in CrewAI
Gatus (Health Dashboard) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Gatus (Health Dashboard) 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 Gatus (Health Dashboard) in CrewAI
The Gatus (Health Dashboard) 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 4 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
Gatus (Health Dashboard) for CrewAI
Every tool call from CrewAI to the Gatus (Health Dashboard) 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 status of all my services at once?
Yes! Use the list_endpoints tool to retrieve a complete list of all configured endpoints and their current health status across your Gatus instance.
How do I check the performance history of a specific service?
You can use get_endpoint_stats with the endpoint's slugified key to see detailed performance statistics, or get_endpoint_health for recent health check results.
Does this server provide raw metrics for analysis?
Yes, the get_metrics tool retrieves raw Prometheus-compatible metrics exported by Gatus, allowing your AI to perform deep technical analysis.
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 →
Autodesk Construction Cloud
10 toolsManage projects, files, issues, and assets in Autodesk Construction Cloud natively via AI.

Mattermark
10 toolsStartup and venture capital data via Mattermark — search companies, investors, and funding rounds.

Harmonic
11 toolsAutomate company and startup intelligence via Harmonic — enrich domains, track funding, and discover investors directly from any AI agent.

InvestorLift
5 toolsAutomate real estate deal sourcing via InvestorLift — list marketplace deals, manage your buy box criteria, and message sellers directly from any AI agent.
