Home / MCP registry index / io.usefulapi/nodeping

NodePing MCP by usefulapi

io.usefulapi/nodeping in the official MCP registry. Endpoint https://nodeping.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read NodePing checks, uptime, results and events; mute checks, manage maintenance and schedules.

We read its 28 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

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

VS Code

code --add-mcp '{"name":"nodeping","type":"http","url":"https://nodeping.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

nodeping_get_account nodeping_list_checks nodeping_get_check nodeping_get_check_results nodeping_get_check_uptime nodeping_get_check_events nodeping_get_current_events nodeping_get_check_summary nodeping_list_notifications nodeping_list_contacts nodeping_get_contact nodeping_list_contact_groups nodeping_list_schedules nodeping_get_schedule nodeping_list_notification_profiles nodeping_list_maintenance nodeping_get_maintenance nodeping_get_probe_info 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 nodeping_put_schedule nodeping_delete_schedule

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): f3c97a9a90bf6145. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-nodeping/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-nodeping)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.