Gatus Health Dashboard MCP. Check System Status with Natural Language Queries
Gatus Health Dashboard MCP lets you monitor your entire service infrastructure using natural conversation. List every monitored endpoint, check its real-time health status, and pull performance metrics—all without leaving your AI agent. It turns complex dashboard checking into simple questions.
Give Claude and any AI agent real-world access
List every monitored endpoint and instantly see its current status across your entire infrastructure.
Drill down into a service to view recent results, historical statuses, and check for patterns of failure or success using its unique key.
Get detailed statistics on an endpoint's speed and reliability, identifying potential latency issues before they become outages.
Access Prometheus-compatible metrics for highly customized reporting or deep technical analysis outside the standard dashboard view.
Ask an AI about this
Waiting for input…
What AI agents can do with Gatus Health Dashboard: 4 Tools
These tools let you query every aspect of your monitored system, from basic endpoint listing to deep performance metric retrieval.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Gatus (Health Dashboard) MCPGet Endpoint Health
Retrieves the current health status and recent results for one specific service endpoint.
Get Endpoint Stats
Pulls key performance statistics, like average latency, for a single designated...
List Endpoints
Provides a comprehensive list of all monitored services and their current...
Get Metrics
Fetches raw, technical performance metrics data from Gatus for custom reporting and...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Gatus (Health Dashboard), then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Gatus. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Dashboard Fatigue Problem
Today, checking if a multi-service application is healthy means logging into the monitoring portal, clicking on the main dashboard. Then you have to open tabs for 'Auth API,' 'Payment Gateway,' and 'User Profiles.' For every single service, you check the green light, copy down the status code, and then manually compare performance metrics like latency or error rates across all those individual views.
With this MCP, you simply ask your agent: 'What's the health of our core services?' Instead of clicking through a dozen screens, you get an immediate, consolidated report. The AI gathers that information using tools like `list_endpoints`, giving you one definitive answer instead of twenty clicks and ten minutes.
Get Status Checks with get_endpoint_health
Before, finding out the status of a specific component meant navigating to that service's dedicated dashboard page. If you were debugging an issue in another tool, you had to stop everything and manually check that other panel just to see if it was working.
Now, your agent handles that lookup instantly. You can ask for `get_endpoint_health` on demand, getting the most current status without disrupting your coding or analysis flow. It's always available when you need it.
What Gatus Health Dashboard MCP does for your AI
You don't need to open a dozen tabs or run manual scripts just to see if your services are up. By connecting this MCP, your AI client becomes a 24/7 Site Reliability Engineering assistant. You can ask it to list all monitored endpoints and instantly get their current health status across the whole system.
Need to know why a service is slow? Ask for performance statistics on that specific endpoint, or pull raw metrics data suitable for deep analysis. This capability means you stop reacting to alerts and start asking questions. The entire catalog of Vinkius makes it simple; connect once from your preferred AI client and get instant visibility into system health.
It's about getting immediate answers: What is the status? How fast was it last time? Did it fail five minutes ago? Your agent handles the complexity, giving you direct insight into service availability when you need it most.
019e389c-e4fa-730d-b998-65c987f911b8 How to set up Gatus Health Dashboard MCP
The bottom line is you get instant system health reports without ever having to manually interact with a web dashboard or run terminal commands.
Subscribe to this MCP and provide your specific Gatus instance URL.
Connect your AI agent to Vinkius. The connection authenticates your access credentials for the monitoring service.
Ask your agent a question, like 'What is the status of the payment gateway?' Your agent calls the necessary tools and returns the structured data.
Who uses Gatus Health Dashboard MCP
This MCP is for ops engineers who are tired of clicking through multiple dashboards at 2 AM. It's essential for SRE teams that need deep performance metrics on demand, and product owners who require quick, high-level reports during an incident.
Quickly audit the health of multiple services and retrieve raw metrics directly through natural language queries instead of leaving the terminal.
Investigate performance regressions or endpoint history by asking targeted questions about latency and uptime over time.
Get high-level, natural language status reports on system availability during an outage without needing to understand the underlying infrastructure metrics.
Benefits of connecting Gatus Health Dashboard MCP
Instant Visibility: Instead of manually navigating a dashboard to see if Service X is up, ask your agent. It uses the list_endpoints tool to give you an immediate summary of all monitored services.
Pinpoint Failures: If something isn't working, don't guess. Use get_endpoint_health to check a specific service and see its most recent failure details instantly.
Diagnose Slowness: When latency spikes, use get_endpoint_stats. This tool shows you the average speed and 99th percentile data so you know exactly where performance is dropping.
Deep Dive Analysis: Need to write a report or build custom tooling? Use get_metrics to pull raw, Prometheus-compatible data that goes far beyond simple status checks.
Operational Efficiency: Your AI agent acts as the ultimate SRE assistant, eliminating the need for multiple context switches between dashboards and terminals.
Gatus Health Dashboard MCP use cases
Investigating an intermittent API outage
The Ops Engineer sees a ticket about fluctuating API availability. Instead of checking three different monitoring panels, they prompt their agent: 'What is the status and performance stats for the user-profile service?' The agent uses get_endpoint_health and then get_endpoint_stats, providing both current failure data and historical latency metrics in one response.
Pre-launch system readiness check
The QA lead needs to confirm every single dependency is green before deployment. They ask the agent to 'List all endpoints.' The agent uses list_endpoints, giving a definitive, real-time status report on the entire connected infrastructure.
Debugging slow payment processing
The Product Owner notices payment transactions are slowing down. They ask the agent to check performance for 'payment-gateway.' The agent uses get_endpoint_stats, confirming if the average latency is spiking and pinpointing exactly which metric changed.
Building custom compliance reports
The Security team needs raw data on all service availability over a period for auditing. They ask the agent to 'Export Prometheus metrics for core services.' The agent executes get_metrics, delivering the structured, technical payload required for external analysis.
Gatus Health Dashboard MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Using the wrong tool for the job
Asking 'How fast is the API?' when you really need historical data. Just checking status (get_endpoint_health) only tells you if it's up or down right now.
To check speed and reliability, you must use get_endpoint_stats. This tool gives you latency metrics (average, 99th percentile) that show performance trends, not just current status.
Assuming raw data is simple
Trying to interpret a massive stream of raw metrics without knowing the format. It looks like garbage text.
If you need raw, deep-dive data for custom tools or analysis, use get_metrics. This tool provides structured Prometheus data ready for your specialized reporting systems.
Ignoring the scope of the check
Asking for 'all metrics' when you only care about one service. You get a huge, unmanageable wall of text.
Always specify which endpoint you need data on. Use get_endpoint_stats or get_endpoint_health and name the exact service key to keep the output focused.
When to use Gatus Health Dashboard MCP
Use this MCP if your workflow requires checking system availability, latency, or historical performance metrics across multiple services in a conversational way. If you need to know 'Is it up?'—this works perfectly. However, don't use this if your only goal is simple notification delivery; for that, a dedicated alerting service might be better suited. Also, if you are building a front-end dashboard and already have the data stream coming from another source, you may not need these tools. But if you are in an IDE or terminal environment and need to query live operational status without context switching, this is exactly what you want. It's your primary tool for real-time infrastructure insight.
Frequently asked questions about Gatus Health Dashboard MCP
How do I list all monitored endpoints using Gatus Health Dashboard MCP? +
You use the list_endpoints tool. This instantly gives you a comprehensive, real-time roster of every service connected to your monitoring system and its current status.
Can I check performance statistics with get_endpoint_stats? +
Yes, using get_endpoint_stats, you can retrieve detailed metrics for a single endpoint. This shows more than just 'up' or 'down,' giving you average latency and reliability data.
What is the difference between get_endpoint_health and get_metrics? +
Use get_endpoint_health for a simple, current status check. Use get_metrics when you need raw, structured Prometheus-compatible data for deep technical analysis or custom reporting.
Does Gatus Health Dashboard MCP work with multiple services? +
Absolutely. The entire MCP is designed to monitor your full infrastructure stack. You can ask about a mix of services, and the agent will use multiple tools to gather all the necessary data.
Can I check an endpoint that failed last week using get_endpoint_health? +
While get_endpoint_health gives recent results, for historical trends or deep dives into past failures, you should use get_endpoint_stats, which tracks performance over time.