Skip to main content
Glama

HostTracker MCP server

validate Smithery Glama score MIT

Connect an AI assistant to HostTracker over the Model Context Protocol and let it operate your monitoring account in conversation: run a live check from 300+ global locations, see what is down, create or pause a monitor, schedule a maintenance window, review incidents, manage who gets alerted, wire a webhook, publish a status page update.

Endpoint   https://mcp.host-tracker.com/mcp
Transport  streamable HTTP
Auth       OAuth 2.1 (sign in when your client asks) - or Authorization: Bearer <HostTracker API token>

This repository is the public face of that hosted server: the connection metadata (server.json), the per-client setup guide (CLIENT.md), and the security policy (SECURITY.md) - and, since 2.0.0, the server's own source code in src/, so you can read exactly what runs behind the endpoint or run a copy yourself (see "Run it yourself" below).

Connect in two minutes

With OAuth (recommended - Claude.ai, Claude Desktop, Claude Code, ChatGPT and any client with an OAuth-capable connector dialog):

  1. Add the endpoint https://mcp.host-tracker.com/mcp as a connector in your client.

  2. Sign in and approve. The client opens HostTracker's sign-in page, then a consent card listing the permissions it asks for (by default: run checks + read monitors). Press Approve. No token ever appears.

  3. Ask in plain language: "is example.com up right now, checked from Europe and Asia?", "which of my monitors are down?", "pause the staging monitor until tomorrow".

Claude Code

With OAuth (no token needed):

claude mcp add --transport http hosttracker https://mcp.host-tracker.com/mcp
# then, inside Claude Code: /mcp -> hosttracker -> Authenticate (opens the sign-in + consent page)

Or with a bearer token in the header:

.mcp.json in your project (or ~/.claude.json for a user-wide connector):

{
  "mcpServers": {
    "hosttracker": {
      "type": "http",
      "url": "https://mcp.host-tracker.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_HOSTTRACKER_API_TOKEN" }
    }
  }
}

Or from the command line:

claude mcp add --transport http hosttracker https://mcp.host-tracker.com/mcp \
  --header "Authorization: Bearer YOUR_HOSTTRACKER_API_TOKEN"

Claude.ai and Claude Desktop

Settings -> Connectors -> Add custom connector -> paste https://mcp.host-tracker.com/mcp -> Connect. The browser opens HostTracker's sign-in + consent page; press Approve and the connector is live. That is the whole setup.

To use a bearer token instead (for example a long-lived token with a hand-picked scope set), Desktop can also connect through the mcp-remote bridge. Edit claude_desktop_config.json:

{
  "mcpServers": {
    "hosttracker": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://mcp.host-tracker.com/mcp",
        "--header", "Authorization:${HT_AUTH}"
      ],
      "env": { "HT_AUTH": "Bearer YOUR_HOSTTRACKER_API_TOKEN" }
    }
  }
}

The ${HT_AUTH} indirection is deliberate: some mcp-remote builds split an argument on its first space, which breaks a literal Authorization: Bearer .... Node.js 18 or newer is required.

Cursor

~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

{
  "mcpServers": {
    "hosttracker": {
      "url": "https://mcp.host-tracker.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_HOSTTRACKER_API_TOKEN" }
    }
  }
}

VS Code (GitHub Copilot agent mode)

.vscode/mcp.json in the workspace. The inputs block keeps the token out of the file, prompting for it once and storing it in the editor's secret storage:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "ht-token",
      "description": "HostTracker API token",
      "password": true
    }
  ],
  "servers": {
    "hosttracker": {
      "type": "http",
      "url": "https://mcp.host-tracker.com/mcp",
      "headers": { "Authorization": "Bearer ${input:ht-token}" }
    }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "hosttracker": {
      "serverUrl": "https://mcp.host-tracker.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_HOSTTRACKER_API_TOKEN" }
    }
  }
}

Run it yourself (Docker)

The hosted endpoint is the normal way to use the server. If you would rather run your own copy - to read the code, audit it, or keep the MCP hop inside your network - the repository builds it from source:

docker build -t hosttracker-mcp https://github.com/HostTracker/mcp.git
docker run --rm -p 8080:8080 hosttracker-mcp

