# co.vantaj/mcp-server

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

- name: co.vantaj/mcp-server
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 75/100 flags: no-repository
- quality: 91/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/co.vantaj%2Fmcp-server
- tools: https://api.protogrid.dev/v1/servers/co.vantaj%2Fmcp-server/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 98
- freshness: 65
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-94% ~updated-101d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 91/100 (strong)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 13 of 13 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,974 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 13, about 1,974 tokens to load them all
- tool set hash: 5eb454c011c69a14454ecffcf5177b71
- badge: [![protogrid quality](https://protogrid.dev/badge/co.vantaj/mcp-server.svg)](https://protogrid.dev/servers/co.vantaj/mcp-server)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://api.vantaj.co/mcp (streamable-http, auth none, reachable true, uptime30d 0.9380531)

## Packages

_none_

## 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 planned downtime.
- `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).
- `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.