# co.vantaj/mcp-server (remote · api.vantaj.co)

Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.

- Trust score: 68/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.vantaj.co`: 68/100 (this document), [markdown](https://verifymcp.io/servers/co-vantaj-mcp-server/api.md), [page](https://verifymcp.io/servers/co-vantaj-mcp-server/api)

## Channel facts

- Endpoint: `https://api.vantaj.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1106 tokens (~85/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.co-vantaj-mcp-server]
url = "https://api.vantaj.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-vantaj-mcp-server": {
      "type": "remote",
      "url": "https://api.vantaj.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-vantaj-mcp-server --url https://api.vantaj.co/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-vantaj-mcp-server:
    url: "https://api.vantaj.co/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (13)

### `list_projects` (~53 tokens)

List projects

List all projects in the workspace. Call this first - most other tools need a project_id.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call
- `limit` (integer): Page size (default 25)

Output parameters:

- `data` (array): Result rows
- `pagination` (object)

### `list_monitors` (~69 tokens)

List monitors

List uptime monitors in a project, with current status, response time, and 24h uptime.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call
- `limit` (integer): Page size (default 25)
- `project_id` (string, required): Project ID (from list_projects)

Output parameters:

- `data` (array): Result rows
- `pagination` (object)

### `get_monitor` (~34 tokens)

Get monitor

Get a single monitor by ID, including status, uptime, regions, and settings.

Input parameters:

- `id` (string, required): Monitor ID

Output parameters:

- `data` (object): The resource object

### `create_monitor` (~200 tokens)

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 when a target that should stay down becomes reachable).

Input parameters:

- `expected_status_codes` (array): HTTP status codes considered up (default: any 2xx)
- `group` (string): Optional group name
- `interval_seconds` (integer): Check interval (default 300)
- `inverted` (boolean): Exposure monitoring: up while unreachable, alert when reachable
- `name` (string, required): Display name
- `project_id` (string, required): Project ID (from list_projects)
- `regions` (array): Probe regions (defaults to all)
- `timeout_seconds` (integer): Request timeout in seconds (default 30)
- `type` (string, required): Check type
- `url` (string, required): URL for http, host for ping/smtp, host:port for tcp

Output parameters:

- `data` (object): The resource object

### `update_monitor` (~158 tokens)

Update monitor

Update a monitor's settings (name, url, interval, inverted, …). Cannot delete.

Input parameters:

- `expected_status_codes` (array): HTTP status codes considered up
- `group` (string): New group name
- `id` (string, required): Monitor ID
- `interval_seconds` (integer): New check interval in seconds
- `inverted` (boolean): Enable/disable exposure monitoring (alert when reachable)
- `name` (string): New display name
- `regions` (array): New probe region list
- `timeout_seconds` (integer): New request timeout in seconds
- `type` (string): New check type
- `url` (string): New target: URL for http, host for ping/smtp, host:port for tcp

Output parameters:

- `data` (object): The resource object

### `pause_monitor` (~36 tokens)

Pause monitor

Pause a monitor - checks stop until it's resumed. Use before planned work on a single target.

Input parameters:

- `id` (string, required): Monitor ID

Output parameters:

- `data` (object): The resource object

### `resume_monitor` (~27 tokens)

Resume monitor

Resume a paused monitor - checks start again immediately.

Input parameters:

- `id` (string, required): Monitor ID

Output parameters:

- `data` (object): The resource object

### `create_maintenance_window` (~173 tokens)

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 planned downtime.

Input parameters:

- `description` (string): Optional details shown alongside the window
- `ends_at` (string, required): ISO 8601 datetime with offset - must be after starts_at
- `monitor_ids` (array, required): Monitors whose alerts to suppress (from list_monitors)
- `project_id` (string, required): Project ID (from list_projects)
- `starts_at` (string, required): ISO 8601 datetime with offset, e.g. 2026-07-12T02:00:00Z
- `timezone` (string): IANA timezone for display (default UTC)
- `title` (string, required): Window title, e.g. 'Database migration'

Output parameters:

- `data` (object): The resource object

### `list_heartbeats` (~68 tokens)

List heartbeats

List heartbeat (cron/background job) monitors in a project, with last-ping status.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call
- `limit` (integer): Page size (default 25)
- `project_id` (string, required): Project ID (from list_projects)

Output parameters:

- `data` (array): Result rows
- `pagination` (object)

### `list_incidents` (~68 tokens)

List incidents

List incidents (outages) in a project - open and resolved, with timestamps and duration.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call
- `limit` (integer): Page size (default 25)
- `project_id` (string, required): Project ID (from list_projects)

Output parameters:

- `data` (array): Result rows
- `pagination` (object)

### `get_incident` (~25 tokens)

Get incident

Get a single incident by ID.

Input parameters:

- `id` (string, required): Incident ID

Output parameters:

- `data` (object): The resource object

### `list_domains` (~61 tokens)

List domains

List tracked domains with expiry dates, registrar, and days remaining.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call
- `limit` (integer): Page size (default 25)
- `project_id` (string, required): Project ID (from list_projects)

Output parameters:

- `data` (array): Result rows
- `pagination` (object)

### `list_status_pages` (~61 tokens)

List status pages

List status pages with visibility, slug, and public URL.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call
- `limit` (integer): Page size (default 25)
- `project_id` (string, required): Project ID (from list_projects)

Output parameters:

- `data` (array): Result rows
- `pagination` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-vantaj-mcp-server/api#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 67
- 2026-07-31: 67
- 2026-07-30: 69
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 67
- 2026-07-26: 66

## Links

- Remote endpoint: https://api.vantaj.co/mcp
- Website: https://vantaj.co/docs/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/co-vantaj-mcp-server/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-vantaj-mcp-server/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/co-vantaj-mcp-server/api