External endpointresponds
mcp-server
Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.
Endpoint URL
https://api.vantaj.co/mcpCurrent status
responds
Last checked
Aug 17, 2026, 05:00 AM UTC
Check
MCP initialize · 8s limit
Latency
223 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
co.vantaj/mcp-server
Current observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- vantaj
- Version
- 1.1.0
- Capability keys
- tools
- Tool names
- list_projects, list_monitors, get_monitor, create_monitor, update_monitor, pause_monitor, resume_monitor, create_maintenance_window, list_heartbeats, list_incidents, get_incident, list_domains, list_status_pages
Instructions excerpt
Vantaj Uptime monitoring. Most tools need a project_id - call list_projects first to discover them. Monitor status values: up, degraded, down, paused, unknown. Inverted monitors are UP while their target is unreachable (exposure monitoring). Deleting resources is not possible via MCP - use the dashboard at app.vantaj.co.
Reported Aug 17, 2026, 05:00 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 125ms
- respondsMCP initialize · 8s limit · HTTP 200 · 515ms
- respondsMCP initialize · 8s limit · HTTP 200 · 92ms
- respondsMCP initialize · 8s limit · HTTP 200 · 223ms