INDIVIDUAL MCP TOOL

get_monitor

Get a single monitor by id, including current status, last_checked_at, SSL/HTTP settings, regions, and alerting configuration.

usefulapi.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://betterstack.usefulapi.io/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_monitor and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.betterstack-mcp]
url = "https://betterstack.usefulapi.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "betterstack-mcp": {
      "type": "http",
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: betterstack-mcp
Remote MCP URL: https://betterstack.usefulapi.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "betterstack-mcp": {
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "betterstack-mcp": {
      "type": "http",
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "betterstack-mcp",
  "transport": "streamable-http",
  "url": "https://betterstack.usefulapi.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

list_monitors — List uptime monitors with their status (up/down/paused/pending/maintenance/validating), check frequency, and alert settings.
list_incidents — List incidents (alerts triggered by monitors/heartbeats), filterable by date range, monitor, and acknowledged/resolved state.
get_incident — Get a single incident by id, including cause, status, timeline timestamps (started/acknowledged/resolved), who acknowledged/resolved it, and the related monitor.
list_heartbeats — List heartbeats (cron/background-job monitors that expect a periodic ping), with period, grace, and status (up/down/paused/pending).
list_on_call — List on-call calendars/schedules and the users currently on call for escalation.
list_status_pages — List public/private status pages with company name, subdomain, aggregate_state, and published flag.
acknowledge_incident — Acknowledge an ongoing incident, signalling that someone is looking into it (stops further escalation).
resolve_incident — Resolve an ongoing incident, marking it as handled/closed.