NodePing MCP server

Read NodePing checks, uptime, results and events; mute checks, manage maintenance and schedules. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.

Connect NodePing50 free tool calls a month

What can I ask?

Turn on the NodePing connector, then ask in plain words. The AI picks the tools.

Is anything down or disabled across my monitors right now?
What was my website check's uptime for the last month?
Which alert notifications were sent in the last few days?
Mute alerts for my staging site check until tomorrow morning.

What you can do with NodePing in Claude and ChatGPT

For IT and operations teams who monitor servers and sites with NodePing.

See what is down or disabled right now

The AI reads everything that is down or disabled across the account, with the type, label and since when, and lists the checks with their pass or fail state.

Review a check's incidents, uptime and response times

The AI reads the down events of a check, its uptime per day or month, the raw results with run time and probe location, and the hourly run-time summary.

Review who was alerted and who gets alerts

The AI lists the alert notifications that were sent, the contacts and contact groups, and the notification schedules.

Mute, disable or change a check

The AI mutes a check until a time or until you unmute it, stops a check from running, or changes its label, tags, target, timeout or re-checks before an alert.

Changes data

Create, review or delete maintenance windows

The AI creates a one-off maintenance window that disables the listed checks for a number of minutes, lists existing entries, or deletes one.

Changes data

Manage contact groups and notification schedules

The AI creates a contact group from existing contacts, renames it or replaces its members, or creates or changes a weekday notification schedule.

Changes data

How do I connect NodePing?

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.

Claude claude.ai · Desktop

Open Customize → Connectors, then click + Add → Add custom connector.
Enter the name NodePing and this URL, then click Add:
https://nodeping.usefulapi.io/mcp
Claude opens the login page: enter your NodePing API token.
In a chat, click + → Connectors and turn on NodePing.

Team and Enterprise: an Owner adds the connector for the organization first.

ChatGPT chatgpt.com

Open Plugins, click +, then Add custom MCP server.
Enter the name NodePing and this URL, choose OAuth as the authentication, confirm the warning and create it:
https://nodeping.usefulapi.io/mcp
ChatGPT opens the login page: enter your NodePing API token.
In Plugins, install NodePing, then choose it in a chat.

No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.

Claude Code

Run this command, then run /mcp in Claude Code to log in:

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

Cursor

Add to Cursor or add this to ~/.cursor/mcp.json:

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

VS Code

Add to VS Code or add this to .vscode/mcp.json:

{
  "servers": {
    "nodeping": {
      "type": "http",
      "url": "https://nodeping.usefulapi.io/mcp"
    }
  }
}

Codex

Run these commands. The second one opens the login page:

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

codex mcp login nodeping

Other clients

Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.

https://nodeping.usefulapi.io/mcp

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.

Pricing

Plan	Price	Limit
Free	$0	50 tool calls / month
Proper user	$9/mo · $90/yr	10,000 tool calls / month
Pro+per user	$39/mo · $390/yr	100,000 tool calls / month

Each paid plan covers this NodePing server only. Ask your AI to run nodeping_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with nodeping_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with nodeping_upgrade before then undoes the cancel. Or write to support@usefulapi.io.

Tools 32

Show all 32 tools (the AI picks them for you)

Read only · 18

Get accountnodeping_get_account
The NodePing account the token belongs to (name, status, timezone, next billing date, default probe locations), or a SubAccount with customer_id.
List checksnodeping_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 checknodeping_get_check
One check by id with its full (scrubbed) configuration. Optionally include its latest result and uptime.
Get check resultsnodeping_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 check uptimenodeping_get_check_uptime
Uptime percentage of a check per day or month (enabled and down milliseconds plus uptime %), with a total.
Get check eventsnodeping_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 current eventsnodeping_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 check hourly summarynodeping_get_check_summary
Hourly summary of a check's results: count, min, max and average run time per UTC hour.
List notifications sentnodeping_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.
List contactsnodeping_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 contactnodeping_get_contact
One contact by id with its addresses (secret-like addresses masked).
List contact groupsnodeping_list_contact_groups
Contact groups (name and member address ids), keyed by group id.
List notification schedulesnodeping_list_schedules
Notification schedules (per-weekday time windows a contact is alerted in).
Get notification schedulenodeping_get_schedule
One notification schedule by name (for example Days or All) with its seven weekday entries.
List notification profilesnodeping_list_notification_profiles
Notification profiles: named sets of contacts/groups with delay and schedule, reusable across checks.
List maintenance windowsnodeping_list_maintenance
Scheduled and ad-hoc maintenance entries (checks they disable, cron, duration, next run, last runs).
Get maintenance windownodeping_get_maintenance
One maintenance entry by id.
Get probe locationsnodeping_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.

Changes data · 10

Update check settingsnodeping_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.
Mute or unmute checknodeping_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.
Disable checknodeping_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).
Create ad-hoc maintenancenodeping_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.
Delete maintenance entrynodeping_delete_maintenance
WRITE (destructive): remove a maintenance entry.
Create contact groupnodeping_create_contact_group
WRITE: create a contact group from existing contact address ids.
Update contact groupnodeping_update_contact_group
WRITE: rename a contact group and/or replace its member list (send the FULL list; omitted members are removed).
Delete contact groupnodeping_delete_contact_group
WRITE (destructive): delete a contact group. Checks that notify the group lose that notification target.
Create or update notification schedulenodeping_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}.
Delete notification schedulenodeping_delete_schedule
WRITE (destructive): delete a notification schedule by name.

Your usefulapi plan · 4

Usage status (free-tier meter)nodeping_usage_status
Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter.
Request a missing featurenodeping_request_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.
Upgrade to Pro or Pro+nodeping_upgrade
Get a paid plan for NodePing (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place: call without confirm first, as the reply states the exact charge for this account (the price difference for the rest of the period, or in a free Pro trial the full Pro+ price, as the trial ends); then call with confirm: true. Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter.
Cancel the Pro subscriptionnodeping_cancel_subscription
Cancel the caller's NodePing Pro subscription at the end of the paid period (no refund for the current period; Pro continues 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.

FAQ

What can I do with NodePing in Claude or ChatGPT?

See what is down or disabled right now. Review a check's incidents, uptime and response times. Review who was alerted and who gets alerts. Mute, disable or change a check. Create, review or delete maintenance windows. Manage contact groups and notification schedules. See what you can do for the details.

Is this an official NodePing product?

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.

Can I connect NodePing to Claude or ChatGPT?

Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.

What do I need to connect?

The login page asks for your NodePing API token. See Before you connect for where to find it.

Do I put my NodePing key or an Authorization header in the client config?

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.

How do you keep my NodePing credentials?

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.

Can the AI change my NodePing data?

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.

What does it cost?

The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this NodePing server only. Cancel any time: your paid plan then runs to the end of the paid period. Run nodeping_usage_status to see how many calls you used.

How do I subscribe or cancel?

Ask the AI to run nodeping_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run nodeping_cancel_subscription. Your paid plan continues to the end of the paid period.

What if a NodePing tool that I need is missing?

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.

Which AI clients can I use?

Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, 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.

Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.

More Observability MCP servers

All Observability servers →