Model Context Protocol server for Rollbar
NodePing MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read NodePing checks, uptime, results and events; mute checks, manage maintenance and schedules.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nodeping-mcp-by-usefulapi https://nodeping.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# nodeping_get_account, nodeping_list_checks, nodeping_get_check and 25 more
NodePing MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http nodeping-mcp-by-usefulapi https://nodeping.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
28 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The NodePing account the token belongs to (name, status, timezone, next billing date, default probe locations), or a SubAccount with customer_id. GET /accounts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Only passing, failing or disabled checks. |
| type | string | no | Only this check type, e.g. HTTP, PING, SSL, DNS. |
| label_contains | string | no | Only checks whose label contains this text (case-insensitive). |
| detail | boolean | no | Return full check objects (parameters, notifications) instead of the compact view. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
One check by id with its full (scrubbed) configuration. Optionally include its latest result and uptime. GET /checks/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks). |
| last_result | boolean | no | Include the check's most recent result. |
| uptime | boolean | no | Include uptime figures. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks). |
| limit | integer | no | Number of results (default 50, max 5000). |
| span | integer | no | Hours of history to return (narrower than limit wins). |
| start | string | no | Start of the range. |
| end | string | no | End of the range (cannot be combined with span). |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
Uptime percentage of a check per day or month (enabled and down milliseconds plus uptime %), with a total. GET /results/uptime/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks). |
| interval | string | no | Bucket size (default months). |
| start | string | no | Start date, e.g. 2026-09-01 (default: earliest data). |
| end | string | no | End date, exclusive (default now). |
| offset | integer | no | UTC offset in hours for the day/month boundaries. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks). |
| start | string | no | Start of the range. |
| end | string | no | End of the range. |
| limit | integer | no | — |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
Everything that is down or disabled right now across the account (type, label, since when). The quickest 'what is broken' view. GET /results/current.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
Hourly summary of a check's results: count, min, max and average run time per UTC hour. GET /results/summary/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks). |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
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}].
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | no | NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks). |
| limit | integer | no | Number of records (default 300, max 5000). |
| span | integer | no | Hours of history to return (narrower than limit wins). |
| include_subaccounts | boolean | no | Also include notifications sent for SubAccounts. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
One contact by id with its addresses (secret-like addresses masked). GET /contacts?id={id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string | yes | Contact id, e.g. 201205050153W2Q4C-BKPGH. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
Contact groups (name and member address ids), keyed by group id. GET /contactgroups.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
Notification schedules (per-weekday time windows a contact is alerted in). GET /schedules.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
One notification schedule by name (for example Days or All) with its seven weekday entries. GET /schedules/{name}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Schedule name. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
Notification profiles: named sets of contacts/groups with delay and schedule, reusable across checks. GET /notificationprofiles.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
Scheduled and ad-hoc maintenance entries (checks they disable, cron, duration, next run, last runs). GET /maintenance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
One maintenance entry by id. GET /maintenance/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maintenance_id | string | yes | Maintenance id, e.g. NZT101. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
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}].
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | probe = individual probe servers, location = regions. |
| code | string | no | One probe or region code; omit to list all. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks). |
| label | string | no | — |
| description | string | no | Up to 1000 characters. |
| tags | array | no | Replaces the check's tags. |
| target | string | no | New target (HTTP-family checks need an http:// or https:// URL). |
| threshold | integer | no | Timeout in seconds. |
| sens | integer | no | Re-checks before the state changes. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks). |
| mute | boolean | yes | true = mute, false = unmute. |
| mute_until_ms | integer | no | Unmute automatically at this time (ms since epoch, must be in the future). Only with mute=true. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | NodePing check id, e.g. 201205050153W2Q4C-0J2HSIRF (from nodeping_list_checks). |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| duration_minutes | integer | yes | How long the checks stay disabled, in minutes (max 7 days). |
| check_ids | array | yes | — |
| start_now | boolean | no | Start immediately (default false: created but not started). |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
WRITE (destructive): remove a maintenance entry. DELETE /maintenance/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maintenance_id | string | yes | Maintenance id. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
WRITE: create a contact group from existing contact address ids. POST /contactgroups.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| members | array | yes | Contact ADDRESS ids (from nodeping_list_contacts), not contact ids. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
WRITE: rename a contact group and/or replace its member list (send the FULL list; omitted members are removed). PUT /contactgroups/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_id | string | yes | Contact group id, e.g. 201205050153W2Q4C-G-3QJWG. |
| name | string | no | — |
| members | array | no | Contact ADDRESS ids (from nodeping_list_contacts), not contact ids. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
WRITE (destructive): delete a contact group. Checks that notify the group lose that notification target. DELETE /contactgroups/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_id | string | yes | Contact group id. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Schedule name. |
| monday | object | no | — |
| tuesday | object | no | — |
| wednesday | object | no | — |
| thursday | object | no | — |
| friday | object | no | — |
| saturday | object | no | — |
| sunday | object | no | — |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
WRITE (destructive): delete a notification schedule by name. DELETE /schedules/{name}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Schedule name. |
| customer_id | string | no | SubAccount customer id (MSP accounts). Omit for your own account. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install NodePing MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish NodePing MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.