NodePing MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

NodePing MCP by usefulapi is answering right now. Last checked 12 min ago. It exposes 28 tools. Last commit 12 Oct 2026.

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

Uptime history 5 hours of history

5 hours agonow

100.0%

Uptime 24h

17 of 17 checks

Tools

read from the server

213 ms

Response time

average over 24h

Stars

last commit 12 Oct 2026

Nothing serious here today

Today is the operative word: we check NodePing MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.nodeping]
url = "https://nodeping.usefulapi.io/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 28

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

nodeping

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_create_contact_group

WRITE: create a contact group from existing contact address ids. POST /contactgroups.

nodeping_delete_contact_group

WRITE (destructive): delete a contact group. Checks that notify the group lose that notification target. DELETE /contactgroups/{id}.

nodeping_delete_maintenance

WRITE (destructive): remove a maintenance entry. DELETE /maintenance/{id}.

nodeping_delete_schedule

WRITE (destructive): delete a notification schedule by name. DELETE /schedules/{name}.

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_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_get_check

One check by id with its full (scrubbed) configuration. Optionally include its latest result and uptime. GET /checks/{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_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_summary

Hourly summary of a check's results: count, min, max and average run time per UTC hour. GET /results/summary/{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_contact

One contact by id with its addresses (secret-like addresses masked). GET /contacts?id={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_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_get_schedule

One notification schedule by name (for example Days or All) with its seven weekday entries. GET /schedules/{name}.

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_list_contact_groups

Contact groups (name and member address ids), keyed by group id. GET /contactgroups.

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_list_maintenance

Scheduled and ad-hoc maintenance entries (checks they disable, cron, duration, next run, last runs). GET /maintenance.

nodeping_list_notification_profiles

Notification profiles: named sets of contacts/groups with delay and schedule, reusable across checks. GET /notificationprofiles.

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_schedules

Notification schedules (per-weekday time windows a contact is alerted in). GET /schedules.

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_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 for always. GET then PUT /schedules/{name}.

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_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}.

Endpoints

URL	Transport	State	Latency	Checked
https://nodeping.usefulapi.io/mcp	streamable-http	answering	162 ms	12 min ago

Alternatives to NodePing MCP by usefulapi

same job, measured the same way

SavvyCal MCP by usefulapi

by usefulapi

Read and create SavvyCal scheduling links and booked events.

8 tools answering

Reclaim.ai MCP by usefulapi

by usefulapi

Read tasks, habits, events and scheduling links; create and update Reclaim tasks and habits.

15 tools answering

Status.io MCP by usefulapi

by usefulapi

Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status.

20 tools answering

StatusCake MCP by usefulapi

by usefulapi

Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.

21 tools answering

Instatus MCP by usefulapi

by usefulapi

Manage status pages: components, incidents and maintenances; set live component status.

14 tools answering

Healthchecks.io MCP by usefulapi

by usefulapi

Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.

12 tools answering

OptimoRoute MCP by usefulapi

by usefulapi

Check OptimoRoute routes, orders and driver events, and create orders or start route planning.

15 tools answering

Mindbody MCP by usefulapi

by usefulapi

Read Mindbody classes, schedules, clients, staff and sales; book clients and appointments.

20 tools answering

NodePing MCP by usefulapi — questions

Answers built from our own checks of this server.

What can NodePing MCP by usefulapi do?

It exposes 28 tools, read directly from the server on our last check. Among them: nodeping_create_adhoc_maintenance, nodeping_create_contact_group, nodeping_delete_contact_group, nodeping_delete_maintenance, nodeping_delete_schedule, nodeping_disable_check and 22 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is NodePing MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 17 of 17 checks got a reply (100.0%), average response time 213 ms. The bar chart above shows every period we have measured.

How do I connect NodePing MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does NodePing MCP by usefulapi need an API key?

No. NodePing MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 28 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is NodePing MCP by usefulapi?

It answers our handshake in 213 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is NodePing MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.