Read NodePing checks, uptime, results and events; mute checks, manage maintenance and schedules. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"nodeping": {
"url": "https://nodeping.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"nodeping": {
"type": "http",
"url": "https://nodeping.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your NodePing API token.
Find it in NodePing → Account Settings (API token). API access needs a plan that includes it; SubAccounts have no token. Your token is used only to call the NodePing API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your NodePing API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
nodeping_get_account | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | Get check hourly 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 | read | List notifications sent 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 | read | 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 | read | Get contact One contact by id with its addresses (secret-like addresses masked). GET /contacts?id={id}. |
nodeping_list_contact_groups | read | List contact groups Contact groups (name and member address ids), keyed by group id. GET /contactgroups. |
nodeping_list_schedules | read | List notification schedules Notification schedules (per-weekday time windows a contact is alerted in). GET /schedules. |
nodeping_get_schedule | read | Get notification schedule One notification schedule by name (for example Days or All) with its seven weekday entries. GET /schedules/{name}. |
nodeping_list_notification_profiles | read | List notification profiles Notification profiles: named sets of contacts/groups with delay and schedule, reusable across checks. GET /notificationprofiles. |
nodeping_list_maintenance | read | List maintenance windows Scheduled and ad-hoc maintenance entries (checks they disable, cron, duration, next run, last runs). GET /maintenance. |
nodeping_get_maintenance | read | Get maintenance window One maintenance entry by id. GET /maintenance/{id}. |
nodeping_get_probe_info | read | Get probe locations 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 | Update check settings 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 or unmute 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 | 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 ad-hoc 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 | Delete maintenance entry WRITE (destructive): remove a maintenance entry. DELETE /maintenance/{id}. |
nodeping_create_contact_group | write | Create contact group WRITE: create a contact group from existing contact address ids. POST /contactgroups. |
nodeping_update_contact_group | write | 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 | 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 notification 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_delete_schedule | write | Delete notification schedule WRITE (destructive): delete a notification schedule by name. DELETE /schedules/{name}. |
nodeping_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
nodeping_request_feature | Request a missing feature Tell usefulapi that the user needs something the NodePing tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
nodeping_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED NodePing tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
nodeping_cancel_subscription | Cancel the Pro subscription Cancel the caller's NodePing Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run nodeping_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this NodePing server only. Subscribe with nodeping_upgrade (it returns a Stripe Checkout link). Cancel any time with nodeping_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running nodeping_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by NodePing. The server calls the NodePing API with your own NodePing access, so it sees only the data that your account can see.
The login page asks for your NodePing API token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your NodePing API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the NodePing API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in NodePing.
Yes, if you approve it. 10 of the 28 NodePing tools can create or change data. The other 18 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this NodePing server only. Run nodeping_usage_status to see how many calls you used.
Ask the AI to run nodeping_upgrade: it returns a Stripe Checkout link. To cancel, run nodeping_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with nodeping_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.