co.vantaj/mcp-server
REMOTE · API.VANTAJ.CO · SCANNED SEP 22
Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- 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 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
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
claude mcp add --transport http co-vantaj-mcp-server 'https://api.vantaj.co/mcp'
{
"mcpServers": {
"co-vantaj-mcp-server": {
"url": "https://api.vantaj.co/mcp"
}
}
} {
"servers": {
"co-vantaj-mcp-server": {
"type": "http",
"url": "https://api.vantaj.co/mcp"
}
}
} [mcp_servers.co-vantaj-mcp-server] url = "https://api.vantaj.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-vantaj-mcp-server": {
"type": "remote",
"url": "https://api.vantaj.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-vantaj-mcp-server --url 'https://api.vantaj.co/mcp' --transport streamable-http
mcp_servers:
co-vantaj-mcp-server:
url: "https://api.vantaj.co/mcp" {
"McpServers": {
"co-vantaj-mcp-server": {
"Transport": "http",
"Url": "https://api.vantaj.co/mcp"
}
}
} assistant mcp add co-vantaj-mcp-server -t streamable-http -u 'https://api.vantaj.co/mcp'
{
"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.
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.
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 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
- 31 Jul 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
- 27 Jul 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 Jul 26 0
First indexed and scored.
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 22 Sept 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 | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 2a654c22351a646d0e1c77f748cb64c2 |
| 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. | 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 |
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 |
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 →
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.
| 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).
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.