could_have_been_email_analyze — Could Have Been Email MCP Tool
could_have_been_email_analyze
(could have been email analyze) is one of 37 tools on the
Could Have Been Email
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call could_have_been_email_analyze from your client
- Claude Code Could Have Been Email could_have_been_email_analyze run in your project directory
- Claude Desktop Could Have Been Email could_have_been_email_analyze ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Could Have Been Email could_have_been_email_analyze ~/.cursor/mcp.json
- VS Code Could Have Been Email could_have_been_email_analyze .vscode/mcp.json
- Zed Could Have Been Email could_have_been_email_analyze ~/.config/zed/settings.json
- Windsurf Could Have Been Email could_have_been_email_analyze ~/.codeium/windsurf/mcp_config.json
- Cline Could Have Been Email could_have_been_email_analyze ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Could Have Been Email could_have_been_email_analyze ~/.gemini/settings.json
- Grok Could Have Been Email could_have_been_email_analyze .mcp.json (in your project root)
- ChatGPT Could Have Been Email could_have_been_email_analyze Settings → Connectors → Advanced → Developer mode
- Claude.ai Could Have Been Email could_have_been_email_analyze Settings → Connectors → Add custom connector
- LangChain Could Have Been Email could_have_been_email_analyze pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http could-have-been-email https://gateway.pipeworx.io/could-have-been-email/mcpOther tools on this server
- 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
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.