MCP MeasureMCP Measure

인덱스 관측됨

statuspal

Read status-page status, services, incidents and metrics; create, update and publish incidents.

사용해야 할까요

품질 및 안전성

A
설명 품질
100%
스키마 완전성
95%
이름 품질
78%
오염 위험
100%
권한 일치
100%
프로토콜 준수
100%

발견 사항 (1)

  • LOWTool 'statuspal_create_incident_update' name length outside 3-30 rangestatuspal_create_incident_update에서

도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.

컨텍스트 비용

~1,972토큰 (도구 정의)
~1.5 KB일반적인 응답 크기
중간 정도의 주의 영향 (128k 컨텍스트의 1.54%)

이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.

설치

원클릭 설치

`claude_desktop_config.json` 파일에 다음을 추가하세요:

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

원격 엔드포인트

https://statuspal.usefulapi.io/mcpstreamable-http

할 수 있는 일

도구 목록

도구 (11)

🟢 읽기 전용🟡 쓰기🔴 삭제⚪ 알 수 없음
🟢statuspal_get_summary(subdomain)

Get the FULL status-page summary — status_page, services[], incidents[], maintenances[], upcoming_maintenances[], info_notices[], and current_status_type. StatusPal: GET /status_pages/{subdomain}/summary.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢statuspal_get_status(subdomain)

Get the current overall status of the status page (the aggregate status type). StatusPal: GET /status_pages/{subdomain}/status.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢statuspal_list_services(subdomain)

List the services on a status page — each with {id, name, current_incident_type, children[]}. StatusPal: GET /status_pages/{subdomain}/services.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢statuspal_get_service_status(subdomain, service_id)

