io.usefulapi/sorry-app
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
Sorry MCP by usefulapi
Publisher-provided description
Read status pages and incidents; make confirmed public changes and manage individual subscribers.
Summary by lookupd
Reads status pages, components, incidents and maintenance; creates or edits public notices and manages page subscribers.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http sorry-app https://sorry-app.usefulapi.io/mcp
Codex, remote (streamable-http)
codex mcp add sorry-app --url https://sorry-app.usefulapi.io/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"sorry-app": {
"url": "https://sorry-app.usefulapi.io/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (21 tools)
Publisher-provided text
sorryapp_list_pagesList the status pages the API token's user can access: id, name, state (operational/degraded/...), timezone, locale, support contacts, notification channels. Thsorryapp_get_pageGet one status page, optionally with related resources embedded (brand, components, custom_domain, notices, notices.updates, theme). Sorry: GET /v1/pages/{page_sorryapp_list_componentsList a status page's components (the parts of your service shown on the page): id, name, description, state (operational/degraded/partially-degraded), position,sorryapp_get_componentGet one component of a status page. Sorry: GET /v1/pages/{page_id}/components/{component_id}.sorryapp_list_noticesList a status page's notices (incidents = type unplanned, maintenance = type planned): id, type, state, timeline_state, subject, synopsis, began/ended times, pusorryapp_get_noticeGet one notice (incident or maintenance) with its state, times and public link. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}.sorryapp_list_notice_updatesList 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_get_notice_updateGet one update of a notice. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}/updates/{update_id}.sorryapp_list_notice_templatesList the page's notice templates (reusable subject + opening comment for new incidents or maintenance): id, name, subject, initial_comment, optional component_isorryapp_list_update_templatesList the page's update templates (reusable text for one notice update): id, name, content, optional component_id. Returns the vendor-default template page; pagisorryapp_list_subscribersList a status page's subscribers (people and channels notified of notices): id, email, phone number, name, company, tags, created time. Webhook URLs of Slack/Tesorryapp_get_subscriberGet one subscriber of a status page (personal data; webhook URLs redacted). Sorry: GET /v1/pages/{page_id}/subscribers/{subscriber_id}.sorryapp_list_timezonesList the timezone names Sorry accepts for a status page (name and GMT offset label). Sorry: GET /v1/timezones.sorryapp_create_componentWRITE: 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_update_componentWRITE: rename a component or change its description on the PUBLIC status page (overwrites the previous value). It cannot change the component's state: state folsorryapp_create_incidentWRITE: open an incident (an unplanned notice) on the status page. These changes are PUBLIC on the status page, including publish=false. publish=true additionallsorryapp_create_maintenanceWRITE: schedule maintenance (a planned notice) on the status page. These changes are PUBLIC on the status page, including publish=false. publish=true additionalsorryapp_update_noticeWRITE: change a notice: its subject, state (for example resolved), affected components, schedule, and/or add a comment (an update) to its timeline. These changesorryapp_create_notice_updateWRITE: 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 consorryapp_edit_notice_updateWRITE: 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/sorryapp_create_subscriberWRITE: 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 p
Details
- Version: 1.9.3
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 556 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/sorry-app/
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.usefulapi/sorry-app)
- 62071 servers
- Last crawl: 2026-11-11T16:39:06.253Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp