Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

co.vantaj/mcp-server

REMOTE · API.VANTAJ.CO

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

Available components

0 this week 80 Trust /100

Last scanned (15 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1106 tokens (~85/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.vantaj.co/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vantaj.co CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 35ae39adf552b2dd131827537f088629
SANs: vantaj.co, api.vantaj.co, *.api.vantaj.co
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.vantaj.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
vantaj.co. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.vantaj.co/mcp Verified 200
http (plaintext) http://api.vantaj.co/mcp Inconclusive 405
MCP tools · 13 exposed · ~1,033 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_maintenance_window ~173

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.

NameTypeReqDescription
descriptionstring–Optional details shown alongside the window
ends_atstringyesISO 8601 datetime with offset - must be after starts_at
monitor_idsarrayyesMonitors whose alerts to suppress (from list_monitors)
project_idstringyesProject ID (from list_projects)
starts_atstringyesISO 8601 datetime with offset, e.g. 2026-07-12T02:00:00Z
timezonestring–IANA timezone for display (default UTC)
titlestringyesWindow title, e.g. 'Database migration'
NameTypeReqDescription
dataobjectyesThe resource object

No examples provided.

create_monitor ~200

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

NameTypeReqDescription
expected_status_codesarray–HTTP status codes considered up (default: any 2xx)
groupstring–Optional group name
interval_secondsinteger–Check interval (default 300)
invertedboolean–Exposure monitoring: up while unreachable, alert when reachable
namestringyesDisplay name
project_idstringyesProject ID (from list_projects)
regionsarray–Probe regions (defaults to all)
timeout_secondsinteger–Request timeout in seconds (default 30)
typestringyesCheck type
urlstringyesURL for http, host for ping/smtp, host:port for tcp
NameTypeReqDescription
dataobjectyesThe resource object

No examples provided.

get_incident ~25

Get a single incident by ID.

NameTypeReqDescription
idstringyesIncident ID
NameTypeReqDescription
dataobjectyesThe resource object

No examples provided.

get_monitor ~34

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

NameTypeReqDescription
idstringyesMonitor ID
NameTypeReqDescription
dataobjectyesThe resource object

No examples provided.

list_domains ~61

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

NameTypeReqDescription
cursorstring–Pagination cursor from a previous call
limitinteger–Page size (default 25)
project_idstringyesProject ID (from list_projects)
NameTypeReqDescription
dataarrayyesResult rows
paginationobjectyes–

No examples provided.

list_heartbeats ~68

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

NameTypeReqDescription
cursorstring–Pagination cursor from a previous call
limitinteger–Page size (default 25)
project_idstringyesProject ID (from list_projects)
NameTypeReqDescription
dataarrayyesResult rows
paginationobjectyes–

No examples provided.

list_incidents ~68

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

NameTypeReqDescription
cursorstring–Pagination cursor from a previous call
limitinteger–Page size (default 25)
project_idstringyesProject ID (from list_projects)
NameTypeReqDescription
dataarrayyesResult rows
paginationobjectyes–

No examples provided.

list_monitors ~69

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

NameTypeReqDescription
cursorstring–Pagination cursor from a previous call
limitinteger–Page size (default 25)
project_idstringyesProject ID (from list_projects)
NameTypeReqDescription
dataarrayyesResult rows
paginationobjectyes–

No examples provided.

list_projects ~53

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

NameTypeReqDescription
cursorstring–Pagination cursor from a previous call
limitinteger–Page size (default 25)
NameTypeReqDescription
dataarrayyesResult rows
paginationobjectyes–

No examples provided.

list_status_pages ~61

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

NameTypeReqDescription
cursorstring–Pagination cursor from a previous call
limitinteger–Page size (default 25)
project_idstringyesProject ID (from list_projects)
NameTypeReqDescription
dataarrayyesResult rows
paginationobjectyes–

No examples provided.

pause_monitor ~36

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

NameTypeReqDescription
idstringyesMonitor ID
NameTypeReqDescription
dataobjectyesThe resource object

No examples provided.

resume_monitor ~27

Resume a paused monitor - checks start again immediately.

NameTypeReqDescription
idstringyesMonitor ID
NameTypeReqDescription
dataobjectyesThe resource object

No examples provided.

update_monitor ~158

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

NameTypeReqDescription
expected_status_codesarray–HTTP status codes considered up
groupstring–New group name
idstringyesMonitor ID
interval_secondsinteger–New check interval in seconds
invertedboolean–Enable/disable exposure monitoring (alert when reachable)
namestring–New display name
regionsarray–New probe region list
timeout_secondsinteger–New request timeout in seconds
typestring–New check type
urlstring–New target: URL for http, host for ping/smtp, host:port for tcp
NameTypeReqDescription
dataobjectyesThe resource object

No examples provided.

Install

How do I install the co.vantaj/mcp-server server?

co.vantaj/mcp-server is a hosted endpoint at https://api.vantaj.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.vantaj.co

# add to Claude Code
claude mcp add --transport http co-vantaj-mcp-server 'https://api.vantaj.co/mcp'
Common questions

What is the co.vantaj/mcp-server server?

co.vantaj/mcp-server is listed in the public MCP registry as co.vantaj/mcp-server. Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages. This page covers its hosted endpoint (https://api.vantaj.co/mcp).

Is the co.vantaj/mcp-server server safe to use?

co.vantaj/mcp-server scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the co.vantaj/mcp-server server expose?

co.vantaj/mcp-server exposes 13 tools: list_projects, list_monitors, get_monitor, create_monitor, update_monitor, and 8 more. Their descriptions and schemas cost roughly 1,033 tokens of context every time the server is loaded.

Does the co.vantaj/mcp-server server require authentication?

No. We connected to co.vantaj/mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the co.vantaj/mcp-server server still maintained?

co.vantaj/mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the co.vantaj/mcp-server server?

VerifyMCP ran 12 checks on co.vantaj/mcp-server, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about co.vantaj/mcp-server: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.