Your copy then answers at http://localhost:8080/mcp and takes exactly the same Authorization: Bearer header: it is a stateless bridge, so it stores nothing and still talks to the public HostTracker API v2 under your token. Without Docker, dotnet run --project src does the same on any machine with the .NET 10 SDK.

The same binary also speaks stdio, for clients that launch the server as a child process instead of connecting to a URL. Add --stdio and pass your token as the HT_TOKEN environment variable (there is no request header on stdio):

HT_TOKEN=YOUR_HOSTTRACKER_API_TOKEN dotnet run --project src -- --stdio
docker run -i --rm -e HT_TOKEN=YOUR_HOSTTRACKER_API_TOKEN hosttracker-mcp --stdio

Logs go to stderr in that mode, so stdout stays a clean protocol stream.

ChatGPT and other clients

ChatGPT (developer mode -> connectors): add https://mcp.host-tracker.com/mcp; ChatGPT offers its "link account" step, which opens HostTracker's sign-in + consent page. Any other client with an OAuth-capable connector dialog works the same way - just the URL.

Any client that can send a static header also works with a bearer token: the endpoint https://mcp.host-tracker.com/mcp and the header Authorization: Bearer YOUR_HOSTTRACKER_API_TOKEN. Where a client's connector form offers an API-key or custom-header authentication mode, the token goes there.

A generic, dependency-free bridge for anything that can only launch a command:

npx -y mcp-remote https://mcp.host-tracker.com/mcp --header "Authorization:${HT_AUTH}"

Longer walkthroughs, verification commands and troubleshooting live in CLIENT.md.

Related MCP server: Uptime Agent MCP Server

What the assistant can do

The server exposes the HostTracker v2 REST API as MCP tools. Every list tool takes limit (maximum 50) and cursor and returns the next cursor; every timestamp is Unix seconds in both directions; ids are opaque strings.

Family

What it covers

Checks

Run an instant check on any URL from 300+ locations (HTTP/S, ping, TCP port, traceroute, DNS, blacklist, WHOIS, Web Risk, crawl, page speed), fetch its result, list the available check types and devices.

Monitors

List, read, create, edit, copy, pause, resume and delete monitors, in single or bulk form, plus the catalogue of monitor types.

Results and incidents

Uptime summaries, raw check results, the incident list, one incident in detail, and comments on an incident.

Maintenance

List, create, edit and delete maintenance windows so planned work does not raise alerts.

Contacts

Manage contacts and contact groups, send and confirm a contact confirmation, and send a test alert to one.

Subscriptions

See who is notified for which monitor, and subscribe or unsubscribe a contact.

Webhooks

Manage webhook endpoints, send a test delivery, review the delivery log and redeliver a failed one.

Status pages

Manage public status pages, publish an incident on one and post follow-up updates.

Reports

Generate a report and list the report types available on your plan.

Jobs

Poll, wait on, cancel or resume the asynchronous jobs that bulk operations and reports return.

Account

Read-only: the account profile, its quota and its current usage. Useful for diagnosing a refused call.

Locations

List the checkpoint pools and individual monitoring locations you can target.

Generic door

describe_api searches the real v2 operations and api_request calls one, for anything without a dedicated tool. It is not a URL proxy: the operation must exist in the published API description, and the safety policy below still applies.

Family

Tools

Checks

run_instant_check, get_check_result, list_check_types

Monitors

list_monitors, get_monitor, create_monitor, update_monitor, delete_monitor, pause_monitor, resume_monitor, copy_monitor, bulk_create_monitors, bulk_update_monitors, bulk_delete_monitors, list_monitor_types

Results and incidents

get_uptime_summary, list_monitor_results, list_incidents, get_incident, comment_incident

Maintenance

list_maintenance, create_maintenance, update_maintenance, delete_maintenance

Contacts

list_contacts, get_contact, create_contact, update_contact, delete_contact, send_contact_confirmation, confirm_contact, test_contact, list_contact_groups, create_contact_group, update_contact_group, delete_contact_group

Subscriptions

list_subscriptions, subscribe_contact, unsubscribe_contact

Webhooks

