Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Sorry (BYOK) icon

Sorry (BYOK)

Read your Sorry status pages, components, incident and maintenance notices with their updates, notice templates and branding with your own API token

Unify Dynamics LLC

Tools12read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderSorryunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Sorry status pages do I have and are they operational?
Tools called
list_pages
Show the settings of Sorry status page 12ab34cd
Tools called
get_page
Which components are degraded on my Sorry status page?
Tools called
list_components
Is Sorry component 3 operational?
Tools called
get_component
What incidents did my Sorry status page report recently?
Tools called
list_notices
Show Sorry notice 432500
Tools called
get_notice

About

Sorry (BYOK) lets an AI assistant read your own Sorry data through the Sorry API with a key you supply (Sorry API token). Read-only: 12 tools (list_pages, get_page, list_components, get_component, list_notices, get_notice, list_notice_updates, get_notice_update, list_notice_templates, get_page_branding, get_custom_domain, list_timezones). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.sorryapp.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sorry. Sorry and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Sorry API (api.sorryapp.com) with a BYOK key; documentation: https://docs.sorryapp.com/v1. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

12 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data12 tools
  • List pagesList the status pages of the account with name, current state, time zone, locale, support contact and public address.
  • Get pageGet one status page: current state, time zone, locale, support contact, public address and timeline settings.
  • List componentsList the components (the parts of your service shown on the status page) with state, description, order and parent component.
  • Get componentGet one component of a status page with its current state.
  • List noticesList the notices (incidents and planned maintenance) of a status page with type, state, subject, synopsis, times and public link.
  • Get noticeGet one notice (incident or planned maintenance) with its state, subject, synopsis, schedule and public link.
  • List notice updatesList the updates posted to one notice, oldest first as published, with text, whether it was sent out to subscribers, and a public link.
  • Get notice updateGet one update of a notice.
  • List notice templatesList the saved notice templates of a status page with name, subject and starting text.
  • Get page brandingGet the colours used by a status page (state colours, navbar, header and body colours).
  • Get custom domainGet the custom domain of a status page and the DNS record (type, from, to) that has to point at Sorry.
  • List timezonesList the time zone names a status page can use, with their UTC offset.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-sorry.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 12 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-sorry.connectorbay.com/mcp
RESTPOST https://byok-sorry.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-sorry.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Sorry API token in the X-Upstream-Key header (get one at docs.sorryapp.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Sorry connector: questions and answers

What is the Sorry connector?

Sorry (BYOK) lets an AI assistant read your own Sorry data through the Sorry API with a key you supply (Sorry API token). It is a hosted MCP server with 12 tools such as List pages, Get page, List components, Get component, List notices, Get notice, published by Unify Dynamics LLC. It is independent and not affiliated with Sorry.

How do I connect Sorry to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-sorry.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-sorry.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-sorry.json.

Do I need a Sorry account or API key?

Yes: this is a bring-your-own-key connector. Create a Sorry API token at https://docs.sorryapp.com/v1/authentication and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Sorry read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Sorry connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Xata (BYOK)

Read your Xata organizations, projects, Postgres branches, regions, limits and branch logs with your own API key

Live · MCP + REST9 tools

Yahoo Japan Text Analysis (BYOK)

Analyze Japanese text with the LY Corporation text analysis API: readings, proofreading, key phrases, morphology, dependency parsing, named entities and kana-kanji conversion with your own Client ID

Live · MCP + REST7 tools

Zamzar (BYOK)

Read your Zamzar file conversion jobs, uploaded files, remaining credits and supported formats with your own API key

Live · MCP + REST8 tools

Zenduty (BYOK)

Read your Zenduty teams, services, escalation policies, schedules, maintenance windows and incidents with your own API key

Live · MCP + REST12 tools

Zenoti (BYOK)

Read your Zenoti spa and salon centers, services, rooms, employees, products, class sessions and stock levels with your own Zenoti API key

Live · MCP + REST9 tools

Zep (BYOK)

Read the users, conversation threads, memory graphs, context templates and ontology of your Zep project with your own API key

Live · MCP + REST9 tools

Documentation

Back to top

Sorry (BYOK) — connector documentation

  • MCP endpoint: https://byok-sorry.connectorbay.com/mcp
  • REST API: POST https://byok-sorry.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-sorry.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Sorry Sorry API token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-sorry.connectorbay.com/health · Tool schemas: https://byok-sorry.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-sorry · agent@connectorbay.com

What Sorry (BYOK) is for

Sorry (BYOK) lets an AI assistant read your own Sorry data through the Sorry API with a key you supply (Sorry API token). Read-only: 12 tools (list_pages, get_page, list_components, get_component, list_notices, get_notice, list_notice_updates, get_notice_update, list_notice_templates, get_page_branding, get_custom_domain, list_timezones). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.sorryapp.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sorry. Sorry and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Sorry status pages do I have and are they operational?"
  • "Show the settings of Sorry status page 12ab34cd"
  • "Which components are degraded on my Sorry status page?"
  • "Is Sorry component 3 operational?"
  • "What incidents did my Sorry status page report recently?"
  • "Show Sorry notice 432500"

What it does

  • list_pages: List the status pages of the account with name, current state, time zone, locale, support contact and public address.
  • get_page: Get one status page: current state, time zone, locale, support contact, public address and timeline settings.
  • list_components: List the components (the parts of your service shown on the status page) with state, description, order and parent component.
  • get_component: Get one component of a status page with its current state.
  • list_notices: List the notices (incidents and planned maintenance) of a status page with type, state, subject, synopsis, times and public link.
  • get_notice: Get one notice (incident or planned maintenance) with its state, subject, synopsis, schedule and public link.
  • list_notice_updates: List the updates posted to one notice, oldest first as published, with text, whether it was sent out to subscribers, and a public link.
  • get_notice_update: Get one update of a notice.
  • list_notice_templates: List the saved notice templates of a status page with name, subject and starting text.
  • get_page_branding: Get the colours used by a status page (state colours, navbar, header and body colours).
  • get_custom_domain: Get the custom domain of a status page and the DNS record (type, from, to) that has to point at Sorry.
  • list_timezones: List the time zone names a status page can use, with their UTC offset.

BYOK key

You bring your own Sorry Sorry API token (https://docs.sorryapp.com/v1/authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.sorryapp.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Sorry API (api.sorryapp.com) with a BYOK key; documentation: https://docs.sorryapp.com/v1. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sorry. Sorry and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Sorry account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Sorry (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Sorry (BYOK) is. Sorry (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Sorry data: Read your Sorry status pages, components, incident and maintenance notices with their updates, notice templates and branding with your own API token. You bring your own Sorry Sorry API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Sorry call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.sorryapp.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Sorry rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Sorry receives. The request we make on your behalf, including the key and the arguments, under Sorry's own terms and privacy policy. Sorry acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Sorry gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Sorry data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Sorry (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Sorry at any time to end all access.

Children. Sorry (BYOK) is a general-audience service operated by the adult using the assistant, under Sorry's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Sorry (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Sorry (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Sorry (BYOK) provides: Read your Sorry status pages, components, incident and maintenance notices with their updates, notice templates and branding with your own API token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Sorry credentials and only access data you are allowed to access. Sorry's terms apply to your use of Sorry; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sorry. Sorry and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Sorry returns, lightly trimmed; it may be incomplete, delayed or changed by Sorry. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Sorry account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Sorry's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Sorry may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Sorry key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Sorry takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-sorry

Sorry (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Sorry (BYOK) never asks for them.

Get Sorry (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Sorry Sorry API token. Create one at https://docs.sorryapp.com/v1/authentication, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Sorry. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Sorry.