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