generate_apologyLABSCO SUMMARY
A joke that was actually designed.
Severity and style are separate axes, which is the correct decomposition and not what a throwaway would have done — the same incident reads very differently in a legal disclaimer and a haiku. The escalation ladder is the tool that gives the game away: it exists because calibrating how sorry to be is genuinely the hard part. Take the grader at face value — the README calls it heuristic and for entertainment, and it means it.
What it is
An MCP server that writes apologies. It is a joke with a working implementation: the parameters are a severity, a style and the thing you did, and the surface includes a calibration tool and a grader, which is more thought than the premise required.
What you get
- An apology generated from a severity, a style, the context of what happened and a recipient —
generate_apology - Five severity levels from a typo in a comment up to leaked user data, so the register matches the incident rather than defaulting to grovelling —
TRIVIAL,MINOR,MAJOR,CRITICAL,NUCLEAR - Fifteen styles including professional, casual, poetic, grovelling, haiku, legal disclaimer, corporate doublespeak, Shakespearean, pirate, passive-aggressive, robot and existential
- A calibration tool that returns one apology at every severity level in the same style, for when you genuinely cannot tell how sorry to be —
escalation_ladder - A grader for an apology you already drafted, scoring sincerity, cringe and hedging out of ten with a one-line verdict — heuristic, and the README says so —
rate_my_apology - A prompt that turns an incident description into a full crisis-communication plan with three options — safe, honest and desperate — each with its own risk assessment —
save_my_ass - Plain HTTP endpoints alongside the MCP transports, including a liveness check and a browser-callable demo wrapper around the generator
Requirements
No account and no key, but you run it yourself: in September 2026 the hosted endpoint the README lists answered MCP requests with an Invalid Host header error. Clone the repository, install from requirements.txt and start the module with Python 3.10 or newer; the server listens on the port given by PORT, defaulting to 8000, with streamable HTTP at /mcp and legacy SSE at /sse. A Dockerfile is included. The package is apology-as-a-service (version 0.2.0). CORS is open on all routes so the demo endpoint works from a browser.
Setup effort
Build from source — git clone https://github.com/Ajollyworld79/Apology-as-a-Service
USE CASES
01
Working out how sorry to be
Ask for the full ladder in one style and read the levels side by side before committing to a register.
02
Drafting the message after an incident
Set the severity and pick a professional register, and get something to edit rather than a blank message box.
03
Checking whether your draft lands
Run it through the grader and see how it scores on sincerity and hedging before you send it.
04
Planning the whole response, not just the note
Get three options with risk assessments — safe, honest and desperate — and pick the one you can live with.
3 tools
Listed in project docs. Your client may show a different list.
escalation_ladderrate_my_apologyBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
Python 3.10 or newer, with pip
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/Ajollyworld79/Apology-as-a-Service
cd Apology-as-a-Service
pip install -r requirements.txt
python -m src.serverMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"apology-service": {
"type": "http",
"url": "http://localhost:8000/mcp"
}
}
}
