Analytics

vantaj.co

Manages uptime monitoring projects and monitors, allowing creation, retrieval, updating, and listing of monitors with status and response time data.

1 endpoint13 known toolsFirst detected July 25, 2026Last detected July 25, 2026

ENDPOINT 1

https://api.vantaj.co/mcp

No auth detected

MCP server metadata

Name: vantaj
Version: 1.1.0

Capabilities

tools

Server instructions

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.

Known tools 13

list_projects

List all projects in the workspace.

Inferred read-only

list_monitors

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

Inferred read-only

get_monitor

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

Inferred read-only

create_monitor

Create a new uptime monitor.

Potential side effects

update_monitor

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

Potential side effects

pause_monitor

Pause a monitor - checks stop until it's resumed.

Inferred read-only

resume_monitor

Resume a paused monitor - checks start again immediately.

Inferred read-only

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.

Inferred read-only

list_heartbeats

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

Inferred read-only

list_incidents

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

Inferred read-only

get_incident

Get a single incident by ID.

Inferred read-only

list_domains

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

Inferred read-only

list_status_pages

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vantaj]
url = "https://api.vantaj.co/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: vantaj
Remote MCP URL: https://api.vantaj.co/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "vantaj": {
      "url": "https://api.vantaj.co/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "vantaj": {
      "type": "http",
      "url": "https://api.vantaj.co/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "vantaj",
  "transport": "streamable-http",
  "url": "https://api.vantaj.co/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.