Get the current status of a single service by its id. StatusPal: GET /status_pages/{subdomain}/services/{service_id}/status.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    },
    "service_id": {
      "type": "number",
      "description": "The service id."
    }
  },
  "required": [
    "service_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢statuspal_list_incidents(subdomain, limit, type, before, after)

List incidents for a status page. Returns {incidents[], links:{next,prev}, meta:{total_count}}. Use `before`/`after` cursors to paginate and `type` to filter. StatusPal: GET /status_pages/{subdomain}/incidents.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    },
    "limit": {
      "description": "Max incidents to return (default 20, max 100).",
      "type": "number"
    },
    "type": {
      "description": "Filter incidents by type.",
      "type": "string"
    },
    "before": {
      "description": "Pagination cursor — return incidents before this cursor.",
      "type": "string"
    },
    "after": {
      "description": "Pagination cursor — return incidents after this cursor.",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢statuspal_get_incident(subdomain, incident_id)

Get a single incident by its id. StatusPal: GET /status_pages/{subdomain}/incidents/{incident_id}.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    },
    "incident_id": {
      "type": "number",
      "description": "The incident id."
    }
  },
  "required": [
    "incident_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢statuspal_list_metrics(subdomain, limit, before, after)

List the metrics configured on a status page. Use `before`/`after` cursors to paginate. StatusPal: GET /status_pages/{subdomain}/metrics.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    },
    "limit": {
      "description": "Max metrics to return.",
      "type": "number"
    },
    "before": {
      "description": "Pagination cursor — return metrics before this cursor.",
      "type": "string"
    },
    "after": {
      "description": "Pagination cursor — return metrics after this cursor.",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴statuspal_create_incident(subdomain, title, type, service_ids, starts_at, ...)

PUBLISHES a new incident to the LIVE public status page (and, with notify=true, emails/notifies subscribers). type="major" or "minor" is an outage incident; type="scheduled" creates a scheduled maintenance window. StatusPal: POST /status_pages/{subdomain}/incidents.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    },
    "title": {
      "type": "string",
      "description": "Incident title (required)."
    },
    "type": {
      "type": "string",
      "enum": [
        "major",
        "minor",
        "scheduled"
      ],
      "description": "Incident type. \"major\"/\"minor\" = outage severity; \"scheduled\" = a maintenance window."
    },
    "service_ids": {
      "type": "array",
      "items": {
        "type": "number"
      },
      "description": "Ids of the affected services (required)."
    },
    "starts_at": {
      "description": "ISO8601 start time (optional; required for scheduled maintenance).",
      "type": "string"
    },
    "ends_at": {
      "description": "ISO8601 end time (optional).",
      "type": "string"
    },
    "notify": {
      "description": "Whether to notify/email subscribers.",
      "type": "boolean"
    },
    "updates": {
      "description": "Optional initial updates to post with the incident.",
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "description": "Update type — common values: \"investigating\", \"identified\", \"monitoring\", \"resolved\", \"issue\"."
          },
          "description": {
            "type": "string",
            "description": "The update message shown on the status page (required)."
          },
          "posted_at": {
            "description": "ISO8601 timestamp for the update (optional; defaults to now).",
            "type": "string"
          },
          "notify": {
            "description": "Whether to notify/email subscribers about this update.",
            "type": "boolean"
          }
        },
        "required": [
          "type",
          "description"
        ]
      }
    }
  },
  "required": [
    "title",
    "type",
    "service_ids"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴statuspal_update_incident(subdomain, incident_id, title, type, service_ids, ...)

UPDATES an existing incident on the LIVE public status page (title/type/services/timing). StatusPal: PUT /status_pages/{subdomain}/incidents/{incident_id}.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    },
    "incident_id": {
      "type": "number",
      "description": "The incident id to update."
    },
    "title": {
      "description": "New incident title.",
      "type": "string"
    },
    "type": {
      "description": "New incident type (\"major\"/\"minor\"/\"scheduled\").",
      "type": "string",
      "enum": [
        "major",
        "minor",
        "scheduled"
      ]
    },
    "service_ids": {
      "description": "New set of affected service ids.",
      "type": "array",
      "items": {
        "type": "number"
      }
    },
    "starts_at": {
      "description": "New ISO8601 start time.",
      "type": "string"
    },
    "ends_at": {
      "description": "New ISO8601 end time.",
      "type": "string"
    },
    "notify": {
      "description": "Whether to notify/email subscribers about the change.",
      "type": "boolean"
    }
  },
  "required": [
    "incident_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴statuspal_create_incident_update(subdomain, incident_id, type, description, posted_at, ...)

POSTS an update (e.g. investigating → identified → monitoring → resolved) to an existing incident on the LIVE public status page (and, with notify=true, notifies subscribers). StatusPal: POST /status_pages/{subdomain}/incidents/{incident_id}/updates.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    },
    "incident_id": {
      "type": "number",
      "description": "The incident id to post an update to."
    },
    "type": {
      "type": "string",
      "description": "Update type — common values: \"investigating\", \"identified\", \"monitoring\", \"resolved\", \"issue\"."
    },
    "description": {
      "type": "string",
      "description": "The update message shown on the status page (required)."
    },
    "posted_at": {
      "description": "ISO8601 timestamp for the update (optional; defaults to now).",
      "type": "string"
    },
    "notify": {
      "description": "Whether to notify/email subscribers about this update.",
      "type": "boolean"
    }
  },
  "required": [
    "incident_id",
    "type",
    "description"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴statuspal_delete_incident(subdomain, incident_id)

DELETES an incident from the LIVE public status page — this permanently removes it. StatusPal: DELETE /status_pages/{subdomain}/incidents/{incident_id}.

입력 스키마

{
  "type": "object",
  "properties": {
    "subdomain": {
      "description": "Status page subdomain (overrides STATUSPAL_SUBDOMAIN).",
      "type": "string"
    },
    "incident_id": {
      "type": "number",
      "description": "The incident id to delete."
    }
  },
  "required": [
    "incident_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

권장 프롬프트

retrieve_data
Get details about [item] from statuspal
예상 도구: statuspal_get_summary
fetch_info
Fetch [information type] using statuspal
예상 도구: statuspal_get_summary
list_items
List all [items] available in statuspal
예상 도구: statuspal_list_services
browse_collection
Show me the [collection] from statuspal
예상 도구: statuspal_list_services
explore_workflow
List available [items], then get details for each one using statuspal
예상 도구: statuspal_list_servicesstatuspal_get_summary

커뮤니티

이 서버 평가하기

증거

최근 관측

검증됨버전이 기록되지 않음도구 11개
검증됨버전이 기록되지 않음도구 11개