NodePing MCP by usefulapi
io.usefulapi/nodepingusefulapi.iostreamable-httpv1.27.4Scanned
Read NodePing checks, uptime, results and events; mute checks, manage maintenance and schedules.
28 tools: 10 can delete or cancel things, 1 change things and 17 only read.
- Reads private data · 7
- Reads text others write · 28
- Can send data out · 0
- 1 finding
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
11 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the NodePing MCP by usefulapi can do
The NodePing MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 28 tools. It can delete or cancel things (10 tools: nodeping_update_check, nodeping_mute_check, nodeping_disable_check, nodeping_create_adhoc_maintenance and 6 more) and create or change data (1 tool: nodeping_get_probe_info). 17 tools only read.
7 tools read private data (nodeping_get_check_results, nodeping_get_check_events, nodeping_list_contacts and 4 more); 28 tools bring in text other people can write (nodeping_get_account, nodeping_list_checks, nodeping_get_check and 25 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Last scanned Oct 25, 2026, version 1.27.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
28 tools
Deletes or cancels 10Claude Code: deny
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).Reads text others writeNo findings
Why it is in this group
- The name "nodeping_create_adhoc_maintenance" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Create ad-hoc maintenance
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
nodeping_create_contact_groupWRITE: create a contact group from existing contact address ids.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_create_contact_group" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE: create a contact group from existing contact address ids. POST /contactgroups.
Annotations the server declares
- title: Create contact group
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
nodeping_delete_contact_groupWRITE (destructive): delete a contact group.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_delete_contact_group" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE (destructive): delete a contact group. Checks that notify the group lose that notification target. DELETE /contactgroups/{id}.
Annotations the server declares
- title: Delete contact group
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
nodeping_delete_maintenanceWRITE (destructive): remove a maintenance entry.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_delete_maintenance" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE (destructive): remove a maintenance entry. DELETE /maintenance/{id}.
Annotations the server declares
- title: Delete maintenance entry
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
nodeping_delete_scheduleWRITE (destructive): delete a notification schedule by name.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_delete_schedule" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE (destructive): delete a notification schedule by name. DELETE /schedules/{name}.
Annotations the server declares
- title: Delete notification schedule
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
nodeping_disable_checkWRITE: stop a check from running (enabled=false); its history is kept.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_disable_check" says "disable": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Disable check
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
nodeping_mute_checkWRITE: mute a check's notifications (the check keeps running and recording) until a time or indefinitely, or unmute it.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Mute or unmute check
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
nodeping_put_scheduleWRITE: create or update a notification schedule.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_put_schedule" says "put": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Create or update notification schedule
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
nodeping_update_checkWRITE: change a check's label, description, tags, target, timeout (threshold seconds) or re-checks before alert (sens).Reads text others writeNo findings
Why it is in this group
- The name "nodeping_update_check" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Update check settings
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
nodeping_update_contact_groupWRITE: rename a contact group and/or replace its member list (send the FULL list; omitted members are removed).Reads text others writeNo findings
Why it is in this group
- The name "nodeping_update_contact_group" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE: rename a contact group and/or replace its member list (send the FULL list; omitted members are removed). PUT /contactgroups/{id}.
Annotations the server declares
- title: Update contact group
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Changes things 1Claude Code: ask
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.Reads text others write1 finding
Why it is in this group
- The name "nodeping_get_probe_info" says "get": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "nodeping_get_probe_info" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "nodeping_get_probe_info" says "get": a word for reading.
Description, as the server wrote it 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}].
Annotations the server declares
- title: Get probe locations
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
Only reads 17Show 17 read-only tools
nodeping_get_accountThe NodePing account the token belongs to (name, status, timezone, next billing date, default probe locations), or a SubAccount with customer_id.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_get_account" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The NodePing account the token belongs to (name, status, timezone, next billing date, default probe locations), or a SubAccount with customer_id. GET /accounts.
Annotations the server declares
- title: Get account
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_get_checkOne check by id with its full (scrubbed) configuration.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_get_check" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it One check by id with its full (scrubbed) configuration. Optionally include its latest result and uptime. GET /checks/{id}.
Annotations the server declares
- title: Get check
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_get_check_eventsDown and disabled events of a check (start, end, message, open) newest first: an incident history.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "nodeping_get_check_events" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "message": it reads messages.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get check events
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "nodeping_get_check_results" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "message": it reads messages.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get check results
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_get_check_summaryHourly summary of a check's results: count, min, max and average run time per UTC hour.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_get_check_summary" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Hourly summary of a check's results: count, min, max and average run time per UTC hour. GET /results/summary/{id}.
Annotations the server declares
- title: Get check hourly summary
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_get_check_uptimeUptime percentage of a check per day or month (enabled and down milliseconds plus uptime %), with a total.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_get_check_uptime" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Uptime percentage of a check per day or month (enabled and down milliseconds plus uptime %), with a total. GET /results/uptime/{id}.
Annotations the server declares
- title: Get check uptime
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_get_contactOne contact by id with its addresses (secret-like addresses masked).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "nodeping_get_contact" says "get": a word for reading.
What it can reach
- private-dataThe name "nodeping_get_contact" says "get" and "contact": it reads contacts.
- private-dataThe description's first sentence says "contact": it reads contacts.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it One contact by id with its addresses (secret-like addresses masked). GET /contacts?id={id}.
Annotations the server declares
- title: Get contact
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_get_current_eventsEverything that is down or disabled right now across the account (type, label, since when).Reads text others writeNo findings
Why it is in this group
- The name "nodeping_get_current_events" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Everything that is down or disabled right now across the account (type, label, since when). The quickest 'what is broken' view. GET /results/current.
Annotations the server declares
- title: Get current events
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_get_maintenanceOne maintenance entry by id.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_get_maintenance" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it One maintenance entry by id. GET /maintenance/{id}.
Annotations the server declares
- title: Get maintenance window
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_get_scheduleOne notification schedule by name (for example Days or All) with its seven weekday entries.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_get_schedule" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it One notification schedule by name (for example Days or All) with its seven weekday entries. GET /schedules/{name}.
Annotations the server declares
- title: Get notification schedule
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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).Reads text others writeNo findings
Why it is in this group
- The name "nodeping_list_checks" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: List checks
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_list_contact_groupsContact groups (name and member address ids), keyed by group id.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "nodeping_list_contact_groups" says "list": a word for reading.
What it can reach
- private-dataThe name "nodeping_list_contact_groups" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "contact": it reads contacts.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Contact groups (name and member address ids), keyed by group id. GET /contactgroups.
Annotations the server declares
- title: List contact groups
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_list_contactsAll notification contacts with their addresses (email, SMS, webhook, Slack, ...).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "nodeping_list_contacts" says "list": a word for reading.
What it can reach
- private-dataThe name "nodeping_list_contacts" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "contact": it reads contacts.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List contacts
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_list_maintenanceScheduled and ad-hoc maintenance entries (checks they disable, cron, duration, next run, last runs).Reads text others writeNo findings
Why it is in this group
- The name "nodeping_list_maintenance" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Scheduled and ad-hoc maintenance entries (checks they disable, cron, duration, next run, last runs). GET /maintenance.
Annotations the server declares
- title: List maintenance windows
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_list_notification_profilesNotification profiles: named sets of contacts/groups with delay and schedule, reusable across checks.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "nodeping_list_notification_profiles" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Notification profiles: named sets of contacts/groups with delay and schedule, reusable across checks. GET /notificationprofiles.
Annotations the server declares
- title: List notification profiles
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_list_notificationsThe alert notifications NodePing sent (who, when, what), for one check or for the whole account, newest first.Reads text others writeNo findings
Why it is in this group
- The name "nodeping_list_notifications" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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}].
Annotations the server declares
- title: List notifications sent
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
nodeping_list_schedulesNotification schedules (per-weekday time windows a contact is alerted in).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "nodeping_list_schedules" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Notification schedules (per-weekday time windows a contact is alerted in). GET /schedules.
Annotations the server declares
- title: List notification schedules
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data7
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write28
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- nodeping_create_adhoc_maintenance
- nodeping_create_contact_group
- nodeping_delete_contact_group
- nodeping_delete_maintenance
- nodeping_delete_schedule
- nodeping_disable_check
- nodeping_get_account
- nodeping_get_check
- nodeping_get_check_events
- nodeping_get_check_results
- nodeping_get_check_summary
- nodeping_get_check_uptime
- and 16 more
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 11 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://nodeping.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://nodeping.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
The server marks "nodeping_get_probe_info" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "nodeping_get_probe_info" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 11 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://nodeping.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://nodeping.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.27.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http nodeping https://nodeping.usefulapi.io/mcpclaude mcp add --transport http nodeping https://nodeping.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__nodeping__nodeping_get_account",
"mcp__nodeping__nodeping_list_checks",
"mcp__nodeping__nodeping_get_check",
"mcp__nodeping__nodeping_get_check_results",
"mcp__nodeping__nodeping_get_check_uptime",
"mcp__nodeping__nodeping_get_check_events",
"mcp__nodeping__nodeping_get_current_events",
"mcp__nodeping__nodeping_get_check_summary",
"mcp__nodeping__nodeping_list_notifications",
"mcp__nodeping__nodeping_list_contacts",
"mcp__nodeping__nodeping_get_contact",
"mcp__nodeping__nodeping_list_contact_groups",
"mcp__nodeping__nodeping_list_schedules",
"mcp__nodeping__nodeping_get_schedule",
"mcp__nodeping__nodeping_list_notification_profiles",
"mcp__nodeping__nodeping_list_maintenance",
"mcp__nodeping__nodeping_get_maintenance"
],
"ask": [
"mcp__nodeping__nodeping_get_probe_info"
],
"deny": [
"mcp__nodeping__nodeping_update_check",
"mcp__nodeping__nodeping_mute_check",
"mcp__nodeping__nodeping_disable_check",
"mcp__nodeping__nodeping_create_adhoc_maintenance",
"mcp__nodeping__nodeping_delete_maintenance",
"mcp__nodeping__nodeping_create_contact_group",
"mcp__nodeping__nodeping_update_contact_group",
"mcp__nodeping__nodeping_delete_contact_group",
"mcp__nodeping__nodeping_put_schedule",
"mcp__nodeping__nodeping_delete_schedule"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nodeping. Review it before you use it.
Capability tags behind 28 rules
- mcp__nodeping__nodeping_get_account untrusted-input
- mcp__nodeping__nodeping_list_checks untrusted-input
- mcp__nodeping__nodeping_get_check untrusted-input
- mcp__nodeping__nodeping_get_check_results private-data, untrusted-input
- mcp__nodeping__nodeping_get_check_uptime untrusted-input
- mcp__nodeping__nodeping_get_check_events private-data, untrusted-input
- mcp__nodeping__nodeping_get_current_events untrusted-input
- mcp__nodeping__nodeping_get_check_summary untrusted-input
- mcp__nodeping__nodeping_list_notifications untrusted-input
- mcp__nodeping__nodeping_list_contacts private-data, untrusted-input
- mcp__nodeping__nodeping_get_contact private-data, untrusted-input
- mcp__nodeping__nodeping_list_contact_groups private-data, untrusted-input
- mcp__nodeping__nodeping_list_schedules private-data, untrusted-input
- mcp__nodeping__nodeping_get_schedule untrusted-input
- mcp__nodeping__nodeping_list_notification_profiles private-data, untrusted-input
- mcp__nodeping__nodeping_list_maintenance untrusted-input
- mcp__nodeping__nodeping_get_maintenance untrusted-input
- mcp__nodeping__nodeping_get_probe_info untrusted-input
- mcp__nodeping__nodeping_update_check untrusted-input
- mcp__nodeping__nodeping_mute_check untrusted-input
- mcp__nodeping__nodeping_disable_check untrusted-input
- mcp__nodeping__nodeping_create_adhoc_maintenance untrusted-input
- mcp__nodeping__nodeping_delete_maintenance untrusted-input
- mcp__nodeping__nodeping_create_contact_group untrusted-input
- mcp__nodeping__nodeping_update_contact_group untrusted-input
- mcp__nodeping__nodeping_delete_contact_group untrusted-input
- mcp__nodeping__nodeping_put_schedule untrusted-input
- mcp__nodeping__nodeping_delete_schedule untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/nodeping/verify?hash=470d6146deab866e87d2049431b97b07bdb87a61b7d825a4963c7c301066e35f" | jq -e '.changed == false'Pinned hash 470d6146deab, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/nodeping/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/nodeping)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
NodePing MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the NodePing MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 28 tools, 11 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the NodePing MCP by usefulapi delete data?
- Yes. 10 tools can delete, cancel or revoke something: nodeping_update_check, nodeping_mute_check, nodeping_disable_check, nodeping_create_adhoc_maintenance, nodeping_delete_maintenance, nodeping_create_contact_group and 4 more.
Can the NodePing MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the NodePing MCP by usefulapi have?
- 28 tools: 10 destructive, 1 write, 17 read. nodeping_update_check, nodeping_mute_check, nodeping_disable_check, nodeping_create_adhoc_maintenance, nodeping_delete_maintenance, nodeping_create_contact_group, nodeping_update_contact_group, nodeping_delete_contact_group and 20 more.
Does the NodePing MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the NodePing MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the NodePing MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.