co.vantaj/mcp-server

REMOTE · API.VANTAJ.CO · SCANNED AUG 3

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

Available components

+1 this week 68 68 Trust /100

Trust breakdown (6 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 →

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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.vantaj.co

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

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

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-vantaj-mcp-server": {
      "type": "remote",
      "url": "https://api.vantaj.co/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add co-vantaj-mcp-server --url https://api.vantaj.co/mcp --transport streamable-http

# ~/.hermes/config.yaml

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

// mcp.json

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 66

First indexed and scored.

Show 5 earlier entries Hide earlier entries

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 3 Aug 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	20 Jun 2026	18 Sept 2026	ECDSA 256	ECDSA-SHA256	157f923262ef376a13663d7c5bab97cc
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

DNSSEC insecure

Validation of api.vantaj.co. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
co.	present	7786	8	Verified
vantaj.co.	absent			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

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.

Tool Tokens

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

Input Output Examples

Name	Type	Req	Description
description	string	—	Optional details shown alongside the window
ends_at	string	yes	ISO 8601 datetime with offset - must be after starts_at
monitor_ids	array	yes	Monitors whose alerts to suppress (from list_monitors)
project_id	string	yes	Project ID (from list_projects)
starts_at	string	yes	ISO 8601 datetime with offset, e.g. 2026-07-12T02:00:00Z
timezone	string	—	IANA timezone for display (default UTC)
title	string	yes	Window title, e.g. 'Database migration'

Name	Type	Req	Description
data	object	yes	The resource object

No examples provided.

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

Input Output Examples

Name	Type	Req	Description
expected_status_codes	array	—	HTTP status codes considered up (default: any 2xx)
group	string	—	Optional group name
interval_seconds	integer	—	Check interval (default 300)
inverted	boolean	—	Exposure monitoring: up while unreachable, alert when reachable
name	string	yes	Display name
project_id	string	yes	Project ID (from list_projects)
regions	array	—	Probe regions (defaults to all)
timeout_seconds	integer	—	Request timeout in seconds (default 30)
type	string	yes	Check type
url	string	yes	URL for http, host for ping/smtp, host:port for tcp

Name	Type	Req	Description
data	object	yes	The resource object

No examples provided.

get_incident Get incident ~25

Get a single incident by ID.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Incident ID

Name	Type	Req	Description
data	object	yes	The resource object

No examples provided.

get_monitor Get monitor ~34

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	Monitor ID

Name	Type	Req	Description
data	object	yes	The resource object

No examples provided.

list_domains List domains ~61

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

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Pagination cursor from a previous call
limit	integer	—	Page size (default 25)
project_id	string	yes	Project ID (from list_projects)

Name	Type	Req	Description
data	array	yes	Result rows
pagination	object	yes	—

No examples provided.

list_heartbeats List heartbeats ~68

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

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Pagination cursor from a previous call
limit	integer	—	Page size (default 25)
project_id	string	yes	Project ID (from list_projects)

Name	Type	Req	Description
data	array	yes	Result rows
pagination	object	yes	—

No examples provided.

list_incidents List incidents ~68

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

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Pagination cursor from a previous call
limit	integer	—	Page size (default 25)
project_id	string	yes	Project ID (from list_projects)

Name	Type	Req	Description
data	array	yes	Result rows
pagination	object	yes	—

No examples provided.

list_monitors List monitors ~69

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

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Pagination cursor from a previous call
limit	integer	—	Page size (default 25)
project_id	string	yes	Project ID (from list_projects)

Name	Type	Req	Description
data	array	yes	Result rows
pagination	object	yes	—

No examples provided.

list_projects List projects ~53

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

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Pagination cursor from a previous call
limit	integer	—	Page size (default 25)

Name	Type	Req	Description
data	array	yes	Result rows
pagination	object	yes	—

No examples provided.

list_status_pages List status pages ~61

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

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Pagination cursor from a previous call
limit	integer	—	Page size (default 25)
project_id	string	yes	Project ID (from list_projects)

Name	Type	Req	Description
data	array	yes	Result rows
pagination	object	yes	—

No examples provided.

pause_monitor Pause monitor ~36

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	Monitor ID

Name	Type	Req	Description
data	object	yes	The resource object

No examples provided.

resume_monitor Resume monitor ~27

Resume a paused monitor - checks start again immediately.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Monitor ID

Name	Type	Req	Description
data	object	yes	The resource object

No examples provided.

update_monitor Update monitor ~158

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

Input Output Examples

Name	Type	Req	Description
expected_status_codes	array	—	HTTP status codes considered up
group	string	—	New group name
id	string	yes	Monitor ID
interval_seconds	integer	—	New check interval in seconds
inverted	boolean	—	Enable/disable exposure monitoring (alert when reachable)
name	string	—	New display name
regions	array	—	New probe region list
timeout_seconds	integer	—	New request timeout in seconds
type	string	—	New check type
url	string	—	New target: URL for http, host for ping/smtp, host:port for tcp

Name	Type	Req	Description
data	object	yes	The resource object

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	66
27 Jul	67
28 Jul	67
29 Jul	68
30 Jul	69
31 Jul	67
1 Aug	67
2 Aug	68
3 Aug	68