instatus
Server Details
Manage status pages: components, incidents and maintenances; set live component status.
- 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
14 toolsinstatus_create_incidentCreate incidentDestructiveInspect
CREATES a new incident — this MODIFIES live status-page data and can notify subscribers. Provide name (required); optionally set the initial message, affected components, per-component impact via statuses, status, started, notify, and shouldPublish. Instatus: POST /v1/{page_id}/incidents. Returns the created incident.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Incident title (required). | |
| notify | No | Whether to notify subscribers about this update. | |
| status | No | Incident status. | |
| message | No | Incident update message (Markdown supported). | |
| page_id | Yes | The status page's id. | |
| started | No | ISO 8601 timestamp for when the incident started. | |
| statuses | No | Per-component impact — set each listed component's status for this event. | |
| components | No | Component ids affected by this incident. | |
| shouldPublish | No | Whether the incident should be published to the status page. |
instatus_create_maintenanceCreate maintenanceDestructiveInspect
CREATES a new scheduled maintenance — this MODIFIES live status-page data and can notify subscribers. Provide name (required); optionally set message, affected components, per-component impact via statuses, status, start/end, duration, and notify. Instatus: POST /v1/{page_id}/maintenances. Returns the created maintenance.
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | ISO 8601 timestamp for when the maintenance ends. | |
| name | Yes | Maintenance title (required). | |
| start | No | ISO 8601 timestamp for when the maintenance starts. | |
| notify | No | Whether to notify subscribers about this update. | |
| status | No | Maintenance status. | |
| message | No | Maintenance update message (Markdown supported). | |
| page_id | Yes | The status page's id. | |
| duration | No | Maintenance duration in minutes. | |
| statuses | No | Per-component impact — set each listed component's status for this event. | |
| components | No | Component ids affected by this maintenance. |
instatus_delete_incidentDelete incidentDestructiveInspect
PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| page_id | Yes | The status page's id. | |
| incident_id | Yes | The incident's id to delete. |
instatus_delete_maintenanceDelete maintenanceDestructiveInspect
PERMANENTLY DELETES a scheduled maintenance by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/maintenances/{maintenance_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| page_id | Yes | The status page's id. | |
| maintenance_id | Yes | The maintenance's id to delete. |
instatus_get_componentGet componentRead-onlyInspect
Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| page_id | Yes | The status page's id. | |
| component_id | Yes | The component's id. |
instatus_get_incidentGet incidentRead-onlyInspect
Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| page_id | Yes | The status page's id. | |
| incident_id | Yes | The incident's id. |
instatus_get_maintenanceGet maintenanceRead-onlyInspect
Get a single scheduled maintenance by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/maintenances/{maintenance_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| page_id | Yes | The status page's id. | |
| maintenance_id | Yes | The maintenance's id. |
instatus_list_componentsList componentsRead-onlyInspect
List a status page's components — id, name, description, status, order, showUptime, grouped, archived. The component ids are what you set impact on. Instatus: GET /v2/{page_id}/components.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to fetch (default 1). | |
| page_id | Yes | The status page's id (from list_pages). | |
| per_page | No | Items per page (default 50, max 100). |
instatus_list_incidentsList incidentsRead-onlyInspect
List a status page's incidents, most recent first — optionally filtered by status. Each incident: id, name, status, impact, affected components, updates, timestamps. Instatus: GET /v1/{page_id}/incidents.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to fetch (default 1). | |
| status | No | Filter to incidents with this status (INVESTIGATING, IDENTIFIED, MONITORING, RESOLVED). | |
| page_id | Yes | The status page's id. | |
| per_page | No | Items per page (default 50, max 100). |
instatus_list_maintenancesList maintenancesRead-onlyInspect
List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to fetch (default 1). | |
| page_id | Yes | The status page's id. | |
| per_page | No | Items per page (default 50, max 100). |
instatus_list_pagesList pagesRead-onlyInspect
List all status pages on the account — each page's id, subdomain, name, status, url, custom domain, and timestamps. The page id is what every other tool takes as page_id. Instatus: GET /v2/pages.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to fetch (default 1). | |
| per_page | No | Items per page (default 50, max 100). |
instatus_update_componentUpdate componentDestructiveInspect
UPDATES a component by id — this MODIFIES live status-page data. The key way to set a component's operational status (OPERATIONAL, UNDERMAINTENANCE, DEGRADEDPERFORMANCE, PARTIALOUTAGE, MAJOROUTAGE). Send only the fields you want to change. Instatus: PUT /v2/{page_id}/components/{component_id}. Returns the updated component.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Component name. | |
| order | No | Display order of the component on the page. | |
| status | No | Operational status of the component. | |
| grouped | No | Whether the component is displayed within a group. | |
| page_id | Yes | The status page's id. | |
| archived | No | Whether the component is archived (hidden). | |
| showUptime | No | Whether to show the uptime graph for this component. | |
| description | No | Free-form component description. | |
| component_id | Yes | The component's id to update. |
instatus_update_incidentUpdate incidentDestructiveInspect
UPDATES an existing incident by id — this MODIFIES live status-page data and can notify subscribers (e.g. move it to MONITORING or RESOLVED). Send only the fields you want to change. Instatus: PUT /v1/{page_id}/incidents/{incident_id}. Returns the updated incident.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Incident title. | |
| notify | No | Whether to notify subscribers about this update. | |
| status | No | Incident status. | |
| message | No | Incident update message (Markdown supported). | |
| page_id | Yes | The status page's id. | |
| started | No | ISO 8601 timestamp for when the incident started. | |
| statuses | No | Per-component impact — set each listed component's status for this event. | |
| components | No | Component ids affected by this incident. | |
| incident_id | Yes | The incident's id to update. | |
| shouldPublish | No | Whether the incident should be published to the status page. |
instatus_update_maintenanceUpdate maintenanceDestructiveInspect
UPDATES an existing scheduled maintenance by id — this MODIFIES live status-page data and can notify subscribers. Send only the fields you want to change. Instatus: PUT /v1/{page_id}/maintenances/{maintenance_id}. Returns the updated maintenance.
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | ISO 8601 timestamp for when the maintenance ends. | |
| name | No | Maintenance title. | |
| start | No | ISO 8601 timestamp for when the maintenance starts. | |
| notify | No | Whether to notify subscribers about this update. | |
| status | No | Maintenance status. | |
| message | No | Maintenance update message (Markdown supported). | |
| page_id | Yes | The status page's id. | |
| duration | No | Maintenance duration in minutes. | |
| statuses | No | Per-component impact — set each listed component's status for this event. | |
| components | No | Component ids affected by this maintenance. | |
| maintenance_id | Yes | The maintenance's id to update. |
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!