Sorry MCP by usefulapi
REMOTE · SORRY-APP.USEFULAPI.IO
Read status pages and incidents; make confirmed public changes and manage individual subscribers.
Available components
Last scanned (48 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://sorry-app.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sorry-app.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sorry-app.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/sorry-app/ |
| http (plaintext) | http://sorry-app.usefulapi.io/mcp | Inconclusive | 302 | http://sorry-app.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sorryapp_create_component Create component ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | 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 | yes | Component name, e.g. API. |
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
No output schema declared.
No examples provided.
sorryapp_create_incident Create incident notice ~283
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.
| Name | Type | Req | Description |
|---|---|---|---|
| component_ids | array | – | Ids of the affected components (from sorryapp_list_components). While the notice is open they show as degraded. |
| confirm | boolean | yes | 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 | yes | 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 | yes | Incident title, e.g. API performance issues. |
No output schema declared.
No examples provided.
sorryapp_create_maintenance Create maintenance notice ~339
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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 | yes | Maintenance title. |
No output schema declared.
No examples provided.
sorryapp_create_notice_update Add notice update ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_publish | boolean | yes | 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 | yes | The update text. |
| notice_id | – | yes | The notice id. |
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
No output schema declared.
No examples provided.
sorryapp_create_subscriber Add one subscriber ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| component_ids | array | – | Subscribe to only these components (default: all components). |
| confirm | boolean | yes | Set true only after the user approved this public status change or subscriber addition and any requested notification. |
| string | – | The subscriber's email address. | |
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
| phone_number | string | – | Phone number with the international country code, e.g. +441234567890. |
No output schema declared.
No examples provided.
sorryapp_edit_notice_update Edit notice update ~142
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Set true only after the user approved this public status change or subscriber addition and any requested notification. |
| content | string | yes | The new text. |
| notice_id | – | yes | The notice id. |
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
| update_id | – | yes | The update id. |
No output schema declared.
No examples provided.
sorryapp_get_component Get component ~70
Get one component of a status page. Sorry: GET /v1/pages/{page_id}/components/{component_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | – | yes | The component id. |
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
No output schema declared.
No examples provided.
sorryapp_get_notice Get notice ~95
Get one notice (incident or maintenance) with its state, times and public link. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | Embed the notice's components and/or updates. |
| notice_id | – | yes | The notice id. |
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
No output schema declared.
No examples provided.
sorryapp_get_notice_update Get notice update ~85
Get one update of a notice. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}/updates/{update_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| notice_id | – | yes | The notice id. |
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
| update_id | – | yes | The update id. |
No output schema declared.
No examples provided.
sorryapp_get_page Get status page ~91
Get one status page, optionally with related resources embedded (brand, components, custom_domain, notices, notices.updates, theme). Sorry: GET /v1/pages/{page_id}?include=...
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | Related resources to embed in the reply. |
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
No output schema declared.
No examples provided.
sorryapp_get_subscriber Get subscriber ~80
Get one subscriber of a status page (personal data; webhook URLs redacted). Sorry: GET /v1/pages/{page_id}/subscribers/{subscriber_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
| subscriber_id | – | yes | The subscriber id. |
No output schema declared.
No examples provided.
sorryapp_list_components List components ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
No output schema declared.
No examples provided.
sorryapp_list_notice_templates List notice templates ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
No output schema declared.
No examples provided.
sorryapp_list_notice_updates List notice updates ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| notice_id | – | yes | The notice id. |
| page_id | string | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
No output schema declared.
No examples provided.
sorryapp_list_notices List notices ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
sorryapp_list_pages List status pages ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sorryapp_list_subscribers List subscribers ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
| per_page | integer | – | Results per page (Sorry's default for subscribers is 500). |
No output schema declared.
No examples provided.
sorryapp_list_timezones List timezones ~37
List the timezone names Sorry accepts for a status page (name and GMT offset label). Sorry: GET /v1/timezones.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sorryapp_list_update_templates List update templates ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
No output schema declared.
No examples provided.
sorryapp_update_component Update component ~144
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | – | yes | The component id. |
| confirm | boolean | yes | 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 | yes | The status page id, e.g. 12ab34cd (from sorryapp_list_pages). |
No output schema declared.
No examples provided.
sorryapp_update_notice Update notice ~398
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | yes | The notice id. |
| page_id | string | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · sorry-app.usefulapi.io
claude mcp add --transport http io-usefulapi-sorry-app 'https://sorry-app.usefulapi.io/mcp'
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.