← All launches
NodePing MCP by usefulapi logo
0 Report

NodePing MCP by usefulapi

by FastDrop

MCP Verified 2 hours ago Registry import free

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

Read NodePing checks, uptime, results and events; mute checks, manage maintenance and schedules. Official MCP Registry: io.usefulapi/nodeping@1.0.0. Remote endpoint: https://nodeping.usefulapi.io/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/nodeping and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 11 Oct 2026. Not supplied by the maker.

  • 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 o

  • 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 86

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

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.

Sign in to claim this listing

Matched on shared tags and the tools their MCP servers actually expose.

Reviews

Sign in to leave a review.

No reviews yet.

Comments

Sign in to join the discussion.

No comments yet - start the discussion.