Skip to content

vantaj.co MCP server

co.vantaj/mcp-servervantaj.costreamable-httpv1.0.0Scanned

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

13 tools: 5 change things and 8 only read.

Tools: 0 delete, 0 irreversible, 5 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the vantaj.co MCP server can do

The vantaj.co MCP server is published by vantaj.co, a domain the MCP Registry verified. It has 13 tools. It can create or change data (5 tools: create_monitor, update_monitor, pause_monitor, resume_monitor and 1 more), but cannot delete data. 8 tools only read.

1 tool brings in text other people can write (list_status_pages); 2 tools can send data out of your system (create_monitor and update_monitor).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Changes things 5Claude Code: ask
  • create_maintenance_windowSchedule a one-time maintenance window: the listed monitors keep running but their alerts are suppressed between starts_at and ends_at.No findings

    Why it is in this group

    • The name "create_maintenance_window" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_monitorCreate a new uptime monitor.Can send data outNo findings

    Why it is in this group

    • The name "create_monitor" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • pause_monitorPause a monitor - checks stop until it's resumed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Pause a monitor - checks stop until it's resumed. Use before planned work on a single target.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • resume_monitorResume a paused monitor - checks start again immediately.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Resume a paused monitor - checks start again immediately.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • update_monitorUpdate a monitor's settings (name, url, interval, inverted, …).Can send data outNo findings

    Why it is in this group

    • The name "update_monitor" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Update a monitor's settings (name, url, interval, inverted, …). Cannot delete.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 8Show 8 read-only tools
  • get_incidentGet a single incident by ID.No findings

    Why it is in this group

    • The name "get_incident" says "get": a word for reading.
    Description, as the server wrote it
    Get a single incident by ID.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_monitorGet a single monitor by ID, including status, uptime, regions, and settings.No findings

    Why it is in this group

    • The name "get_monitor" says "get": a word for reading.
    Description, as the server wrote it
    Get a single monitor by ID, including status, uptime, regions, and settings.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_domainsList tracked domains with expiry dates, registrar, and days remaining.No findings

    Why it is in this group

    • The name "list_domains" says "list": a word for reading.
    Description, as the server wrote it
    List tracked domains with expiry dates, registrar, and days remaining.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_heartbeatsList heartbeat (cron/background job) monitors in a project, with last-ping status.No findings

    Why it is in this group

    • The name "list_heartbeats" says "list": a word for reading.
    Description, as the server wrote it
    List heartbeat (cron/background job) monitors in a project, with last-ping status.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_incidentsList incidents (outages) in a project - open and resolved, with timestamps and duration.No findings

    Why it is in this group

    • The name "list_incidents" says "list": a word for reading.
    Description, as the server wrote it
    List incidents (outages) in a project - open and resolved, with timestamps and duration.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_monitorsList uptime monitors in a project, with current status, response time, and 24h uptime.No findings

    Why it is in this group

    • The name "list_monitors" says "list": a word for reading.
    Description, as the server wrote it
    List uptime monitors in a project, with current status, response time, and 24h uptime.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_projectsList all projects in the workspace.No findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.
    Description, as the server wrote it
    List all projects in the workspace. Call this first - most other tools need a project_id.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_status_pagesList status pages with visibility, slug, and public URL.Reads text others writeNo findings

    Why it is in this group

    • The name "list_status_pages" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List status pages with visibility, slug, and public URL.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.vantaj.co/mcp: tools/list returned 13 tools to an anonymous client, including create_monitor (write), update_monitor (write), pause_monitor (write), resume_monitor (write), create_maintenance_window (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__vantaj__list_projects",
      "mcp__vantaj__list_monitors",
      "mcp__vantaj__get_monitor",
      "mcp__vantaj__list_heartbeats",
      "mcp__vantaj__list_incidents",
      "mcp__vantaj__get_incident",
      "mcp__vantaj__list_domains",
      "mcp__vantaj__list_status_pages"
    ],
    "ask": [
      "mcp__vantaj__create_monitor",
      "mcp__vantaj__update_monitor",
      "mcp__vantaj__pause_monitor",
      "mcp__vantaj__resume_monitor",
      "mcp__vantaj__create_maintenance_window"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vantaj. Review it before you use it.

Capability tags behind 3 rules
  • mcp__vantaj__create_monitor outbound
  • mcp__vantaj__update_monitor outbound
  • mcp__vantaj__list_status_pages untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/co.vantaj/mcp-server/verify?hash=c4189409a3bd305b09db04e8f8a9ceef27b446318728f8e0f0851a1c20dbc8d0" | jq -e '.changed == false'

Pinned hash c4189409a3bd, from Nov 12, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.vantaj/mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.vantaj/mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/co.vantaj/mcp-server.svg)](https://radar.anlyon.com/servers/co.vantaj/mcp-server)

Source: MCP Registry. Synced Oct 21, 2026, 17:47 UTC.

vantaj.co MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the vantaj.co MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the vantaj.co MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the vantaj.co MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the vantaj.co MCP server have?

13 tools: 5 write, 8 read. create_monitor, update_monitor, pause_monitor, resume_monitor, create_maintenance_window, list_projects, list_monitors, get_monitor and 5 more.

Does the vantaj.co MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the vantaj.co MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_monitor and update_monitor.

Has the vantaj.co MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.