# NodePing Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## NodePing

Monitor website and service uptime, view alerts and manage maintenance windows

- Record: https://musedirectory.ai/connector/nodeping
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/nodeping/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 3209ms, checked 2026-10-29T10:45:47Z
- Endpoint: https://nodeping.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T08:01:29Z)
- Source: Found in the official MCP Registry (io.usefulapi/nodeping) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fnodeping

Connects to NodePing uptime monitoring service. Check status of monitored websites and services, view downtime history and incidents, mute alerts, schedule maintenance, and manage notification contacts and groups.

Example request: "Show me which of my monitored services are currently down and when they went offline"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use NodePing to help me. It is a free service with an MCP server at https://nodeping.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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 
- 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 f
- nodeping_delete_schedule: WRITE (destructive): delete a notification schedule by name. DELETE /schedules/{name}.

Screening checks:
- MCP handshake: pass (Answered in 1198ms)
- Domain against threat feeds (Cloudflare security DNS): pass (nodeping.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (28 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)