Vantaj MCP server

• Registry nameco.vantaj/mcp-serververified in the MCP registry

The registry name sits under vantaj.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-19
• Tools13
• Server calls itselfvantaj
• Server version1.1.0
• Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 88 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer245 ms
• Space in an agent's context≈ 1,829 tokensthe definitions of all its tools (13), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results13 of 13 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_projects

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

• list_monitors

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

• get_monitor

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

• 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).

• update_monitor

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

• 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.

• 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.

• 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.

• get_incident

  Get a single incident by ID.

• list_domains

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

• list_status_pages

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