GitHub repo analytics: stars, trending, code search, contributor maps for project research.
List all projects in the workspace. Call this first - most other tools need a project_id.
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
What it does
Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.
Quickstart
# 1 — install (mcprush login holds a key from your dashboard)
npx mcprush@latest add api-vantaj-co-mcp-server
# 2 — ask your agent something
> Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.
Mcp Server is free: there is no plan to choose, no cap to set and nothing that can bill you.
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 — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add --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 at the gateway. The server itself runs on the publisher’s own infrastructure, so 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.
Takes no parameters.
List uptime monitors in a project, with current status, response time, and 24h uptime.
Takes no parameters.
Get a single monitor by ID, including status, uptime, regions, and settings.
Takes no parameters.
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).
Takes no parameters.
Update a monitor's settings (name, url, interval, inverted, …). Cannot delete.
Takes no parameters.
Pause a monitor - checks stop until it's resumed. Use before planned work on a single target.
Takes no parameters.
Resume a paused monitor - checks start again immediately.
Takes no parameters.
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.
Takes no parameters.
List heartbeat (cron/background job) monitors in a project, with last-ping status.
Takes no parameters.
List incidents (outages) in a project - open and resolved, with timestamps and duration.
Takes no parameters.
Get a single incident by ID.
Takes no parameters.
List tracked domains with expiry dates, registrar, and days remaining.
Takes no parameters.
List status pages with visibility, slug, and public URL.
Takes no parameters.
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Mcp Server costs nothing to install and nothing to call, 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 a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
Pinned to 1.1.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
No release note was published with this version.
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Writing one takes an account with at least 50 real tool calls against Mcp Server in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.