Vantaj

co.vantajPublished by vantaj.coOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant manage Vantaj uptime monitors, heartbeats, incidents, and status pages through a remote MCP endpoint.

What you can do
This remote MCP server connects an assistant to Vantaj's uptime monitoring service. According to the registry description, it covers monitors, heartbeats, incidents, and status pages, so an assistant can work with those monitoring objects on the user's Vantaj account. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Worth adding when a team already uses Vantaj for uptime monitoring and wants an assistant to help manage monitors, heartbeats, incidents, or status pages without switching to the web interface. It is not useful for people without a Vantaj account.
Requirements
A remote MCP endpoint at over streamable HTTP. The manifest declares no authentication, environment variables, or headers, and no local package or runtime. A Vantaj account is implied by the service but not stated in the input.
Before you install
The manifest declares no authentication, which is unusual for a service that manages monitoring configuration; verify how access is actually controlled before connecting. The server can likely create, change, or delete monitors, heartbeats, incidents, and status pages, so review any write actions. No credentials, payments, or third-party data flows are shown in the input.

Installation

In SourceWeft

  1. Open Vantaj in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.vantaj%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

13

list_projects

List projects

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

Parameterslimitcursor

list_monitors

List monitors

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

Parameterslimitcursorproject_idrequired

get_monitor

Get monitor

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

Parametersidrequired

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

Parametersurlrequirednamerequiredtyperequiredgroupregionsinvertedproject_idrequiredtimeout_secondsinterval_secondsexpected_status_codes

update_monitor

Update monitor

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

Parametersidrequiredurlnametypegroupregionsinvertedtimeout_secondsinterval_secondsexpected_status_codes

pause_monitor

Pause monitor

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

Parametersidrequired

resume_monitor

Resume monitor

Resume a paused monitor - checks start again immediately.

Parametersidrequired

create_maintenance_window

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.

Parameterstitlerequiredends_atrequiredtimezonestarts_atrequiredproject_idrequireddescriptionmonitor_idsrequired

list_heartbeats

List heartbeats

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

Parameterslimitcursorproject_idrequired

list_incidents

List incidents

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

Parameterslimitcursorproject_idrequired

get_incident

Get incident

Get a single incident by ID.

Parametersidrequired

list_domains

List domains

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

Parameterslimitcursorproject_idrequired

list_status_pages

List status pages

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

Parameterslimitcursorproject_idrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.