# NodePing MCP by usefulapi (remote · nodeping.usefulapi.io)

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

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- remote · `nodeping.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-nodeping/nodeping.md), [page](https://verifymcp.io/servers/io-usefulapi-nodeping/nodeping)

## Channel facts

- Endpoint: `https://nodeping.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3263 tokens (~116/item across 28 items; 28 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the NodePing MCP by usefulapi server?

NodePing MCP by usefulapi is a hosted endpoint at https://nodeping.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.io-usefulapi-nodeping]
url = "https://nodeping.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-nodeping": {
      "type": "remote",
      "url": "https://nodeping.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-nodeping --url 'https://nodeping.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-nodeping:
    url: "https://nodeping.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-nodeping": {
      "Transport": "http",
      "Url": "https://nodeping.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-nodeping -t streamable-http -u 'https://nodeping.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-nodeping": {
      "type": "http",
      "url": "https://nodeping.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 62, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (28)

### `nodeping_get_account` (~68 tokens)

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.

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.

### `nodeping_list_checks` (~182 tokens)

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 /checks.

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `detail` (boolean): Return full check objects (parameters, notifications) instead of the compact view.
- `label_contains` (string): Only checks whose label contains this text (case-insensitive).
- `status` (string): Only passing, failing or disabled checks.
- `type` (string): Only this check type, e.g. HTTP, PING, SSL, DNS.

### `nodeping_get_check` (~126 tokens)

Get check

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

Input parameters:

- `check_id` (string, required): NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks).
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `last_result` (boolean): Include the check's most recent result.
- `uptime` (boolean): Include uptime figures.

### `nodeping_get_check_results` (~224 tokens)

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}.

Input parameters:

- `check_id` (string, required): NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks).
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `end` (string): End of the range (cannot be combined with span).
- `limit` (integer): Number of results (default 50, max 5000).
- `span` (integer): Hours of history to return (narrower than `limit` wins).
- `start` (string): Start of the range.

### `nodeping_get_check_uptime` (~173 tokens)

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}.

Input parameters:

- `check_id` (string, required): NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks).
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `end` (string): End date, exclusive (default now).
- `interval` (string): Bucket size (default months).
- `offset` (integer): UTC offset in hours for the day/month boundaries.
- `start` (string): Start date, e.g. 2026-09-01 (default: earliest data).

### `nodeping_get_check_events` (~141 tokens)

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}.

Input parameters:

- `check_id` (string, required): NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks).
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `end` (string): End of the range.
- `limit` (integer)
- `start` (string): Start of the range.

### `nodeping_get_current_events` (~67 tokens)

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.

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.

### `nodeping_get_check_summary` (~103 tokens)

Get check hourly summary

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

Input parameters:

- `check_id` (string, required): NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks).
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.

### `nodeping_list_notifications` (~173 tokens)

List notifications sent

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}].

Input parameters:

- `check_id` (string): NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks).
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `include_subaccounts` (boolean): Also include notifications sent for SubAccounts.
- `limit` (integer): Number of records (default 300, max 5000).
- `span` (integer): Hours of history to return (narrower than `limit` wins).

### `nodeping_list_contacts` (~78 tokens)

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.

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.

### `nodeping_get_contact` (~81 tokens)

Get contact

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

Input parameters:

- `contact_id` (string, required): Contact id, e.g. 201205050153W2Q4C-BKPGH.
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.

### `nodeping_list_contact_groups` (~53 tokens)

List contact groups

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

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.

### `nodeping_list_schedules` (~53 tokens)

List notification schedules

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

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.

### `nodeping_get_schedule` (~67 tokens)

Get notification schedule

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

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `name` (string, required): Schedule name.

### `nodeping_list_notification_profiles` (~56 tokens)

List notification profiles

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

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.

### `nodeping_list_maintenance` (~60 tokens)

List maintenance windows

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

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.

### `nodeping_get_maintenance` (~63 tokens)

