Model Context Protocol server for Rollbar
API Vantaj Co MCP Server is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http api-vantaj-co-mcp-server https://api.vantaj.co/mcp
# 2 — ask your agent for something these tools do
# list_projects, list_monitors, get_monitor and 10 more
API Vantaj Co MCP Server costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http api-vantaj-co-mcp-server https://api.vantaj.co/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all projects in the workspace. Call this first - most other tools need a project_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Page size (default 25) |
| cursor | string | no | Pagination cursor from a previous call |
List uptime monitors in a project, with current status, response time, and 24h uptime.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | Project ID (from list_projects) |
| limit | integer | no | Page size (default 25) |
| cursor | string | no | Pagination cursor from a previous call |
Get a single monitor by ID, including status, uptime, regions, and settings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Monitor ID |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | Project ID (from list_projects) |
| name | string | yes | Display name |
| url | string | yes | URL for http, host for ping/smtp, host:port for tcp |
| type | string | yes | Check type |
| interval_seconds | integer | no | Check interval (default 300) |
| regions | array | no | Probe regions (defaults to all) |
| group | string | no | Optional group name |
| timeout_seconds | integer | no | Request timeout in seconds (default 30) |
| expected_status_codes | array | no | HTTP status codes considered up (default: any 2xx) |
| inverted | boolean | no | Exposure monitoring: up while unreachable, alert when reachable |
Update a monitor's settings (name, url, interval, inverted, …). Cannot delete.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Monitor ID |
| name | string | no | New display name |
| url | string | no | New target: URL for http, host for ping/smtp, host:port for tcp |
| type | string | no | New check type |
| interval_seconds | integer | no | New check interval in seconds |
| regions | array | no | New probe region list |
| group | string | no | New group name |
| timeout_seconds | integer | no | New request timeout in seconds |
| expected_status_codes | array | no | HTTP status codes considered up |
| inverted | boolean | no | Enable/disable exposure monitoring (alert when reachable) |
Pause a monitor - checks stop until it's resumed. Use before planned work on a single target.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Monitor ID |
Resume a paused monitor - checks start again immediately.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Monitor ID |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | Project ID (from list_projects) |
| title | string | yes | Window title, e.g. 'Database migration' |
| description | string | no | Optional details shown alongside the window |
| starts_at | string | yes | ISO 8601 datetime with offset, e.g. 2026-07-12T02:00:00Z |
| 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) |
| timezone | string | no | IANA timezone for display (default UTC) |
List heartbeat (cron/background job) monitors in a project, with last-ping status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | Project ID (from list_projects) |
| limit | integer | no | Page size (default 25) |
| cursor | string | no | Pagination cursor from a previous call |
List incidents (outages) in a project - open and resolved, with timestamps and duration.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | Project ID (from list_projects) |
| limit | integer | no | Page size (default 25) |
| cursor | string | no | Pagination cursor from a previous call |
Get a single incident by ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Incident ID |
List tracked domains with expiry dates, registrar, and days remaining.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | Project ID (from list_projects) |
| limit | integer | no | Page size (default 25) |
| cursor | string | no | Pagination cursor from a previous call |
List status pages with visibility, slug, and public URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | Project ID (from list_projects) |
| limit | integer | no | Page size (default 25) |
| cursor | string | no | Pagination cursor from a previous call |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install API Vantaj Co MCP Server or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish API Vantaj Co MCP Server can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.