NodePing
Monitor website and service uptime, view alerts and manage maintenance windows
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.
Try asking Muse: "Show me which of my monitored services are currently down and when they went offline"
See the most upvoted connectors
Source: Found in the official MCP Registry (io.usefulapi/nodeping) · First listed October 29, 2026
Last 24 hours
Each bar is one check, every 15 minutes. Green means it answered. Last checked 1 h ago.
Is it safe to connect?
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
How to add it to Muse
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. 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.
https://nodeping.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Also use it in ChatGPT or Claude
NodePing is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
Add it to ChatGPT
- 1
Open ChatGPT settings
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
- 2
Turn on developer mode
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
- 3
Create the connector
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
- 4
Use it in a chat
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
Add it to Claude
- 1
Open Claude settings
In Claude, open Settings, then Connectors.
- 2
Add a custom connector
Choose Add custom connector, give it a name, and paste the link.
- 3
Connect and use it
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://nodeping.usefulapi.io/mcpWhat people ask Muse to do
Technical details: safety screening, tools, response time and recent checks
Response time at the last check: 3209ms. Worked in 100% of checks over 30 days.
Screening · October 29, 2026
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
Tools · 28
nodeping_get_accountThe 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_checksList 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_checkOne check by id with its full (scrubbed) configuration. Optionally include its latest result and uptime. GET /checks/{id}.nodeping_get_check_resultsRaw 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_uptimeUptime percentage of a check per day or month (enabled and down milliseconds plus uptime %), with a total. GET /results/uptime/{id}.nodeping_get_check_eventsDown 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_eventsEverything 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_summaryHourly summary of a check's results: count, min, max and average run time per UTC hour. GET /results/summary/{id}.nodeping_list_notificationsThe 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_contactsAll 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_contactOne contact by id with its addresses (secret-like addresses masked). GET /contacts?id={id}.nodeping_list_contact_groupsContact groups (name and member address ids), keyed by group id. GET /contactgroups.nodeping_list_schedulesNotification schedules (per-weekday time windows a contact is alerted in). GET /schedules.nodeping_get_scheduleOne notification schedule by name (for example Days or All) with its seven weekday entries. GET /schedules/{name}.nodeping_list_notification_profilesNotification profiles: named sets of contacts/groups with delay and schedule, reusable across checks. GET /notificationprofiles.nodeping_list_maintenanceScheduled and ad-hoc maintenance entries (checks they disable, cron, duration, next run, last runs). GET /maintenance.nodeping_get_maintenanceOne maintenance entry by id. GET /maintenance/{id}.nodeping_get_probe_infoNodePing'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_checkWRITE: 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_checkWRITE: 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_checkWRITE: 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_maintenanceWRITE: 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_maintenanceWRITE (destructive): remove a maintenance entry. DELETE /maintenance/{id}.nodeping_create_contact_groupWRITE: create a contact group from existing contact address ids. POST /contactgroups.nodeping_update_contact_groupWRITE: rename a contact group and/or replace its member list (send the FULL list; omitted members are removed). PUT /contactgroups/{id}.nodeping_delete_contact_groupWRITE (destructive): delete a contact group. Checks that notify the group lose that notification target. DELETE /contactgroups/{id}.nodeping_put_scheduleWRITE: 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 fnodeping_delete_scheduleWRITE (destructive): delete a notification schedule by name. DELETE /schedules/{name}.Recent checks
Link
https://nodeping.usefulapi.io/mcpQuestions about NodePing in Muse
How do I connect NodePing to Muse?
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.
Is NodePing working right now?
At the last check (October 29, 2026, 10:45 UTC) the endpoint was working, answering in 3209ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
Is NodePing safe to connect to Muse?
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
What can NodePing do in Muse?
It exposes 28 tools, including nodeping_get_account, nodeping_list_checks, nodeping_get_check, nodeping_get_check_results. For example, you could ask Muse: "Show me which of my monitored services are currently down and when they went offline"
Follow NodePing
Made this app? Claim it or get a status badge
Is this yours?
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/nodeping)). If you build NodePing, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/nodeping"><img src="https://musedirectory.ai/badge/nodeping.svg" alt="NodePing on musedirectory.ai" width="236" height="40"></a>