could-have-been-email MCP — wraps StupidAPIs (requires X-API-Key)
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-pipeworx-io-could-have-been-email": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
could-have-been-email MCP — wraps StupidAPIs (requires X-API-Key)
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
This MCP server allows Claude and other AI assistants to access your LinkedIn. Scrape LinkedIn profiles, companies and jobs, and manage your inbox.
IMAP/SMTP email MCP server — 47 tools, IMAP IDLE push, multi-account, AI triage.
Local email connectivity for AI agents — read, draft, send, and organize Outlook mail via MCP
MCP Security Weekly
Get CVE alerts and security updates for io.github.pipeworx-io/could-have-been-email and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
could-have-been-email MCP — wraps StupidAPIs (requires X-API-Key)
Part of Pipeworx — an MCP gateway connecting AI agents to 250+ live data sources.
| Tool | Description |
|---|---|
could_have_been_email_analyze | Check if a meeting transcript could have been an email instead. Returns filler word count, decisions made, action items, and a suggested email that would've replaced the meeting. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"could-have-been-email": {
"url": "https://gateway.pipeworx.io/could-have-been-email/mcp"
}
}
}
Or connect to the full Pipeworx gateway for access to all 250+ data sources:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Instead of calling tools directly, you can ask questions in plain English:
ask_pipeworx({ question: "your question about Could Have Been Email data" })
The gateway picks the right tool and fills the arguments automatically.
MIT