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