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