list_webhooks, create_webhook, update_webhook, delete_webhook, test_webhook, list_webhook_deliveries, redeliver_webhook

Status pages

list_status_pages, get_status_page, create_status_page, update_status_page, delete_status_page, create_status_page_incident, add_status_page_incident_update

Reports

generate_report, list_report_types

Jobs

get_job, wait_for_job, cancel_job, resume_job

Account

get_account, get_account_quota, get_account_usage

Locations

list_locations

Generic door

describe_api, api_request

Three behaviours worth knowing before the first call:

  • Bulk operations validate first. A bulk tool returns a validation report; the write needs an explicit second call with submit=true. Bulk deletion additionally needs confirmed=true and the count the validation pass reported, so a selection that drifted in between is refused.

  • Bulk operations and reports are asynchronous. They answer with a job id; poll it with wait_for_job.

  • Deleting anything is not undoable, so it always takes two calls. A delete tool's first call removes nothing - it returns the resource so the assistant can show you what is about to go - and only a repeat call with confirmed=true deletes. The API returns a receipt listing what was removed.

Authentication and scopes

Two ways in, same permission model:

  • OAuth (connected apps). The client registers itself, you sign in once and approve a scope set on the consent page, and the server mints short-lived access tokens (1 hour) with rotating refresh tokens (90 days) behind the scenes. If the client requests no scopes it gets check + monitor:read. The account family is never grantable to a connected app. Every connection is listed under Integrations -> API -> Connected apps, where one click revokes it (the app then has to ask you again). A tool that needs a scope the connection lacks answers missing_scope naming what is required - reconnect and approve the wider set.

  • Bearer tokens. Mint them at Integrations -> API with a hand-picked scope set, expiration and optional IP allow-list; pass them in the Authorization header.

Scopes are per family with :read and :write leaves that do not imply each other; a bare family name satisfies every leaf under it.

You want the assistant to

Scopes

Run instant checks

check

See monitors, uptime and incidents

monitor:read

Create, edit, pause or delete monitors and maintenance

monitor:write

See who is notified

contact:read, subs:read

Manage contacts and subscriptions

contact:write, subs:write

Manage webhooks

webhook:read, webhook:write

Manage status pages and publish incidents

statuspage:read, statuspage:write

Read quota, usage and limits

account:read (bearer tokens only - not offered to OAuth connections)

Grant the narrowest set that covers the work. There is never a reason to grant account:write: the server refuses every write under /account regardless of what the token allows. If a call comes back refused, ask the assistant to run get_account_quota, which reports the scopes the token actually carries.

Limits and quota

  • The endpoint rate-limits each client IP on /mcp. A limited response carries Retry-After, which the server passes through as a value; it never sleeps or retries on your behalf, so the assistant decides what to do.

  • Your API plan quota is enforced against your own token, exactly as it is for direct REST calls. get_account_usage and get_account_quota report where you stand. Details in the errors and limits guide.

  • Application failures (no token, wrong scope, quota exhausted, invalid input) come back as ordinary tool results with an actionable message rather than a protocol error.

Safety

The server is stateless and stores nothing: every call is forwarded to the API under your own token, and all ownership, quota and rate enforcement happens there. On top of that it refuses, at the server, regardless of the token: any write under /account, and anything touching payments, plans, passwords, login or the minting of API tokens. Content that a checked target controls is wrapped in a fenced, length-capped block before it reaches the model, so a hostile target cannot inject instructions into your assistant. Full policy in SECURITY.md.

License

The contents of this repository (documentation and metadata) are released under the MIT license. The hosted MCP server and the HostTracker service itself are proprietary.

Available Tools

65 tools
add_status_page_incident_updateAInspect

Append an update to a declared incident's timeline (and move its state, e.g. to 'resolved'). Scope 'statuspage:write'. This too is PUBLISHED and notifies subscribers - get the wording approved first.

Inputs: id (required), state (required), message (required), incidentId (required), +1 more.

api_requestA
Destructive
Inspect

Call any HostTracker v2 REST operation that no curated tool covers. Look the operation up with describe_api first - the method and path must match a real operation or the call is refused. The caller's token supplies authorisation and its scopes still apply. Writes under /account are refused outright by this server's safety policy. A DELETE, and any bulk write that is not a /validate dry-run, is refused unless confirmed=true - confirm with the user first, then retry with confirmed=true.

