Skip to content
Agentmart
Submit a tool

NodePing MCP by usefulapi

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

Connector by usefulapi.io · Domain verified by the MCP Registry

IndexedMITRemote (HTTP)
Write a review

Install

Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/usefulapi-io-nodeping

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

  • https://nodeping.usefulapi.io/mcp Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
18 read · 0 write · 10 delete
Secrets
None asked for
Install scripts
Nothing to install (hosted)
Runs as
Hosted (remote endpoint)

Tools by what they do 28

From the running server's own tool list (tools/list) on Oct 25, 2026.

Read 18 · Look things up without changing anything.

  • nodeping_get_account
  • nodeping_get_check
  • nodeping_get_check_events
  • nodeping_get_check_results
  • nodeping_get_check_summary
  • nodeping_get_check_uptime
  • nodeping_get_contact
  • nodeping_get_current_events
  • nodeping_get_maintenance
  • nodeping_get_probe_info
  • nodeping_get_schedule
  • nodeping_list_checks
Show 6 more tools
  • nodeping_list_contact_groups
  • nodeping_list_contacts
  • nodeping_list_maintenance
  • nodeping_list_notification_profiles
  • nodeping_list_notifications
  • nodeping_list_schedules

Delete 10 · Delete, drop, revoke or wipe things.

  • nodeping_create_adhoc_maintenance
  • nodeping_create_contact_group
  • nodeping_delete_contact_group
  • nodeping_delete_maintenance
  • nodeping_delete_schedule
  • nodeping_disable_check
  • nodeping_mute_check
  • nodeping_put_schedule
  • nodeping_update_check
  • nodeping_update_contact_group

Network hosts it talks to 1

  • nodeping.usefulapi.io · found in remote endpoint, install command

Tools (28)

As the server listed them on Oct 25, 2026. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • nodeping_create_adhoc_maintenanceCreate ad-hoc maintenancecan change or delete data

    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_groupCreate contact groupcan change or delete data

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

  • nodeping_delete_contact_groupDelete contact groupcan change or delete data

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

  • nodeping_delete_maintenanceDelete maintenance entrycan change or delete data

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

  • nodeping_delete_scheduleDelete notification schedulecan change or delete data

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

  • nodeping_disable_checkDisable checkcan change or delete data

    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_accountGet accountread-only

    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_checkGet checkread-only

    One check by id with its full (scrubbed) configuration. Optionally include its latest result and uptime. GET /checks/{id}.

  • nodeping_get_check_eventsGet check eventsread-only

    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_resultsGet check resultsread-only

    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_summaryGet check hourly summaryread-only

    Hourly summary of a check's results: count, min, max and average run time per UTC hour. GET /results/summary/{id}.

  • nodeping_get_check_uptimeGet check uptimeread-only

    Uptime percentage of a check per day or month (enabled and down milliseconds plus uptime %), with a total. GET /results/uptime/{id}.

  • nodeping_get_contactGet contactread-only

    One contact by id with its addresses (secret-like addresses masked). GET /contacts?id={id}.

  • nodeping_get_current_eventsGet current eventsread-only

    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_maintenanceGet maintenance windowread-only

    One maintenance entry by id. GET /maintenance/{id}.

Show 13 more tools
  • nodeping_get_probe_infoGet probe locationsread-only

    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_scheduleGet notification scheduleread-only

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

  • nodeping_list_checksList checksread-only

    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_groupsList contact groupsread-only

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

  • nodeping_list_contactsList contactsread-only

    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_maintenanceList maintenance windowsread-only

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

  • nodeping_list_notification_profilesList notification profilesread-only

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

  • nodeping_list_notificationsList notifications sentread-only

    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_schedulesList notification schedulesread-only

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

  • nodeping_mute_checkMute or unmute checkcan change or delete data

    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_scheduleCreate or update notification schedulecan change or delete data

    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_checkUpdate check settingscan change or delete data

    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_groupUpdate contact groupcan change or delete data

    WRITE: rename a contact group and/or replace its member list (send the FULL list; omitted members are removed). PUT /contactgroups/{id}.

Signals

Stars
0
Forks
0
Open issues
1
Last commit (this folder)
Oct 24, 2026 (5 days ago)
Last release
Oct 25, 2026 (3 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.usefulapi/nodeping
Version
1.11.0
Auth
Auth not stated
License
MIT
Repository
github.com/m190/usefulapi-mcp
Website
usefulapi.io/nodeping/
First seen
Oct 24, 2026
Last checked
Oct 26, 2026
Source
Official MCP Registrygithub-graphql

More from usefulapi.io

Cite this page

NodePing MCP by usefulapi. Agent Mart. https://agentmart.dev/connectors/usefulapi-io-nodeping (last updated 2026-10-26)