Send That Email
Server Details
send-that-email MCP — wraps StupidAPIs (keyless — no credential needed)
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 33.9% over 37 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-send-that-email
- GitHub Stars
- 1
- Server Listing
- mcp-send-that-email
TDQS
Scored across 32 tools
Several tool families have overlapping boundaries: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded (beta is explicitly identical today), deep_research vs ask_pipeworx, ai_visibility_check vs scan_competitor_ai_presence, and the large polymarket_* cluster (edges, arbitrage, bet_research, edge_tracker, fill_risk). The descriptions do an unusually good job of steering between them ('PREFER OVER', 'START HERE', 'follow up with'), which lifts it above a 2, but the set still contains multiple pairs an agent could reasonably misselect.
Everything is lower snake_case, so casing is consistent, but the naming style is mixed: verb_noun (list_subscriptions, resolve_entity, validate_claim, generate_llms_txt, discover_tools) coexists with bare noun phrases (entity_profile, recent_changes, recent_alerts, polymarket_edges) and vague names (recent_alerts vs recent_changes vs list_subscriptions are easily confused). Readable, but no single predictable pattern.
32 tools is above the 25+ threshold for 'too many', and the surface mixes a broad Pipeworx data gateway with memory, subscriptions, and a lone email analyzer, making the set feel like several products stapled together. A tighter grouping (or splitting the email tool from the Pipeworx suite) would reduce the selection burden.
The server is named 'Send That Email' but has exactly one email tool (send_that_email_analyze) — analysis only, no send/draft/read/list — so the named domain is a dead end. The rest of the surface is a mislabeled general Pipeworx gateway whose coverage is broad but lacks direct CRUD/lifecycle operations for any single domain.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
1 tool update
- Changed
entity_profile3 fields changed- changed
Input schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon." - changed
Input schema / properties / type / enumPrevious value: -[ - "company" -]New value: +[ + "company", + "ticker" +] - changed
Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
1 tool update
- Changed
resolve_entity1 field changed- changed
Input schema / properties / value / descriptionPrevious value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."
Related MCP Connectors
could-have-been-email MCP — wraps StupidAPIs (keyless — no credential needed)
ship-on-friday MCP — wraps StupidAPIs (keyless — no credential needed)
buzzword-density MCP — wraps StupidAPIs (keyless — no credential needed)
yc-rejection MCP — wraps StupidAPIs (keyless — no credential needed)
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceAuthenticated email service MCP for AI agents.191Apache 2.0
- AlicenseCqualityDmaintenanceA simple Node.js MCP (Model Context Protocol) server for sending emails using TurboSMTP3JavaScriptMIT
- AlicenseNot gradedqualityDmaintenanceEnables sending emails through the Resend service API. Provides a simple email sending tool that integrates with MCP-compatible clients.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to send emails via Cloudflare's Email Service. Provides both MCP server integration for AI tools and a REST API for traditional applications with support for HTML content, attachments, and secure authentication.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.