Inputs: path (required), method (required), query, bodyJson, +2 more.

bulk_create_monitorsAInspect

Create many monitors in one asynchronous job. Scope 'monitor:write'. The batch is validated first and, unless submit is true, only the validation report comes back - show it to the user, then call again with submit=true. The submitted job is polled with get_job.

Inputs: itemsJson (required), submit, defaultsJson, idempotencyKey.

bulk_delete_monitorsA
DestructiveIdempotent
Inspect

Delete every monitor a filter selects, as an asynchronous job. HIGHLY DESTRUCTIVE - always show the user the validation count first and get an explicit go-ahead. Called without expectedCount it only validates; the submission needs BOTH confirmed=true and the expectedCount the validation reported, and the API refuses it if the selection drifted meanwhile. Scope 'monitor:write'.

Inputs: filterJson (required), confirmed, expectedCount, idempotencyKey.

bulk_update_monitorsAInspect

Apply one patch to every monitor a filter selects, as an asynchronous job. Scope 'monitor:write'. Without submit=true only the count and a sample of what would be touched come back - show that to the user first.

Inputs: filterJson (required), submit, operation, patchJson, +1 more.

cancel_jobAInspect

Cancel a queued or running asynchronous operation. Items already processed are NOT rolled back - confirm with the user, then read the receipt to see what had been done before the stop.

Inputs: id (required).

comment_incidentAInspect

Annotate an incident with a note (for example the root cause) and get the incident back. Scope 'monitor:write'. The comment replaces any previous one.

Inputs: id (required), comment (required).

confirm_contactAInspect

Confirm a contact with the code it received. Scope 'contact:write'. Ask the user to read the code from their inbox or phone.

Inputs: id (required), code (required).

copy_monitorAInspect

Copy a monitor to one or more new addresses, keeping its configuration. Scope 'monitor:write'. Copying many addresses answers with a job id - poll it with get_job.

Inputs: id (required), urls (required), name, includeAlerts, +2 more.

create_contactAInspect

Create a contact of type email, sms, voiceCall or webPush. Scope 'contact:write'. Sending to a person's address is a real-world action - confirm the address with the user first. The contact is created UNCONFIRMED: a confirmation code is sent to it, and confirm_contact must be called with that code before it receives alerts. For signed HTTP delivery use create_webhook instead.

Inputs: type (required), address (required), name, language, +1 more.

create_contact_groupAInspect

Create a contact group: a named set of contacts, each with the events it should receive. Scope 'contact:write'.

Inputs: name (required), itemsJson (required).

create_maintenanceAInspect

Schedule a maintenance window over an explicit set of monitors. Scope 'monitor:write'. While it runs the covered monitors suppress alerts (and statistics, if asked). Times are Unix seconds.

Inputs: from (required), name (required), monitorIds (required), to, +5 more.

create_monitorAInspect

Create a monitor. Scope 'monitor:write'. Confirm the target and interval with the user first - a monitor consumes an account slot and starts alerting. Attach contacts afterwards with subscribe_contact.

Inputs: type (required), url, name, tags, +5 more.

create_status_pageAInspect

Create a status page. Scope 'statuspage:write'. The page becomes PUBLIC at its slug - agree the slug, the title and which monitors appear with the user before creating it.

Inputs: slug (required), title (required), settingsJson, componentsJson.

create_status_page_incidentAInspect

Declare an incident or a scheduled maintenance on a status page. Scope 'statuspage:write'. This PUBLISHES the message to the page and notifies its subscribers - have the user approve the exact wording first.

Inputs: id (required), title (required), message (required), kind, +6 more.

create_webhookAInspect

Register a webhook. Scope 'webhook:write'. The url must be https and publicly reachable. Events are chosen from: monitor.down, monitor.up, monitor.repeatedlyDown, incident.opened, incident.closed, monitor.created, monitor.updated, monitor.deleted, maintenance.ended, certificate.expiring, domain.expiring, contact.confirmed, contact.updated. The response carries the signing secret once.

Inputs: url (required), events (required), name, tags, +1 more.

