NodePing MCP by usefulapi

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

https://nodeping.usefulapi.io/mcp

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

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

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

https://nodeping.usefulapi.io/mcp

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• 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 or label text. Compact by default; set detail=true for the full (scrubbed) check

• 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 8601 or RFC 2822; GMT unless a zone is given) to bound it. GET /results/{id}.

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

• nodeping_list_notifications

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

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

• nodeping_get_contact

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

• nodeping_list_contact_groups

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

• nodeping_list_schedules

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

• nodeping_get_schedule

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

• nodeping_list_notification_profiles

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

• nodeping_list_maintenance

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

• nodeping_get_maintenance

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

• nodeping_get_probe_info

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

• nodeping_update_check

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

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

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

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

• nodeping_delete_maintenance

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

• nodeping_create_contact_group

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

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

• nodeping_delete_contact_group

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

• nodeping_put_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 f

• nodeping_delete_schedule

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

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

• ✓ 통과

  제작자와 저장소 일치

  레지스트리 이름이 도메인 usefulapi.io 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  18ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 28개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

기타 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 32403개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 32403개 중 97%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 32403개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

{