io.usefulapi由 usefulapi.io 發布官方發布者v1.8.4更新於 Nov 7, 2026
Read status pages and incidents; make confirmed public changes and manage individual subscribers.
發布方自己的服務：Ably MCP by usefulapi
讀取 Sorry 狀態頁、元件、事件與訂閱者，並在確認後對公開狀態頁做出變更，例如事件、維護與通知更新。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.usefulapi%2Fsorry-app/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"sorry-by-usefulapi": {
"type": "http",
"url": "https://sorry-app.usefulapi.io/mcp"
}
}
}https://sorry-app.usefulapi.io/mcp.claude mcp add --transport http sorry-app https://sorry-app.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 Sorry credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/sorry-app/
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 sorryapp_upgrade (it returns a Stripe Checkout link). Cancel any time with sorryapp_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running sorryapp_upgrade before then undoes the cancel. Or write to [email protected].
MIT
Create a token in Sorry under My Account → API Tokens. This independent connector uses customer-authorized API access, with no claimed vendor endorsement or partner status. Your vendor subscription, API eligibility, quotas and notification/SMS charges remain separate. Sorry documents 10 requests per second per API token.
The token is encrypted for authorized API calls. Requested status records and subscriber contact details reach your chosen AI client and LLM provider. Credential fields, connected-token values and Slack/Teams webhook URLs are redacted. Revoke the token in Sorry to stop access; disconnect UsefulAPI to end this connection.
Usage and billing follow this token. Rotation creates a new UsefulAPI identity and does not automatically transfer Pro. Cancel the old UsefulAPI plan before rotation or contact support before changing the token.
Every write requires explicit confirmation. Components, notices and notice updates are public. publish=false requests suppression of the subscriber/integration broadcast; it does not make a private draft. publish=true additionally requests delivery through configured email, SMS, Slack, Teams or X channels. Vendor automations may also react to a public change, so review its content and audience.
The separate new-notice-update tool exposes no verified suppression switch and requires explicit broadcast confirmation. Adding a subscriber enables future notifications to that address or phone number. The connector does not delete resources or import/remove subscriber lists.
No vendor call is automatically replayed. After a timeout or uncertain response, check Sorry before repeating a write: duplicate calls can duplicate public records or notifications. A valid response record id is required before reporting an acknowledged change.
Notice lists support the documented page parameter, and subscriber lists support page/per_page. Template tools return the vendor-default page with documented filters; template paging and notice per_page controls are withheld pending verified request contracts. Maintenance times are sent as HH:MM:SS in the status page’s timezone.
The 21 tools were checked against current vendor documentation and local mocks. Missing/nonexistent-token checks received the vendor’s JSON401. No authenticated customer reads, real public status changes, subscriber additions or notifications were tested.
來源：servers/sorry-app/README.md，提交 4046075
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.
無需輸入參數。
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=...
includepage_id必填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.
page_id必填Get component
Get one component of a status page. Sorry: GET /v1/pages/{page_id}/components/{component_id}.
page_id必填component_id必填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.
pagetypestateincludepage_id必填created_aftersubject_containsGet notice
Get one notice (incident or maintenance) with its state, times and public link. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}.
includepage_id必填notice_id必填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.
page_id必填notice_id必填Get notice update
Get one update of a notice. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}/updates/{update_id}.
page_id必填notice_id必填update_id必填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.
page_id必填name_containscomponent_name_containsList 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.
page_id必填name_containscomponent_name_containsList 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.
pageincludepage_id必填per_pagecomponent_idGet subscriber
Get one subscriber of a status page (personal data; webhook URLs redacted). Sorry: GET /v1/pages/{page_id}/subscribers/{subscriber_id}.
page_id必填subscriber_id必填List timezones
List the timezone names Sorry accepts for a status page (name and GMT offset label). Sorry: GET /v1/timezones.
無需輸入參數。
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.
name必填confirm必填page_id必填descriptionUpdate 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}.
nameconfirm必填page_id必填descriptioncomponent_id必填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.
confirm必填page_id必填publishsubject必填component_idsinitial_commentCreate 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.
confirm必填page_id必填publishsubject必填component_idsbegins_at_datebegins_at_timeinitial_commentduration_in_minutesshould_automate_scheduleUpdate 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}.
stateconfirm必填page_id必填publishsubjectnotice_id必填component_idsbegins_at_datebegins_at_timeadditional_commentduration_in_minutesAdd 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.
content必填page_id必填notice_id必填confirm_publish必填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}.
confirm必填content必填page_id必填notice_id必填update_id必填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.
emailconfirm必填page_id必填phone_numbercomponent_ids已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
io.usefulapi官方發布者
用於 Ably 的 MCP 伺服器——頻道歷史、線上狀態、佔用情況、統計、發布和應用管理。AI 翻譯
io.usefulapi官方發布者
託管式唯讀 MCP 伺服器，讓助理查詢 Woffu 公司的使用者、勞動契約、部門與辦公地點。
io.usefulapi官方發布者
託管的 White Label Loyalty MCP 伺服器：瀏覽獎勵、查看客戶點數錢包與等級進度，並以點數購買獎勵。
io.usefulapi官方發布者
託管的 Weekdone 連接器，讓助理讀取週報、團隊、目標與 KPI，並新增報告項目、留言和 KPI 數值。
io.usefulapi官方發布者
託管式唯讀 MCP 伺服器，讓助理列出 WebinarKit 的網路研討會、場次時間、系列、會議以及白標子帳戶。
{ "mcpServers": { "sorry-app": { "url": "https://sorry-app.usefulapi.io/mcp" } }}