validate_voice — Bloody Hopes Historical Critic MCP Tool
validate_voice
(validate voice) is one of 13 tools on the
Bloody Hopes Historical Critic
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call validate_voice from your client
- Claude Code Bloody Hopes Historical Critic validate_voice run in your project directory
- Claude Desktop Bloody Hopes Historical Critic validate_voice ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Bloody Hopes Historical Critic validate_voice ~/.cursor/mcp.json
- VS Code Bloody Hopes Historical Critic validate_voice .vscode/mcp.json
- Zed Bloody Hopes Historical Critic validate_voice ~/.config/zed/settings.json
- Windsurf Bloody Hopes Historical Critic validate_voice ~/.codeium/windsurf/mcp_config.json
- Cline Bloody Hopes Historical Critic validate_voice ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Bloody Hopes Historical Critic validate_voice ~/.gemini/settings.json
- Grok Bloody Hopes Historical Critic validate_voice .mcp.json (in your project root)
- ChatGPT Bloody Hopes Historical Critic validate_voice Settings → Connectors → Advanced → Developer mode
- Claude.ai Bloody Hopes Historical Critic validate_voice Settings → Connectors → Add custom connector
- LangChain Bloody Hopes Historical Critic validate_voice pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bloodyhopes-campfire https://bloodyhopes.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.