statuspal
Server Details
Read status-page status, services, incidents and metrics; create, update and publish incidents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
11 toolsstatuspal_create_incidentCreate incidentDestructiveInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Incident type. "major"/"minor" = outage severity; "scheduled" = a maintenance window. | |
| title | Yes | Incident title (required). | |
| notify | No | Whether to notify/email subscribers. | |
| ends_at | No | ISO8601 end time (optional). | |
| updates | No | Optional initial updates to post with the incident. | |
| starts_at | No | ISO8601 start time (optional; required for scheduled maintenance). | |
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| service_ids | Yes | Ids of the affected services (required). |
statuspal_create_incident_updatePost incident updateDestructiveInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Update type — common values: "investigating", "identified", "monitoring", "resolved", "issue". | |
| notify | No | Whether to notify/email subscribers about this update. | |
| posted_at | No | ISO8601 timestamp for the update (optional; defaults to now). | |
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| description | Yes | The update message shown on the status page (required). | |
| incident_id | Yes | The incident id to post an update to. |
statuspal_delete_incidentDelete incidentDestructiveInspect
DELETES an incident from the LIVE public status page — this permanently removes it. StatusPal: DELETE /status_pages/{subdomain}/incidents/{incident_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| incident_id | Yes | The incident id to delete. |
statuspal_get_incidentGet incidentRead-onlyInspect
Get a single incident by its id. StatusPal: GET /status_pages/{subdomain}/incidents/{incident_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| incident_id | Yes | The incident id. |
statuspal_get_service_statusGet service statusRead-onlyInspect
Get the current status of a single service by its id. StatusPal: GET /status_pages/{subdomain}/services/{service_id}/status.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| service_id | Yes | The service id. |
statuspal_get_statusGet overall statusRead-onlyInspect
Get the current overall status of the status page (the aggregate status type). StatusPal: GET /status_pages/{subdomain}/status.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
statuspal_get_summaryGet status page summaryRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
statuspal_list_incidentsList incidentsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter incidents by type. | |
| after | No | Pagination cursor — return incidents after this cursor. | |
| limit | No | Max incidents to return (default 20, max 100). | |
| before | No | Pagination cursor — return incidents before this cursor. | |
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
statuspal_list_metricsList metricsRead-onlyInspect
List the metrics configured on a status page. Use before/after cursors to paginate. StatusPal: GET /status_pages/{subdomain}/metrics.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Pagination cursor — return metrics after this cursor. | |
| limit | No | Max metrics to return. | |
| before | No | Pagination cursor — return metrics before this cursor. | |
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
statuspal_list_servicesList servicesRead-onlyInspect
List the services on a status page — each with {id, name, current_incident_type, children[]}. StatusPal: GET /status_pages/{subdomain}/services.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
statuspal_update_incidentUpdate incidentDestructiveInspect
UPDATES an existing incident on the LIVE public status page (title/type/services/timing). StatusPal: PUT /status_pages/{subdomain}/incidents/{incident_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | New incident type ("major"/"minor"/"scheduled"). | |
| title | No | New incident title. | |
| notify | No | Whether to notify/email subscribers about the change. | |
| ends_at | No | New ISO8601 end time. | |
| starts_at | No | New ISO8601 start time. | |
| subdomain | No | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). | |
| incident_id | Yes | The incident id to update. | |
| service_ids | No | New set of affected service ids. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!