polish_and_prove — Standout MCP Tool
polish_and_prove
(polish and prove) is one of 30 tools on the
Standout
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call polish_and_prove from your client
- Claude Code Standout polish_and_prove run in your project directory
- Claude Desktop Standout polish_and_prove ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Standout polish_and_prove ~/.cursor/mcp.json
- VS Code Standout polish_and_prove .vscode/mcp.json
- Zed Standout polish_and_prove ~/.config/zed/settings.json
- Windsurf Standout polish_and_prove ~/.codeium/windsurf/mcp_config.json
- Cline Standout polish_and_prove ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Standout polish_and_prove ~/.gemini/settings.json
- Grok Standout polish_and_prove .mcp.json (in your project root)
- ChatGPT Standout polish_and_prove Settings → Connectors → Advanced → Developer mode
- Claude.ai Standout polish_and_prove Settings → Connectors → Add custom connector
- LangChain Standout polish_and_prove pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http standout https://standoutmcp.io/api/mcp
Other tools on this server
- get_design_direction
- list_directions
- get_app_theme
- get_component_code
- critique_ui
- critique_design
- make_it_standout
- client_report
- get_section_code
- get_hero_concept
- get_asset_pack
- get_showpiece
- get_motion_recipes
- get_premium_components
- assemble_premium_page
- search_references
- get_reference
- get_similar_references
- search_flows
- get_flow
- synthesize_direction_from_references
- build_from_reference
- build_from_reference_v2
- critique_similarity
- get_free_trial_key
- unlock_bonus_calls
- watch_site
- unwatch_site
- list_watches
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.