io.usefulapi/nodeping

up checked 2026-11-11T02:38:24.947Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

NodePing MCP by usefulapi

Publisher-provided description

Read NodePing checks, uptime, results and events; mute checks, manage maintenance and schedules.

Summary by lookupd

Read uptime, check results and incident history; mute or disable checks, and manage maintenance windows, contacts and schedules.

Install

Claude Code, remote (streamable-http)

claude mcp add --transport http nodeping https://nodeping.usefulapi.io/mcp

Codex, remote (streamable-http)

codex mcp add nodeping --url https://nodeping.usefulapi.io/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (28 tools)

Publisher-provided text

• nodeping_get_account The NodePing account the token belongs to (name, status, timezone, next billing date, default probe locations), or a SubAccount with customer_id. GET /accounts.
• nodeping_list_checks List monitoring checks with label, type, target, interval, enabled state and pass/fail (state 1 = passing, 0 = failing; firstdown = when the current outage bega
• nodeping_get_check One check by id with its full (scrubbed) configuration. Optionally include its latest result and uptime. GET /checks/{id}.
• nodeping_get_check_results Raw results of a check, newest first by default: pass/fail (su), run time (rt, ms), message (m), status text (sc), start (s) and the probe location (l). Use spa
• nodeping_get_check_uptime Uptime percentage of a check per day or month (enabled and down milliseconds plus uptime %), with a total. GET /results/uptime/{id}.
• nodeping_get_check_events Down and disabled events of a check (start, end, message, open) newest first: an incident history. limit=1 returns the most recent event. GET /results/events/{i
• nodeping_get_current_events Everything that is down or disabled right now across the account (type, label, since when). The quickest 'what is broken' view. GET /results/current.
• nodeping_get_check_summary Hourly summary of a check's results: count, min, max and average run time per UTC hour. GET /results/summary/{id}.
• nodeping_list_notifications The alert notifications NodePing sent (who, when, what), for one check or for the whole account, newest first. Contact addresses that are webhook URLs or keys a
• nodeping_list_contacts All notification contacts with their addresses (email, SMS, webhook, Slack, ...). Webhook/Slack/PagerDuty/Pushover addresses are masked. Address ids are what co
• nodeping_get_contact One contact by id with its addresses (secret-like addresses masked). GET /contacts?id={id}.
• nodeping_list_contact_groups Contact groups (name and member address ids), keyed by group id. GET /contactgroups.
• nodeping_list_schedules Notification schedules (per-weekday time windows a contact is alerted in). GET /schedules.
• nodeping_get_schedule One notification schedule by name (for example Days or All) with its seven weekday entries. GET /schedules/{name}.
• nodeping_list_notification_profiles Notification profiles: named sets of contacts/groups with delay and schedule, reusable across checks. GET /notificationprofiles.
• nodeping_list_maintenance Scheduled and ad-hoc maintenance entries (checks they disable, cron, duration, next run, last runs). GET /maintenance.
• nodeping_get_maintenance One maintenance entry by id. GET /maintenance/{id}.
• nodeping_get_probe_info NodePing's probe servers (two-letter codes) or regions (nam, lam, eur, eao, wlw): the values a check's run locations use. GET /info/probe[/{code}] or /info/loca
• nodeping_update_check WRITE: change a check's label, description, tags, target, timeout (threshold seconds) or re-checks before alert (sens). Only the fields you pass change. It does
• nodeping_mute_check WRITE: mute a check's notifications (the check keeps running and recording) until a time or indefinitely, or unmute it. mute_until is a future time in ms since
• nodeping_disable_check WRITE: stop a check from running (enabled=false); its history is kept. Re-enabling is done in the NodePing app (it changes the number of billed checks). PUT /ch
• nodeping_create_adhoc_maintenance WRITE: create a one-off maintenance window that disables the listed checks for duration_minutes and re-enables them afterwards (no alerts meanwhile). Created in
• nodeping_delete_maintenance WRITE (destructive): remove a maintenance entry. DELETE /maintenance/{id}.
• nodeping_create_contact_group WRITE: create a contact group from existing contact address ids. POST /contactgroups.
• nodeping_update_contact_group WRITE: rename a contact group and/or replace its member list (send the FULL list; omitted members are removed). PUT /contactgroups/{id}.
• nodeping_delete_contact_group WRITE (destructive): delete a contact group. Checks that notify the group lose that notification target. DELETE /contactgroups/{id}.
• nodeping_put_schedule WRITE: create or update a notification schedule. NodePing stores all seven weekdays at once, so for an existing schedule the weekdays you pass are merged into i
• nodeping_delete_schedule WRITE (destructive): delete a notification schedule by name. DELETE /schedules/{name}.

Details

• Version: 1.24.3
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 515 ms
• First indexed: 2026-11-01T10:05:29.223Z
• Last seen in registry: 2026-11-11T00:17:30.321Z
• Repository: https://github.com/m190/usefulapi-mcp
• Website: https://usefulapi.io/nodeping/

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.usefulapi/nodeping.svg)](https://lookupd.com/servers/io.usefulapi/nodeping)

• 62033 servers
• Last crawl: 2026-11-11T15:38:39.561Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp