check_email_auth — Quiet Failures MCP Tool Read-only
check_email_auth
(check email auth) is one of 6 tools on the
Quiet Failures
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_email_auth from your client
- Claude Code Quiet Failures check_email_auth run in your project directory
- Claude Desktop Quiet Failures check_email_auth ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Quiet Failures check_email_auth ~/.cursor/mcp.json
- VS Code Quiet Failures check_email_auth .vscode/mcp.json
- Zed Quiet Failures check_email_auth ~/.config/zed/settings.json
- Windsurf Quiet Failures check_email_auth ~/.codeium/windsurf/mcp_config.json
- Cline Quiet Failures check_email_auth ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Quiet Failures check_email_auth ~/.gemini/settings.json
- Grok Quiet Failures check_email_auth .mcp.json (in your project root)
- ChatGPT Quiet Failures check_email_auth Settings → Connectors → Advanced → Developer mode
- Claude.ai Quiet Failures check_email_auth Settings → Connectors → Add custom connector
- LangChain Quiet Failures check_email_auth pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http quiet-failures https://mcp.quietfailures.com/mcpOther tools on this server
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.