Vantaj MCP Server

co.vantaj/mcp-server

answering

Vantaj is answering right now. Last checked 14 min ago. It exposes 13 tools.

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

Uptime history 39 hours of history

39 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

144 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

monitor

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_monitor

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

update_monitor

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

domains

list_domains

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

heartbeats

list_heartbeats

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

incident

get_incident

Get a single incident by ID.

incidents

list_incidents

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

maintenance

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.

monitors

list_monitors

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

pause

pause_monitor

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

projects

list_projects

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

resume

resume_monitor

Resume a paused monitor - checks start again immediately.

status

list_status_pages

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

Endpoints

URL	Transport	State	Latency	Checked
https://api.vantaj.co/mcp	streamable-http	answering	172 ms	14 min ago

Vantaj — questions

Answers built from our own checks of this server.

What can Vantaj do?

It exposes 13 tools, read directly from the server on our last check. Among them: create_maintenance_window, create_monitor, get_incident, get_monitor, list_domains, list_heartbeats and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Vantaj working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 144 ms. The bar chart above shows every period we have measured.

How do I connect Vantaj?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Vantaj need an API key?

No. Vantaj completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Vantaj?

It answers our handshake in 144 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.