delete_contactA
DestructiveIdempotent
Inspect

Delete a contact and every subscription it had. Scope 'contact:write'. DESTRUCTIVE - confirm with the user first (their monitors stop notifying that address), then report the receipt this returns.

Inputs: id (required), confirmed.

delete_contact_groupA
DestructiveIdempotent
Inspect

Delete a contact group. Scope 'contact:write'. DESTRUCTIVE - confirm with the user first. The contacts themselves are not deleted.

Inputs: id (required), confirmed.

delete_maintenanceA
DestructiveIdempotent
Inspect

Cancel a maintenance window. Scope 'monitor:write'. DESTRUCTIVE - confirm with the user first; cancelling an ACTIVE window makes its monitors start alerting again immediately.

Inputs: id (required), confirmed.

delete_monitorA
DestructiveIdempotent
Inspect

Delete one monitor and its subscriptions. Scope 'monitor:write'. DESTRUCTIVE and not undoable - confirm with the user first, then report the deletion receipt this returns.

Inputs: id (required), confirmed.

delete_status_pageA
DestructiveIdempotent
Inspect

Delete a status page with its components, incidents and subscribers. Scope 'statuspage:write'. DESTRUCTIVE and public-facing - confirm with the user first; the slug stops resolving immediately.

Inputs: id (required), confirmed.

delete_webhookA
DestructiveIdempotent
Inspect

Unregister a webhook and stop its deliveries. Scope 'webhook:write'. DESTRUCTIVE - confirm with the user first; pending deliveries are dropped and the signing secret cannot be recovered.

Inputs: id (required), confirmed.

describe_apiA
Read-only
Inspect

Describe the HostTracker v2 REST operations available through api_request: their paths, what each one does, its query parameters and its request-body members. Call it with a search term (e.g. 'contact', '/webhook', 'statuspage') before using api_request, so the call is built from the real contract rather than guessed. All timestamps in this API are Unix seconds and all ids are opaque strings.

Inputs: search.

generate_reportAInspect

Request an uptime report over a set of monitors and a time range. Scope 'monitor:read'. Answers with a job id - poll it with get_job or wait_for_job; the finished job names the report to fetch. Times are Unix seconds.

Inputs: monitorIds (required), to, from, format, +4 more.

get_accountA
Read-only
Inspect

Read the account: identity, package, resource usage, limits and status flags. Scope 'account:read'. Read-only - this server cannot change account settings.

Inputs: no named parameters.

get_account_quotaA
Read-only
Inspect

Read the API quota headroom and the scopes the current token actually carries. Scope 'account:read'. Call this first when another tool returns a 403 - it shows whether the token is simply missing a scope.

Inputs: no named parameters.

get_account_usageA
Read-only
Inspect

Read how many monitors, contacts, reports and maintenance windows the account uses out of what its package allows. Scope 'account:read'.

Inputs: no named parameters.

get_check_resultA
Read-only
Inspect

Fetch the current results of a previously started instant check by its dbId and id (as returned by run_instant_check). Requires a token with the 'check' scope.

Inputs: id (required), dbId (required).

get_contactA
Read-only
Inspect

Read one contact. Scope 'contact:read'. Add expand='subscription' to see what it is subscribed to.

Inputs: id (required), expand.

get_incidentA
Read-only
Inspect

Read one incident with the transitions that opened and closed it. Scope 'monitor:read'.

Inputs: id (required), expand.

get_jobA
Read-only
Inspect

Poll one asynchronous operation: its state, progress and per-item results. A failed job still answers 200 with state='failed'; each failed item carries its own error.

Inputs: id (required), limit, cursor.

get_monitorA
Read-only
Inspect

Read one monitor with its full configuration. Scope 'monitor:read'. Add expand tokens for more detail (settings, uptime, lastResult, lastIncident, subscription, maintenance, attached, spans).

Inputs: id (required), to, from, expand.

get_status_pageA
Read-only
Inspect

Read one status page with its settings and components. Scope 'statuspage:read'.

Inputs: id (required).

get_uptime_summaryA
Read-only
Inspect

