# Vantaj MCP server

Source: https://glimind.com/server/mcp-registry%2Fco.vantaj%2Fmcp-server
Registry id: `mcp-registry/co.vantaj/mcp-server`
Status: live (checked 2026-11-22T17:06:17.005Z)

## Verdict

Vantaj MCP server answered 100% of Glimind's liveness checks over 30 days, better than 43% of MCP servers, with 129 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (100/100) across 13 tools, costing an agent about 2,030 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 43% of MCP servers |
| Median handshake latency | 129 ms | 78% of MCP servers |
| p95 handshake latency | 327 ms | — |
| Checks in 30 days | 6,870 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 20 min | — |
| Agent-readiness score | 100/100 (A) | 91% of MCP servers |
| Tools | 13 | — |
| Tool-list size for an agent | ~2,030 tokens | 47% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "vantaj-mcp-server": {
      "type": "http",
      "url": "https://api.vantaj.co/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http vantaj-mcp-server https://api.vantaj.co/mcp
```

## Tools (13)

- `create_maintenance_window`: Schedule a one-time maintenance window: the listed monitors keep running but their alerts are suppressed between starts_at and ends_at. Use before deploys or pl
- `create_monitor`: Create a new uptime monitor. Checks start immediately. Types: http, tcp (host:port URL), smtp, ping, ssl, dns. Set inverted=true for exposure monitoring (alert 
- `get_incident`: Get a single incident by ID.
- `get_monitor`: Get a single monitor by ID, including status, uptime, regions, and settings.
- `list_domains`: List tracked domains with expiry dates, registrar, and days remaining.
- `list_heartbeats`: List heartbeat (cron/background job) monitors in a project, with last-ping status.
- `list_incidents`: List incidents (outages) in a project - open and resolved, with timestamps and duration.
- `list_monitors`: List uptime monitors in a project, with current status, response time, and 24h uptime.
- `list_projects`: List all projects in the workspace. Call this first - most other tools need a project_id.
- `list_status_pages`: List status pages with visibility, slug, and public URL.
- `pause_monitor`: Pause a monitor - checks stop until it's resumed. Use before planned work on a single target.
- `resume_monitor`: Resume a paused monitor - checks start again immediately.
- `update_monitor`: Update a monitor's settings (name, url, interval, inverted, …). Cannot delete.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
