
Wraps the StupidAPIs excuse generator to give your AI agent a single tool: excuse_generate. It returns humorous or plausible excuses for being late, missing deadlines, or ghosting someone. Hosted by Pipeworx as a standalone MCP endpoint over streamable HTTP, requiring an X-API-Key header for authentication. You can connect directly to the excuse-only server or access it through the full Pipeworx gateway alongside 673+ other data sources. The gateway supports ask_pipeworx for plain English queries instead of direct tool calls. Reach for this when you need your agent to generate creative excuses on demand, whether for testing conversational flows or just adding some levity to automated responses.
excuse MCP — wraps StupidAPIs (requires X-API-Key)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
excuse_generate | Generate an excuse for a given situation (late/missed_deadline/ghosted), tailored to the target audience (boss/friend/date/recruiter/professor/client) and quality tier (implausible/plausible/airtight/medical). Returns ready-to-use excuse text. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"excuse": {
"url": "https://gateway.pipeworx.io/excuse/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/excuse/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Excuse data" })
The gateway picks the right tool and fills the arguments automatically.
MIT