Standout
Design taste for AI coding agents: art directions, section code, design critique, motion recipes.
https://standoutmcp.io/api/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- standout
- Version
- 1.1.0
- Capability keys
- tools
- Tool names
- get_design_direction, list_directions, get_app_theme, get_component_code, critique_ui, critique_design, polish_and_prove, 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
Standout is the final design polish and proof layer for AI-built websites. START with polish_and_prove whenever the user asks to build, redesign, restyle, improve, or critique a website or web UI. Pass the live URL when one exists, otherwise pass source or a business brief. Follow the returned execution contract: apply the fixes in the real repository, preserve facts and working behavior, verify 390px and 1440px, then call polish_and_prove again with the improved URL or source. Do not report the work complete before the second call produces the final gate and client proof. Use specialist tools such as build_from_reference_v2, assemble_premium_page, get_premium_components, get_section_code, and critique_similarity only when the contract or user brief needs them. Treat category, output-quality, asset, originality, reduced-motion, and publish gates as blocking requirements. NO KEY? If a tool returns a license error because no key is configured, call get_free_trial_key once to self-provisi
Reported Aug 17, 2026, 05:07 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 513ms
- respondsMCP initialize · 8s limit · HTTP 200 · 815ms
- respondsMCP initialize · 8s limit · HTTP 200 · 657ms
- respondsMCP initialize · 8s limit · HTTP 200 · 419ms