io.usefulapiPublished by usefulapi.ioOfficial publisherv1.36.4Updated Nov 7, 2026
Manage status pages: components, incidents and maintenances; set live component status.
The publisher's own server: Ably MCP by usefulapi
Hosted Instatus server that lets an assistant read and change status pages: components, incidents and scheduled maintenances.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.usefulapi%2Finstatus/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"instatus-by-usefulapi": {
"type": "http",
"url": "https://instatus.usefulapi.io/mcp"
}
}
}Manage Instatus from Claude, Cursor, or any MCP client — manage status pages — components, incidents and scheduled maintenances, and set live status. Hosted, no local install: connect with your Instatus API token.
Live endpoint: https://instatus.usefulapi.io/mcp · Homepage: https://usefulapi.io
https://instatus.usefulapi.io/mcp.claude mcp add --transport http instatus https://instatus.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Instatus credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/instatus/
On first connect you'll paste your Instatus API token (Instatus → Developers → API). It's validated, stored per-user, and scoped to you — no keys in config files.
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with instatus_upgrade (it returns a Stripe Checkout link). Cancel any time with instatus_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running instatus_upgrade before then undoes the cancel. Or write to [email protected].
MIT — see LICENSE. Documentation only; the server is hosted.
Source: servers/instatus/README.md at commit 4046075
List pages
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.
pageper_pageList components
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.
pagepage_idrequiredper_pageGet component
Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.
page_idrequiredcomponent_idrequiredList incidents
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.
pagestatuspage_idrequiredper_pageGet incident
Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.
page_idrequiredincident_idrequiredList maintenances
List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.
pagepage_idrequiredper_pageGet maintenance
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}.
page_idrequiredmaintenance_idrequiredUpdate component
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.
nameorderstatusgroupedpage_idrequiredarchivedshowUptimedescriptioncomponent_idrequiredCreate incident
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.
namerequirednotifystatusmessagepage_idrequiredstartedstatusescomponentsshouldPublishUpdate incident
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.
namenotifystatusmessagepage_idrequiredstartedstatusescomponentsincident_idrequiredshouldPublishDelete incident
PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.
page_idrequiredincident_idrequiredCreate maintenance
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.
endnamerequiredstartnotifystatusmessagepage_idrequireddurationstatusescomponentsUpdate maintenance
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.
endnamestartnotifystatusmessagepage_idrequireddurationstatusescomponentsmaintenance_idrequiredDelete maintenance
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}.
page_idrequiredmaintenance_idrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
io.usefulapiOfficial publisher
Hosted MCP server for Ably realtime messaging: inspect channel history, presence and occupancy, publish messages, and review app usage and configuration.
io.usefulapiOfficial publisher
Hosted read-only MCP server that lets an assistant look up Woffu company users, employment contracts, departments and offices.
io.usefulapiOfficial publisher
Hosted MCP server for White Label Loyalty: browse rewards, read a customer's points wallet and tier progress, and buy rewards with points.
io.usefulapiOfficial publisher
Hosted Weekdone connector that lets an assistant read weekly reports, teams, objectives and KPIs, and add report items, comments and KPI values.
io.usefulapiOfficial publisher
Hosted read-only MCP server that lets an assistant list WebinarKit webinars, their dates, series, meetings and white-label sub-accounts.
{ "mcpServers": { "instatus": { "url": "https://instatus.usefulapi.io/mcp" } }}