Sorry MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Sorry MCP by usefulapi is answering right now. Last checked 4 min ago. It exposes 21 tools. Last commit 1 Nov 2026.

Read status pages and incidents; make confirmed public changes and manage individual subscribers.

Uptime history 15 hours of history

15 hours agonow

100.0%

Uptime 24h

56 of 56 checks

Tools

read from the server

246 ms

Response time

average over 24h

Stars

last commit 1 Nov 2026

Nothing serious here today

Today is the operative word: we check Sorry MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add sorry-app --transport http https://sorry-app.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://sorry-app.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.sorry-app]
url = "https://sorry-app.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "sorry-app": {
      "url": "https://sorry-app.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "sorry-app": {
      "type": "http",
      "url": "https://sorry-app.usefulapi.io/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

sorryapp

sorryapp_create_component

WRITE: add a component to a status page. It appears on the PUBLIC status page immediately, as operational. Sorry: POST /v1/pages/{page_id}/components.

sorryapp_create_incident

WRITE: open an incident (an unplanned notice) on the status page. These changes are PUBLIC on the status page, including publish=false. publish=true additionally requests delivery to subscribers and integrations (email, SMS, Slack, Teams, X); vendor SMS/notification charges may apply. Confirm the content and audience first. It marks the listed components degraded on the PUBLIC page. Starts in the investigating state. Sorry: POST /v1/pages/{page_id}/notices with type=unplanned.

sorryapp_create_maintenance

WRITE: schedule maintenance (a planned notice) on the status page. These changes are PUBLIC on the status page, including publish=false. publish=true additionally requests delivery to subscribers and integrations (email, SMS, Slack, Teams, X); vendor SMS/notification charges may apply. Confirm the content and audience first. Sorry: POST /v1/pages/{page_id}/notices with type=planned.

sorryapp_create_notice_update

WRITE: add one update (a comment) to a notice's timeline. It is PUBLIC on the status page, and Sorry's docs say a new update is also published to the page's configured integrations (email, SMS, Slack, Teams, X). The docs list no switch to suppress that on this endpoint, so confirm_publish=true is required; this endpoint has no exposed suppression switch. Sorry: POST /v1/pages/{page_id}/notices/{notice_id}/updates.

sorryapp_create_subscriber

WRITE: add ONE subscriber (an email address and/or a phone number) to a status page. From then on that person is emailed/texted about notices published on the page, and Sorry may send them a confirmation. Add only people who asked to be notified. No bulk import. Sorry: POST /v1/pages/{page_id}/subscribers.

sorryapp_edit_notice_update

WRITE: rewrite the text of an existing notice update on the PUBLIC status page (overwrites the previous text; the old text is not kept). Sorry: PATCH /v1/pages/{page_id}/notices/{notice_id}/updates/{update_id}.

sorryapp_get_component

Get one component of a status page. Sorry: GET /v1/pages/{page_id}/components/{component_id}.

sorryapp_get_notice

Get one notice (incident or maintenance) with its state, times and public link. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}.

sorryapp_get_notice_update

Get one update of a notice. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}/updates/{update_id}.

sorryapp_get_page

Get one status page, optionally with related resources embedded (brand, components, custom_domain, notices, notices.updates, theme). Sorry: GET /v1/pages/{page_id}?include=...

sorryapp_get_subscriber

Get one subscriber of a status page (personal data; webhook URLs redacted). Sorry: GET /v1/pages/{page_id}/subscribers/{subscriber_id}.

sorryapp_list_components

List a status page's components (the parts of your service shown on the page): id, name, description, state (operational/degraded/partially-degraded), position, parent_id. Sorry: GET /v1/pages/{page_id}/components.

sorryapp_list_notice_templates

List the page's notice templates (reusable subject + opening comment for new incidents or maintenance): id, name, subject, initial_comment, optional component_id. Returns the vendor-default template page; paging controls are withheld pending a verified request contract. Sorry: GET /v1/pages/{page_id}/notice_templates.

