Connect-MCP

NodePing MCP by usefulapi

io.usefulapi/nodeping · v1.0.0

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

MCPremoteno credentials

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 28 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 86/100

What it does: 28 tools · 18 read, 10 write (incl. delete/pay)

Test call nodeping_get_account: needs a key: HTTP 401 (946 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +8
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://nodeping.usefulapi.io/mcp

Tools

28 tools listed at last check
  • 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 began). Filter client-side by status, type or label text. Compact by default; set detail=true for the full (scrubbed) check objects. GET /checks
  • 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 span (hours) or start/end (ms epoch, ISO 8601 or RFC 2822; GMT unless a zone is given) to bound it. GET /results/{id}.
  • 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/{id}.
  • 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 are masked. GET /notifications[/{check_id}].
  • nodeping_list_contacts All notification contacts with their addresses (email, SMS, webhook, Slack, ...). Webhook/Slack/PagerDuty/Pushover addresses are masked. Address ids are what contact groups and checks reference. GET /contacts.
  • 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/location[/{code}].
  • 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 not enable the check, create checks or touch billing. PUT /checks/{id}.
  • 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 the epoch; omit it with mute=true to mute until unmuted. PUT /checks/{id}.
  • 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 /checks/{id}.
  • 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 inactive unless start_now=true, which starts it immediately. POST /maintenance/ad-hoc.
  • 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 its current ones; a new schedule needs all seven. Per weekday: time1/time2 window (24h), exclude to invert it, disabled for no alerts, allday
  • nodeping_delete_schedule WRITE (destructive): delete a notification schedule by name. DELETE /schedules/{name}.

Badge

Connect-MCP badge for io.usefulapi/nodeping

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/nodeping.svg)](https://clawy.uk/mcp/s/io.usefulapi/nodeping)

Repository · Website