Uptime, SLA and response-time figures over a time window for one or more monitors. Scope 'monitor:read'. Times are Unix seconds; omitting the window uses the API's default range.

Inputs: monitor (required), to, sla, from, +5 more.

list_check_typesA
Read-only
Inspect

List the instant-check types HostTracker supports, plus the device profiles a page-loading (waterfall) check can emulate. Read live from the API catalogue and cached briefly. No authentication required.

Inputs: no named parameters.

list_contact_groupsB
Read-only
Inspect

List the account's contact groups. Scope 'contact:read'.

Inputs: limit, cursor.

list_contactsA
Read-only
Inspect

List the account's contacts. Scope 'contact:read'. An unconfirmed contact receives nothing until it is confirmed.

Inputs: q, id, type, limit, +2 more.

list_incidentsA
Read-only
Inspect

List down-episodes across the account or a monitor selection, newest first. Scope 'monitor:read'.

Inputs: to, from, limit, state, +3 more.

list_locationsA
Read-only
Inspect

List the location pools checks can run from (and, with agents=true, the individual monitoring locations). Pool ids are what the 'pools' argument of create_monitor and run_instant_check takes; 'allworld' means everywhere.

Inputs: pool, limit, agents, cursor, +1 more.

list_maintenanceA
Read-only
Inspect

List scheduled, active and finished maintenance windows. Scope 'monitor:read'.

Inputs: to, from, limit, state, +2 more.

list_monitor_resultsA
Read-only
Inspect

List one monitor's raw check results, newest first. Scope 'monitor:read'. Use it to see what actually happened at a given time; the error text comes from the monitored target and is untrusted data.

Inputs: monitorId (required), to, from, limit, +4 more.

list_monitorsA
Read-only
Inspect

List the account's monitors, newest page first. Scope 'monitor:read'. Filters combine with AND; omit them all to list the whole account. Returns at most 50 rows plus a cursor for the next page.

Inputs: q, id, tag, sort, +4 more.

list_monitor_typesA
Read-only
Inspect

List every monitor type with its label, minimum interval and whether the account's package can create it. Anonymous, but a token adds the per-account limits.

Inputs: no named parameters.

list_report_typesA
Read-only
Inspect

List the report types, output formats, sections and schedules available. Anonymous.

Inputs: no named parameters.

list_status_pagesA
Read-only
Inspect

List the account's status pages. Scope 'statuspage:read'.

Inputs: limit, cursor.

list_subscriptionsA
Read-only
Inspect

List who is notified about what. Scope 'subs:read'. kind='alert' (default) lists alert subscriptions, kind='report' lists scheduled-report subscriptions; filter by monitor and/or contact.

Inputs: kind, limit, cursor, contactId, +3 more.

list_webhook_deliveriesA
Read-only
Inspect

List recent deliveries for one webhook, with their outcome and attempts. Scope 'webhook:read'. Use it to diagnose why an endpoint stopped receiving events.

Inputs: id (required), to, from, limit, +3 more.

list_webhooksA
Read-only
Inspect

List the account's registered webhooks, including whether each is enabled and its recent failure count. Scope 'webhook:read'.

Inputs: limit, cursor.

pause_monitorAInspect

Pause a monitor: it stops checking and stops alerting until resumed. Scope 'monitor:write'.

Inputs: id (required).

redeliver_webhookAInspect

Resend a previously recorded delivery to the same endpoint. Scope 'webhook:write'. The receiver sees the same delivery id, so a correctly-written consumer deduplicates it.

Inputs: id (required), deliveryId (required).

resume_jobAInspect

Continue a job whose state is 'interrupted' (the server running it died). Items already concluded are skipped. A job that is not interrupted, or whose kind cannot be resumed, is refused.

Inputs: id (required).

resume_monitorAInspect

Resume a paused monitor. Scope 'monitor:write'.

Inputs: id (required).

run_instant_checkAInspect

Run a free instant website/host check from HostTracker's global monitoring locations and return per-location results. Requires a token with the 'check' scope (mint at Integrations -> API, https://www.host-tracker.com/integrations/api). Starts the check, polls up to ~30s, and returns per-location status plus the public result-page URL; a check that is still running comes back partial with the ids to poll.

Inputs: url (required), type, pools, device, +1 more.