Get maintenance window

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

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `maintenance_id` (string, required): Maintenance id, e.g. NZT101.

### `nodeping_get_probe_info` (~96 tokens)

Get probe locations

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}].

Input parameters:

- `code` (string): One probe or region code; omit to list all.
- `kind` (string, required): probe = individual probe servers, location = regions.

### `nodeping_update_check` (~204 tokens)

Update check settings

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}.

Input parameters:

- `check_id` (string, required): NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks).
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `description` (string): Up to 1000 characters.
- `label` (string)
- `sens` (integer): Re-checks before the state changes.
- `tags` (array): Replaces the check's tags.
- `target` (string): New target (HTTP-family checks need an http:// or https:// URL).
- `threshold` (integer): Timeout in seconds.

### `nodeping_mute_check` (~174 tokens)

Mute or unmute 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}.

Input parameters:

- `check_id` (string, required): NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks).
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `mute` (boolean, required): true = mute, false = unmute.
- `mute_until_ms` (integer): Unmute automatically at this time (ms since epoch, must be in the future). Only with mute=true.

### `nodeping_disable_check` (~113 tokens)

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}.

Input parameters:

- `check_id` (string, required): NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks).
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.

### `nodeping_create_adhoc_maintenance` (~138 tokens)

Create ad-hoc 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.

Input parameters:

- `check_ids` (array, required)
- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `duration_minutes` (integer, required): How long the checks stay disabled, in minutes (max 7 days).
- `name` (string, required)
- `start_now` (boolean): Start immediately (default false: created but not started).

### `nodeping_delete_maintenance` (~60 tokens)

Delete maintenance entry

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

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `maintenance_id` (string, required): Maintenance id.

### `nodeping_create_contact_group` (~78 tokens)

Create contact group

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

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `members` (array, required): Contact ADDRESS ids (from nodeping_list_contacts), not contact ids.
- `name` (string, required)

### `nodeping_update_contact_group` (~122 tokens)

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}.

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `group_id` (string, required): Contact group id, e.g. 201205050153W2Q4C-G-3QJWG.
- `members` (array): Contact ADDRESS ids (from nodeping_list_contacts), not contact ids.
- `name` (string)

### `nodeping_delete_contact_group` (~72 tokens)

Delete contact group

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

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `group_id` (string, required): Contact group id.

### `nodeping_put_schedule` (~171 tokens)

Create or update notification 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}.

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `friday` (object)
- `monday` (object)
- `name` (string, required): Schedule name.
- `saturday` (object)
- `sunday` (object)
- `thursday` (object)
- `tuesday` (object)
- `wednesday` (object)

### `nodeping_delete_schedule` (~61 tokens)

Delete notification schedule

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

Input parameters:

- `customer_id` (string): SubAccount customer id (MSP accounts). Omit for your own account.
- `name` (string, required): Schedule name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-nodeping/nodeping#diagnostics

## Score history

- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 62
- 2026-10-12: 60

## Common questions

### What is the NodePing MCP by usefulapi server?

NodePing MCP by usefulapi is listed in the public MCP registry as io.usefulapi/nodeping. Read NodePing checks, uptime, results and events; mute checks, manage maintenance and schedules. This page covers its hosted endpoint (https://nodeping.usefulapi.io/mcp).

### Is the NodePing MCP by usefulapi server safe to use?

NodePing MCP by usefulapi scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the NodePing MCP by usefulapi server expose?

NodePing MCP by usefulapi exposes 28 tools: nodeping_get_account, nodeping_list_checks, nodeping_get_check, nodeping_get_check_results, nodeping_get_check_uptime, and 23 more. Their descriptions and schemas cost roughly 3,057 tokens of context every time the server is loaded.

### Does the NodePing MCP by usefulapi server require authentication?

Yes. NodePing MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the NodePing MCP by usefulapi server still maintained?

NodePing MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://nodeping.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/nodeping/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-nodeping/nodeping.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-nodeping/nodeping.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-nodeping/nodeping