Corporate Satire MCP server

@pipeworx/corporate-satire

Comedy generator: turns a plain announcement into a fabricated, satirical corporate statement in the shape of a company news bulletin. Everything it returns is invented for entertainment — the spokesperson quote, the boilerplate, the media contact, the stakeholders_aligned count. For real wire-service announcements use globenewswire, prnewswire or einpresswire; for company filings use edgar.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

returns pressrelease (the upstream's field name: title, body, boilerplate, media contact as one text block) plus joke metadata: actualnewsvalue, quotesaidby, workshopsthisrequired, monthsinplanning, stakeholdersaligned, presspickupprobability, originalthing / newthing. tone is one of visionary, disrupting, humbled, transparent, pivoting.

• corporatesatiregenerate(announcement, company?, tone?, location?) —

Auth

Keyless. The endpoint answers a bare request (verified 2026-09-21, HTTP 200 with no X-API-Key). Earlier versions of this pack shipped a literal key in source; it was removed in fleet #2287 because the upstream does not need it.

Data sources

GET with announcement, company, tone, location as query params.

• — the generator.

(apiofthe_day, tool schemas).

• — the catalogue of StupidAPIs endpoints

History

Renamed from press-release / pressreleasegenerate on 2026-09-21 (fleet #2287). The old name was the #1 searchpacks hit for "latest press release from " and handed that query to a joke generator. A first attempt at satire-press-release still ranked #1: searchpacks scores a slug hit at +15 per query token, so any slug carrying "press" and "release" beats the real wire packs by construction. Hence a slug with neither word. Both old gateway paths (/press-release/mcp, /satire-press-release/mcp) still resolve to this pack via RENAMEDPACKSLUGS in the gateway, because the npm package and MCP Registry entry published under the original name point at the first.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "corporate-satire": {
      "url": "https://gateway.pipeworx.io/corporate-satire/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/corporate-satire/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, 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 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

Shortened. The full README is on GitHub.