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 件