sorryapp_list_notice_updates

List the updates (timeline comments) of one notice: id, content, should_publish, public link, times. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}/updates.

sorryapp_list_notices

List a status page's notices (incidents = type unplanned, maintenance = type planned): id, type, state, timeline_state, subject, synopsis, began/ended times, public link. Optional filters and embedded updates/components. Sorry: GET /v1/pages/{page_id}/notices.

sorryapp_list_pages

List the status pages the API token's user can access: id, name, state (operational/degraded/...), timezone, locale, support contacts, notification channels. The id is the page_id every other tool takes. Sorry: GET /v1/pages.

sorryapp_list_subscribers

List a status page's subscribers (people and channels notified of notices): id, email, phone number, name, company, tags, created time. Webhook URLs of Slack/Teams subscribers are redacted. Contains personal data. Sorry: GET /v1/pages/{page_id}/subscribers.

sorryapp_list_timezones

List the timezone names Sorry accepts for a status page (name and GMT offset label). Sorry: GET /v1/timezones.

sorryapp_list_update_templates

List the page's update templates (reusable text for one notice update): id, name, content, optional component_id. Returns the vendor-default template page; paging controls are withheld pending a verified request contract. Sorry: GET /v1/pages/{page_id}/update_templates.

sorryapp_update_component

WRITE: rename a component or change its description on the PUBLIC status page (overwrites the previous value). It cannot change the component's state: state follows open notices (use the notice tools). Sorry: PATCH /v1/pages/{page_id}/components/{component_id}.

sorryapp_update_notice

WRITE: change a notice: its subject, state (for example resolved), affected components, schedule, and/or add a comment (an update) to its timeline. These changes are PUBLIC on the status page, including publish=false. publish=true additionally requests delivery to subscribers and integrations (email, SMS, Slack, Teams, X); vendor SMS/notification charges may apply. Confirm the content and audience first. Fields you pass overwrite the previous values. Sorry: PATCH /v1/pages/{page_id}/notices/{notice_id}.

Endpoints

URL	Transport	State	Latency	Checked
https://sorry-app.usefulapi.io/mcp	streamable-http	answering	184 ms	4 min ago

Alternatives to Sorry MCP by usefulapi

same job, measured the same way

StatusPal MCP by usefulapi

by usefulapi

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

11 tools answering

Instatus MCP by usefulapi

by usefulapi

Manage status pages: components, incidents and maintenances; set live component status.

14 tools answering

Better Stack MCP by usefulapi

by usefulapi

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

9 tools answering

Instatus

by instatus

Status pages, incidents, maintenance, components and subscribers on Instatus.

answering

Status.io MCP by usefulapi

by usefulapi

Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status.

20 tools answering

Openuptime

by openuptime

Manage uptime monitors, incidents and status pages from any MCP client.

answering

Release Radar MCP by usefulapi

by usefulapi

Correlate GitHub releases with Sentry issues and PagerDuty incidents.

5 tools answering

Dead Man's Snitch MCP by usefulapi

by usefulapi

Read Dead Man's Snitch monitors and status; create, tag, pause and unpause snitches.

8 tools answering

Sorry MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Sorry MCP by usefulapi do?

It exposes 21 tools, read directly from the server on our last check. Among them: sorryapp_create_component, sorryapp_create_incident, sorryapp_create_maintenance, sorryapp_create_notice_update, sorryapp_create_subscriber, sorryapp_edit_notice_update and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Sorry MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 56 of 56 checks got a reply (100.0%), average response time 246 ms. The bar chart above shows every period we have measured.

How do I connect Sorry MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Sorry MCP by usefulapi need an API key?

No. Sorry MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Sorry MCP by usefulapi?

It answers our handshake in 246 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Sorry MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at sorry-app.usefulapi.io, which runs on its operator's own terms.