_ registry / mcp streamable-http

vantaj

https://api.vantaj.co

Registry code: 8ae881d676b119dd

api record

Vantaj Uptime monitoring. Most tools need a project_id - call list_projects first to discover them. Monitor status values: up, degraded, down, paused, unknown. Inverted monitors are UP while their target is unreachable (exposure monitoring). Deleting resources is not possible via MCP - use the dashboard at app.vantaj.co.

endpoint
https://api.vantaj.co/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 13 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 13 tools
13 never probed 0 of 13 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • pause_monitor unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Monitor ID"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • resume_monitor unknown never probed

    Resume a paused monitor - checks start again immediately.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Monitor ID"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • create_maintenance_window unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id",
    "title",
    "starts_at",
    "ends_at",
    "monitor_ids"
  ],
  "properties": {
    "title": {
      "type": "string",
      "description": "Window title, e.g. 'Database migration'"
    },
    "ends_at": {
      "type": "string",
      "description": "ISO 8601 datetime with offset - must be after starts_at"
    },
    "timezone": {
      "type": "string",
      "description": "IANA timezone for display (default UTC)"
    },
    "starts_at": {
      "type": "string",
      "description": "ISO 8601 datetime with offset, e.g. 2026-07-12T02:00:00Z"
    },
    "project_id": {
      "type": "string",
      "description": "Project ID (from list_projects)"
    },
    "description": {
      "type": "string",
      "description": "Optional details shown alongside the window"
    },
    "monitor_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Monitors whose alerts to suppress (from list_monitors)"
    }
  },
  "additionalProperties": false
}
    arguments 44 lines
  • list_heartbeats unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Page size (default 25)"
    },
    "cursor": {
      "type": "string",
      "description": "Pagination cursor from a previous call"
    },
    "project_id": {
      "type": "string",
      "description": "Project ID (from list_projects)"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • list_incidents unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Page size (default 25)"
    },
    "cursor": {
      "type": "string",
      "description": "Pagination cursor from a previous call"
    },
    "project_id": {
      "type": "string",
      "description": "Project ID (from list_projects)"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • get_incident unknown never probed

    Get a single incident by ID.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Incident ID"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • list_domains unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Page size (default 25)"
    },
    "cursor": {
      "type": "string",
      "description": "Pagination cursor from a previous call"
    },
    "project_id": {
      "type": "string",
      "description": "Project ID (from list_projects)"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • list_status_pages unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Page size (default 25)"
    },
    "cursor": {
      "type": "string",
      "description": "Pagination cursor from a previous call"
    },
    "project_id": {
      "type": "string",
      "description": "Project ID (from list_projects)"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • create_monitor unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id",
    "name",
    "url",
    "type"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "URL for http, host for ping/smtp, host:port for tcp"
    },
    "name": {
      "type": "string",
      "description": "Display name"
    },
    "type": {
      "enum": [
        "http",
        "tcp",
        "smtp",
        "ping",
        "ssl",
        "dns"
      ],
      "type": "string",
      "description": "Check type"
    },
    "group": {
      "type": "string",
      "description": "Optional group name"
    },
    "regions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Probe regions (defaults to all)"
    },
    "inverted": {
      "type": "boolean",
      "description": "Exposure monitoring: up while unreachable, alert when reachable"
    },
    "project_id": {
      "type": "string",
      "description": "Project ID (from list_projects)"
    },
    "timeout_seconds": {
      "type": "integer",
      "maximum": 120,
      "minimum": 1,
      "description": "Request timeout in seconds (default 30)"
    },
    "interval_seconds": {
      "enum": [
        30,
        60,
        180,
        300,
        600,
        1800,
        3600,
        21600,
        86400
      ],
      "type": "integer",
      "description": "Check interval (default 300)"
    },
    "expected_status_codes": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "description": "HTTP status codes considered up (default: any 2xx)"
    }
  },
  "additionalProperties": false
}
    arguments 79 lines
  • update_monitor unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Monitor ID"
    },
    "url": {
      "type": "string",
      "description": "New target: URL for http, host for ping/smtp, host:port for tcp"
    },
    "name": {
      "type": "string",
      "description": "New display name"
    },
    "type": {
      "enum": [
        "http",
        "tcp",
        "smtp",
        "ping",
        "ssl",
        "dns"
      ],
      "type": "string",
      "description": "New check type"
    },
    "group": {
      "type": "string",
      "description": "New group name"
    },
    "regions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "New probe region list"
    },
    "inverted": {
      "type": "boolean",
      "description": "Enable/disable exposure monitoring (alert when reachable)"
    },
    "timeout_seconds": {
      "type": "integer",
      "maximum": 120,
      "minimum": 1,
      "description": "New request timeout in seconds"
    },
    "interval_seconds": {
      "enum": [
        30,
        60,
        180,
        300,
        600,
        1800,
        3600,
        21600,
        86400
      ],
      "type": "integer",
      "description": "New check interval in seconds"
    },
    "expected_status_codes": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "description": "HTTP status codes considered up"
    }
  },
  "additionalProperties": false
}
    arguments 76 lines
  • list_projects unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Page size (default 25)"
    },
    "cursor": {
      "type": "string",
      "description": "Pagination cursor from a previous call"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • list_monitors unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Page size (default 25)"
    },
    "cursor": {
      "type": "string",
      "description": "Pagination cursor from a previous call"
    },
    "project_id": {
      "type": "string",
      "description": "Project ID (from list_projects)"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • get_monitor unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Monitor ID"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8ae881d676b119dd/badge.svg)](https://brick.blue/agent/8ae881d676b119dd)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.