# Sorry MCP by usefulapi (remote · sorry-app.usefulapi.io)

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

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `sorry-app.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-sorry-app/sorry-app.md), [page](https://verifymcp.io/servers/io-usefulapi-sorry-app/sorry-app)

## Channel facts

- Endpoint: `https://sorry-app.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.7.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Sorry MCP by usefulapi server?

Sorry MCP by usefulapi is a hosted endpoint at https://sorry-app.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-sorry-app": {
      "type": "remote",
      "url": "https://sorry-app.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-sorry-app --url 'https://sorry-app.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-sorry-app:
    url: "https://sorry-app.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-sorry-app": {
      "Transport": "http",
      "Url": "https://sorry-app.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-sorry-app -t streamable-http -u 'https://sorry-app.usefulapi.io/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 18, −47)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 65)

First indexed and scored.

## MCP tools (21)

### `sorryapp_list_pages` (~63 tokens)

List status 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_get_page` (~91 tokens)

Get status 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=...

Input parameters:

- `include` (array): Related resources to embed in the reply.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).

### `sorryapp_list_components` (~90 tokens)

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.

Input parameters:

- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).

### `sorryapp_get_component` (~70 tokens)

Get component

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

Input parameters:

- `component_id` (required): The component id.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).

### `sorryapp_list_notices` (~214 tokens)

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.

Input parameters:

- `created_after` (string): Only notices created after this ISO 8601 date or datetime.
- `include` (array): Embed each notice's components and/or updates.
- `page` (integer): Page number, starting at 1.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).
- `state` (string): Only notices in this state (planned: scheduled, cancelled, underway, complete; unplanned: investigating, identified, recovering, resolved, false_alarm).
- `subject_contains` (string): Only notices whose subject contains this text.
- `type` (string): planned = maintenance, unplanned = incident.

### `sorryapp_get_notice` (~95 tokens)

Get notice

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

Input parameters:

- `include` (array): Embed the notice's components and/or updates.
- `notice_id` (required): The notice id.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).

### `sorryapp_list_notice_updates` (~89 tokens)

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.

Input parameters:

- `notice_id` (required): The notice id.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).

### `sorryapp_get_notice_update` (~85 tokens)

Get notice update

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

Input parameters:

- `notice_id` (required): The notice id.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).
- `update_id` (required): The update id.

### `sorryapp_list_notice_templates` (~136 tokens)

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.

Input parameters:

- `component_name_contains` (string): Only templates scoped to a component whose name contains this text.
- `name_contains` (string): Only templates whose name contains this text.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).

### `sorryapp_list_update_templates` (~129 tokens)

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.

Input parameters:

- `component_name_contains` (string): Only templates scoped to a component whose name contains this text.
- `name_contains` (string): Only templates whose name contains this text.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).

### `sorryapp_list_subscribers` (~162 tokens)

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.

Input parameters:

- `component_id`: Only subscribers to this component (plus those subscribed to all components).
- `include` (array): Embed each subscriber's components.
- `page` (integer): Page number, starting at 1.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).
- `per_page` (integer): Results per page (Sorry's default for subscribers is 500).

### `sorryapp_get_subscriber` (~80 tokens)

Get subscriber

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

Input parameters:

- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).
- `subscriber_id` (required): The subscriber id.

### `sorryapp_list_timezones` (~37 tokens)

List timezones

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

### `sorryapp_create_component` (~125 tokens)

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.

Input parameters:

- `confirm` (boolean, required): Set true only after the user approved this public status change or subscriber addition and any requested notification.
- `description` (string): Optional text shown next to the name.
- `name` (string, required): Component name, e.g. API.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).

### `sorryapp_update_component` (~144 tokens)

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}.

Input parameters:

- `component_id` (required): The component id.
- `confirm` (boolean, required): Set true only after the user approved this public status change or subscriber addition and any requested notification.
- `description` (string): New description.
- `name` (string): New name.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).

### `sorryapp_create_incident` (~283 tokens)

Create incident notice

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.

Input parameters:

- `component_ids` (array): Ids of the affected components (from sorryapp_list_components). While the notice is open they show as degraded.
- `confirm` (boolean, required): Set true only after the user approved this public status change or subscriber addition and any requested notification.
- `initial_comment` (string): First update shown on the incident (public).
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).
- `publish` (boolean): should_publish: true also sends this out to subscribers and integrations (email, SMS, Slack, Teams, X). Default false: sent as should_publish=false to suppress the requested broadcast. The notice/cha…
- `subject` (string, required): Incident title, e.g. API performance issues.

### `sorryapp_create_maintenance` (~339 tokens)

Create maintenance notice

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.

Input parameters:

- `begins_at_date` (string): Start date, YYYY-MM-DD (in the status page's timezone).
- `begins_at_time` (string): Start time, 24-hour HH:MM:SS.
- `component_ids` (array): Ids of the affected components (from sorryapp_list_components). While the notice is open they show as degraded.
- `confirm` (boolean, required): Set true only after the user approved this public status change or subscriber addition and any requested notification.
- `duration_in_minutes` (integer): Expected length of the maintenance in minutes.
- `initial_comment` (string): First update shown on the notice (public).
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).
- `publish` (boolean): should_publish: true also sends this out to subscribers and integrations (email, SMS, Slack, Teams, X). Default false: sent as should_publish=false to suppress the requested broadcast. The notice/cha…
- `should_automate_schedule` (boolean): true: Sorry moves the notice to underway and complete at the scheduled times.
- `subject` (string, required): Maintenance title.

### `sorryapp_update_notice` (~398 tokens)

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}.

Input parameters:

- `additional_comment` (string): A new public update to add to the notice timeline. publish controls the requested subscriber/integration broadcast; false still changes the public page.
- `begins_at_date` (string): Planned notices only: new start date YYYY-MM-DD.
- `begins_at_time` (string): Planned notices only: new start time HH:MM:SS.
- `component_ids` (array): Ids of the affected components (from sorryapp_list_components). While the notice is open they show as degraded.
- `confirm` (boolean, required): Set true only after the user approved this public status change or subscriber addition and any requested notification.
- `duration_in_minutes` (integer): Planned notices only: new duration in minutes.
- `notice_id` (required): The notice id.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).
- `publish` (boolean): should_publish: true also sends this out to subscribers and integrations (email, SMS, Slack, Teams, X). Default false: sent as should_publish=false to suppress the requested broadcast. The notice/cha…
- `state` (string): New state. Planned: scheduled, cancelled, underway, complete. Unplanned: investigating, identified, recovering, resolved, false_alarm.
- `subject` (string): New subject.

### `sorryapp_create_notice_update` (~209 tokens)

Add 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.

Input parameters:

- `confirm_publish` (boolean, required): Must be true. Confirms you understand the update is published on the PUBLIC status page and pushed to subscribers and configured integrations (email, SMS, Slack, Teams, X): Sorry's docs offer no way…
- `content` (string, required): The update text.
- `notice_id` (required): The notice id.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).

### `sorryapp_edit_notice_update` (~142 tokens)

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}.

Input parameters:

- `confirm` (boolean, required): Set true only after the user approved this public status change or subscriber addition and any requested notification.
- `content` (string, required): The new text.
- `notice_id` (required): The notice id.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).
- `update_id` (required): The update id.

### `sorryapp_create_subscriber` (~188 tokens)

Add one 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.

Input parameters:

- `component_ids` (array): Subscribe to only these components (default: all components).
- `confirm` (boolean, required): Set true only after the user approved this public status change or subscriber addition and any requested notification.
- `email` (string): The subscriber's email address.
- `page_id` (string, required): The status page id, e.g. 12ab34cd (from sorryapp_list_pages).
- `phone_number` (string): Phone number with the international country code, e.g. +441234567890.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-sorry-app/sorry-app#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 65
- 2026-10-31: 65

## Common questions

### What is the Sorry MCP by usefulapi server?

Sorry MCP by usefulapi is listed in the public MCP registry as io.usefulapi/sorry-app. Read status pages and incidents; make confirmed public changes and manage individual subscribers. This page covers its hosted endpoint (https://sorry-app.usefulapi.io/mcp).

### Is the Sorry MCP by usefulapi server safe to use?

Sorry MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Sorry MCP by usefulapi server expose?

Sorry MCP by usefulapi exposes 21 tools: sorryapp_list_pages, sorryapp_get_page, sorryapp_list_components, sorryapp_get_component, sorryapp_list_notices, and 16 more. Their descriptions and schemas cost roughly 3,169 tokens of context every time the server is loaded.

### Does the Sorry MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Sorry MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Sorry MCP by usefulapi server still maintained?

Sorry MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Sorry MCP by usefulapi server?

VerifyMCP ran 4 checks on Sorry MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Sorry MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://sorry-app.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/sorry-app/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-sorry-app/sorry-app.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-sorry-app/sorry-app/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-sorry-app/sorry-app.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-sorry-app/sorry-app