
Wraps the StupidAPIs buzzword density analyzer to help you catch corporate jargon overload in any text. You get one tool that returns a density score, severity level, flagged terms, and total buzzword count. Flip on roast_mode for snarky feedback about your synergistic paradigm shifts. Useful for cleaning up marketing copy, checking your own writing before it ships, or auditing content that sounds like it was written by a committee. Requires an X-API-Key from StupidAPIs. Part of the Pipeworx gateway that bundles 250+ data sources, so you can connect to the full gateway instead of individual servers if you want broader access.
buzzword-density MCP — wraps StupidAPIs (requires X-API-Key)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
buzzword_density_analyze | Analyze a text passage for overused industry jargon using a tech, finance, consulting, startup, or combined dictionary. Returns buzzword count, density score (0-100), severity level, flagged terms, and an optional roast critique when roast=true. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"buzzword-density": {
"url": "https://gateway.pipeworx.io/buzzword-density/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/buzzword-density/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 Buzzword Density data" })
The gateway picks the right tool and fills the arguments automatically.
MIT