send_contact_confirmationAInspect

Send (or resend) the confirmation code to an unconfirmed contact. Scope 'contact:write'. This delivers a real message to the address; the code itself is never returned to the agent - ask the user for it.

Inputs: id (required).

subscribe_contactAInspect

Subscribe a contact to a monitor. Scope 'monitor:write'. Pass alertTypes for alerting and/or frequencies for scheduled reports; each list REPLACES that leg's current value set for this pair. The contact must be confirmed before anything is actually delivered.

Inputs: contactId (required), monitorId (required), alertTypes, frequencies.

test_contactAInspect

Send a real test alert to a confirmed contact and report how the delivery ended. Scope 'contact:write'. This actually messages the person and may cost account balance for sms/voice - ask first.

Inputs: id (required), alertType.

test_webhookAInspect

Send a synthetic test delivery and report the endpoint's answer. Scope 'webhook:write'. This makes a real request to the configured url; the endpoint's response body is third-party content.

Inputs: id (required), eventName.

unsubscribe_contactA
DestructiveIdempotent
Inspect

Remove a contact's subscription to a monitor. Scope 'monitor:write'. By default both legs are removed; pass kind='alert' or kind='report' for just one. Confirm with the user - they stop being notified.

Inputs: contactId (required), monitorId (required), kind.

update_contactAInspect

Partially update a contact. Scope 'contact:write'. Changing the address re-triggers confirmation.

Inputs: id (required), name, address, language, +2 more.

update_contact_groupAInspect

Rename a contact group and/or REPLACE its membership. Scope 'contact:write'. A members list replaces the whole set, it does not merge.

Inputs: id (required), name, itemsJson.

update_maintenanceAInspect

Reschedule a maintenance window or change what it covers. Scope 'monitor:write'. Only the arguments you pass are changed; a monitorIds list REPLACES the current coverage.

Inputs: id (required), to, from, name, +4 more.

update_monitorAInspect

Partially update a monitor. Scope 'monitor:write'. Only the arguments you pass are changed; everything else stays as it is.

Inputs: id (required), url, name, tags, +5 more.

update_status_pageAInspect

Change a status page's title and/or settings. Scope 'statuspage:write'. The change is immediately visible to the public.

Inputs: id (required), title, settingsJson.

update_webhookAInspect

Change a webhook's url, events, scope, name, or enabled state. Scope 'webhook:write'. Re-enabling an auto-disabled webhook also clears its failure counter.

Inputs: id (required), url, name, events, +2 more.

wait_for_jobA
Read-only
Inspect

Poll a job until it reaches a terminal state or ~30 seconds elapse, then return it. If it is still running when the budget is spent, call this again - it never blocks longer than one slice.

Inputs: id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    TDQS

    A3.7/5.0

    Scored across 65 tools

    Disambiguation4/5

    Most tools map cleanly to resource+action pairs (monitor, contact, webhook, status page, maintenance), so the intended target is usually obvious. A few boundaries are fuzzy: get_account, get_account_quota, and get_account_usage overlap, and monitor incidents vs. status-page incidents/maintenance need careful reading. The api_request catch-all also sits alongside every curated operation.

    Naming Consistency4/5

    The set is overwhelmingly consistent snake_case verb_noun naming with predictable list/get/create/update/delete/bulk prefixes. Minor deviations exist: api_request is not verb-first, and get_ vs list_ plus add_ vs create_ vary slightly without much confusion.

    Tool Count1/5

    65 tools is far beyond the 3-15 well-scoped range and clearly falls in the 50+ extreme-mismatch band. The surface is bloated by single-resource CRUD, bulk variants, job polling helpers, and an api_request fallback that overlap with each other.

    Completeness4/5

    CRUD/lifecycle coverage is broad across monitors, contacts, webhooks, status pages, incidents, maintenance, reports, and instant checks, plus bulk and async operations. Minor gaps remain: a generated report has no dedicated fetch tool, and status-page incident detail/deletion is left to api_request.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A management server for UptimeRobot that enables natural language processing through Model Context Protocol, allowing users to manage monitors, maintenance windows, and reports using conversational commands.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.
      13 npm
      MIT