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