Koskamo

Pipeworx Passive Aggression MCP

Document v2 · published by Koskamo · updated 2026-10-12

Original source

This MCP server, operated by Pipeworx, provides a tool to analyze text for passive-aggressive language. It returns a severity score from 0-100, flags specific phrases with explanations, translates the subtext into plain English, and suggests direct responses. It is a free tier service with a limit of 50 calls per day, designed for entertainment or communication analysis purposes.

  • Operator: Pipeworx
  • Endpoint: https://gateway.pipeworx.io/passive-aggression/mcp
  • Transport: streamable-http
  • Sign-in: No sign-in
  • Category: Productivity and knowledge
  • Use cases: Analyze text for passive-aggressive language; Get severity score (0-100) of detected aggression; Translate subtext into plain English; Receive suggested direct responses
  • Tools: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, search_within, deep_research, discover_tools, resolve_entity, compare_entities, subscribe, unsubscribe, list_subscriptions, recent_alerts, entity_profile, recent_changes, validate_claim, company_facts, scan_dependency, bet_research, polymarket_arbitrage, polymarket_edges, polymarket_kalshi_spread, polymarket_fill_risk, polymarket_edge_tracker, kalshi_weather_edge, resolution_audit, resolution_diff, release_calendar_markets, archive_evidence, archive_compare, research_row, classify_row, pipeworx_trending, suggest_questions, generate_llms_txt, ai_visibility_check, scan_competitor_ai_presence, pipeworx_feedback, remember, recall, forget, passive_aggression_detect
  • Documentation: https://pipeworx.io/packs/passive-aggression
  • Directory listing: https://koskamo.com/explore/pipeworx-passive-aggression-mcp
  • Also known as: Pipeworx Passive Aggression MCP MCP; pipeworx-passive-aggression-mcp

Source and provenance

Original source
pipeworx.io
Published on Koskamo by
Koskamo
Citation version
Document v2
Reuse
Check the original source’s reuse terms.

This record mirrors the MCP server directory listing and updates when the listing changes. To correct it, suggest an edit on the listing.

Version history

  1. Synced from the directory

    Version 2

  2. Synced from the directory

    Version 1