Standout
REMOTE · STANDOUTMCP.IO · SCANNED AUG 3
Anti-slop design taste for AI coding agents: art directions, section code, 0-100 page critic.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 30 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5705 tokens (~190/item across 30 items; 30 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · standoutmcp.io
claude mcp add --transport http io-standoutmcp-standout https://standoutmcp.io/api/mcp
[mcp_servers.io-standoutmcp-standout] url = "https://standoutmcp.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-standoutmcp-standout": {
"type": "remote",
"url": "https://standoutmcp.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add io-standoutmcp-standout --url https://standoutmcp.io/api/mcp --transport streamable-http
mcp_servers:
io-standoutmcp-standout:
url: "https://standoutmcp.io/api/mcp" {
"mcpServers": {
"io-standoutmcp-standout": {
"type": "http",
"url": "https://standoutmcp.io/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://standoutmcp.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=standoutmcp.io | CN=YR2,O=Let's Encrypt,C=US | 11 Jun 2026 | 9 Sept 2026 | RSA 2048 | SHA256-RSA | 671573ba577623389df861d81143480c5ea |
| SANs: standoutmcp.io | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC secure
Validation of standoutmcp.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| standoutmcp.io. | present | 2371 | 13 | Verified |
| standoutmcp.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; form-action 'self'; script-src 'self' 'unsafe-inline' https://cdn.paddle.com https://public.profitwell.com https://va.vercel-scripts.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.paddle.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: blob: https:; connect-src 'self' https://*.paddle.com https://api.resend.com https://*.profitwell.com; frame-src 'self' https://*.paddle.com; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://standoutmcp.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://standoutmcp.io/api/mcp | HTTPS enforced | 308 | https://standoutmcp.io/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
assemble_premium_page ~207
Assemble a coherent premium build kit from Standout-original primitives: type scale, spacing rhythm, hero background, card/surface, dial or metric, section transition, text motion, and proof/pricing. Use before building a luxury/high-end/Framer-like page so the agent has real components instead of generic advice.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Site category or type, e.g. saas, church, ecommerce, agency |
| direction | string | — | Standout direction id, e.g. aurora-glass or porcelain-atelier |
| intensity | string | — | Motion/visual intensity |
| query | string | — | Full brief, e.g. 'luxury light website with soft wavy hero animation and 3D dials' |
| response_format | string | — | Return markdown or structured JSON |
| site_type | string | — | Finer site type, e.g. church, mcp, saas, portfolio |
| tone | string | — | Tone constraint |
No output schema declared.
No examples provided.
build_from_reference ~339
Reference-first build — 'show me what you like, I'll build it.' Give a reference you LIKE (a public site URL via reference_url, and/or a curated library id via reference_id from search_references) plus what YOU are building, and get back a matching StandOut direction, a reference-backed build plan, and the next call for section code. This is the front door for building from an EXAMPLE instead of a text brief: Standout reads the URL server-side for its semantic signal (title, headings, copy) and folds it into the direction match. Note: pixel-level palette/type extraction from an image is not yet supported (that is the Phase 2 vision pass) — for now it matches on the page's text/structure plus the curated library. Pass reference_id to anchor on an exact curated reference.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | — | Who the page must convince |
| business | string | yes | What YOU are building (not the reference), e.g. 'booking site for a Fiji dive shop' |
| direction | string | — | Optional StandOut direction id to force, e.g. terminal-grade |
| industry | string | — | Industry or category, e.g. developer tool, restaurant, law firm |
| reference_id | string | — | Or a curated reference id from search_references to anchor the match on |
| reference_url | string | — | Public URL of a site whose style you like. Standout reads it server-side for its semantic signal. |
| response_format | string | — | Return markdown or structured JSON |
| vibe | string | — | Desired feel, e.g. premium, technical, warm, playful |
No output schema declared.
No examples provided.
build_from_reference_v2 ~287
Reference Intelligence Layer — build from a site you like without cloning it. Pass a public reference_url plus what YOU are building and optional favorite_bits such as 'hero animation', 'pricing card', or 'color mood'. Standout captures server-readable HTML/CSS signals, extracts Reference DNA, names what to borrow, names what to avoid, gives a similarity-risk guardrail, then returns a reference-backed original build direction. This is the right tool when the user says 'I like this site but don't want to steal it.'
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | — | Who the page must convince |
| business | string | yes | What YOU are building (not the reference), e.g. 'Mac app that makes websites and PDFs readable outside' |
| direction | string | — | Optional StandOut direction id to force, e.g. terminal-grade |
| favorite_bits | array | — | Specific parts the user likes, e.g. ['hero animation', 'warm colors', 'pricing card']. These become inspiration tokens, not copied components. |
| industry | string | — | Industry or category, e.g. developer tool, Mac utility, restaurant |
| reference_url | string | yes | Public URL of a site whose style or specific parts you like |
| response_format | string | — | Return markdown or structured JSON |
| vibe | string | — | Desired feel, e.g. premium, technical, warm, playful |
No output schema declared.
No examples provided.
client_report ~266
Generate a CLIENT-READY design audit report for an agency to send to its client: a Standout Score, what's holding the page back, what to fix and why it matters, a client-safe summary, and the page screenshots — all in plain language with NO internal jargon. Pass url for the current page; optionally pass after_url (or after_source) for a rebuilt version to get a true before/after with both screenshots and the score improvement. Pass agency_name to WHITE-LABEL it: the report text and the shareable public report page both read 'Prepared by {agency}', ready to send to the client as your own.
| Name | Type | Req | Description |
|---|---|---|---|
| after_source | string | — | Raw HTML/CSS of the rebuilt page, for a before/after comparison |
| after_url | string | — | The rebuilt (after) page URL, for a before/after comparison |
| agency_name | string | — | White-label: your agency/studio name, shown as 'Prepared by X' in the report and on the shareable report page |
| business | string | — | Business name/description for the report header and classification |
| source | string | — | Raw HTML/CSS of the current page, if not published |
| url | string | — | The current (before) page URL to audit |
No output schema declared.
No examples provided.
critique_design ~223
Brutal, specific design critique of an existing page: automatic AI-slop detection (banned gradients, centered-hero defaults, h-screen bugs, cliche copy) plus a prioritized fix list with exact values. When you pass a URL, the response also includes LIVE SCREENSHOTS of the rendered page at phone (390px) and desktop (1440px) widths — look at them and fix what fails visually — and saves an unlisted SHAREABLE SCORE REPORT (score + category breakdown + screenshots) whose link you should give to the user. Always prefer passing the published URL over raw source for these reasons.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | Description of the current design if no source available |
| direction | string | — | Direction pack id the page implements (e.g. ink-and-paper). ALWAYS pass this when the page was built from get_design_direction so the critique respects the design system instead of fighting it. |
| source | string | — | Raw HTML/CSS/JSX of the page |
| url | string | — | Public URL of the page to critique |
No output schema declared.
No examples provided.
critique_similarity ~149
Originality guardrail — compare a built page/source/description against a reference site and flag shared recognizable fingerprints. Use after build_from_reference_v2, before showing or publishing, to avoid producing a design that is visually too close to the inspiration.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_description | string | — | Plain-language description of the built design if source is unavailable |
| candidate_source | string | — | Built page HTML/CSS/JSX to compare against the reference |
| favorite_bits | array | — | The same favorite bits passed to build_from_reference_v2, if any |
| reference_url | string | yes | Public URL of the reference site the user liked |
| response_format | string | — | Return markdown or structured JSON |
No output schema declared.
No examples provided.
critique_ui ~217
Deterministic critique for APPLICATION UI (dashboards, admin panels, SaaS views): runs the app-UI slop rulebook against React/JSX/HTML source (radius chaos, card-in-card, gray-on-gray text, raw palette classes, missing empty/loading/error states, clickable divs, killed focus rings) and, when a Standout app theme is installed, a theme-conformance pass (foreign colors, missing semantic token classes). Returns a 0-100 UI score with a ship verdict and a prioritized fix list. Use after building every view; re-run until the score clears 85. For marketing/landing PAGES use critique_design instead.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | The component or screen source to critique (React/JSX/TSX/HTML/CSS) |
| theme | string | — | Installed app theme id (e.g. graphite-ledger) to also check token-law conformance |
| view | string | — | What this view is, e.g. 'invoices table', for context |
No output schema declared.
No examples provided.
get_app_theme ~202
Get a LOCKED design-token system for application UI (dashboards, admin panels, SaaS tools): every color role contrast-checked, exactly two radii, a five-step type scale, spacing, elevation and motion tokens, plus a Tailwind v4 semantic mapping, the theme's usage law, and the app-UI slop rulebook. This is how a vibe-coded app stops looking AI-generated: install the theme once and every view the agent builds matches. Call with NO theme to browse the menu (free); call with a theme id to receive the full system. Themes share brand DNA with the website directions, so a client's site and app stay on one identity.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | — | Menu format when browsing: markdown (default) or JSON |
| theme | string | — | Theme id from the menu, e.g. graphite-ledger, terminal-grade-ui, porcelain-ui. Omit to browse the menu (unmetered). |
No output schema declared.
No examples provided.
get_asset_pack ~79
Ready-to-paste CSS for a direction: custom properties (palette + fonts), button/card/nav treatments, grain texture, Google Fonts import, and the matched motion recipe list.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | — | Direction pack id (e.g. terminal-grade) |
| query | string | — | Or describe the business/vibe and the best pack is chosen |
No output schema declared.
No examples provided.
get_component_code ~163
Get FINISHED application-UI components (React + Tailwind, zero dependencies) written against a Standout app theme's semantic tokens: app shell with sidebar/topbar, stat row with mono tabular metrics, data table with layout-matched loading skeletons + instructive empty state + inline retryable error, and a settings form with inline validation, sticky save bar and a two-step danger zone. States are built in, so the agent wires data and content instead of inventing structure. Install the theme first via get_app_theme.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | — | Component id: app-shell, stat-row, data-table, settings-form, or 'all' (default) |
| theme | string | — | App theme id the components bind to (default graphite-ledger) |
No output schema declared.
No examples provided.
get_design_direction ~448
Get a complete, distinctive, reference-backed art direction for a website: palette with exact hex roles, type pairing, layout DNA, hero spec, component treatments, imagery rules, matched motion recipes, and public-product reference evidence. Use FIRST, before building, so the site has a coherent direction instead of defaults. The catalog holds 14 directions: 9 with light base palettes and 5 dark — pass tone to constrain. If you only know the business name, call it anyway: the response will give you a few quick questions to ask the user, then call again with their answers as vibe/audience. REDESIGNS: if the business has an existing website, pass its URL as current_site_url — Standout fetches it server-side and returns a content inventory (services, prices, hours, contacts) plus a redesign protocol, so no questions are needed.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | — | Who the site must convince |
| boldness | string | — | How adventurous the signature concept should be: safe (conservative/trust-first businesses like clinics, accountants, law firms), elevated (default), bold, or experimental. A 'safe' request never rec… |
| business | string | — | What the business is, e.g. 'dive shop in Fiji running charters'. If omitted, the response returns a few quick intake questions to ask the user instead of erroring. |
| current_site_url | string | — | The business's EXISTING website URL, for redesigns. Standout fetches it and returns the content to preserve + the redesign protocol |
| industry | string | — | Industry, e.g. restaurant, law firm, saas, gym |
| tone | string | — | Base palette tone. Pass when the client asks for a light or dark site; matching stays inside that pool (9 light / 5 dark directions) |
| vibe | string | — | Desired feel, e.g. premium, playful, technical, warm |
No output schema declared.
No examples provided.
get_flow ~66
Get the full step-by-step payload for one user journey: problem, steps, user actions, system responses, related direction ids, and agent implementation notes.
| Name | Type | Req | Description |
|---|---|---|---|
| flow_id | string | yes | Flow id from search_flows |
| response_format | string | — | Return markdown or structured JSON |
No output schema declared.
No examples provided.
get_free_trial_key ~86
Self-provision a free Standout trial key (25 calls, no signup) without leaving the conversation. Call this when no license key is configured or your Standout calls return a license error. Returns the key plus the exact reconnect instructions to hand your user. Free and unmetered; issuance is capped per network, so never call it when you already have a working key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_hero_concept ~81
Get a complete hero section concept: headline + subline copy (no marketing cliches), CTA labels, exact background treatment, and copy-paste ambient motion CSS matched to the design direction.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business this hero sells |
| direction | string | — | Direction pack id from get_design_direction (e.g. coastal-film) |
No output schema declared.
No examples provided.
get_motion_recipes ~182
Production-ready motion for any stack: CSS/vanilla-JS recipes (staggered entrances, scroll reveals, marquees, grain, parallax) PLUS finished shader-grade ambient pieces - WebGL gradient mesh, image ripple displacement, live halftone, velocity-reactive type rail, scroll-scrubbed zoom portal - palette-keyed to Standout directions. Request by ids or describe what you need; pass direction for palette-filled shader code.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | — | Direction pack id (e.g. coastal-film); fills shader piece palettes with the pack's hexes |
| ids | array | — | Recipe or piece ids, e.g. ['gradient-mesh-flow','fade-rise-stagger'] |
| query | string | — | Or describe the desired motion, e.g. 'webgl hero shader' or 'premium dark portfolio hovers' |
No output schema declared.
No examples provided.
get_premium_components ~251
Standout-original premium primitives: luxury hero backgrounds, Framer-style dials/gauges, shader/glass cards, soft section transitions, proof rails, pricing plates, and headline motion. Returns copy-paste HTML/CSS/vanilla JS snippets with reduced-motion fallbacks. Use when the user asks for premium, luxury, beautiful, wavy, Framer-like, glass, 3D controls, or high-end motion.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Site category or type, e.g. saas, church, ecommerce, agency |
| direction | string | — | Standout direction id, e.g. aurora-glass or porcelain-atelier |
| intensity | string | — | Motion/visual intensity |
| limit | integer | — | Number of primitives to return, max 12 |
| query | string | — | Desired feel/components, e.g. 'light luxury wavy Framer dials' |
| response_format | string | — | Return markdown or structured JSON |
| site_type | string | — | Finer site type, e.g. church, mcp, saas, portfolio |
| tone | string | — | Tone constraint |
| type | string | — | Optional primitive type filter |
No output schema declared.
No examples provided.
get_reference ~76
Get the full structured payload for one reference: source URL, categories, tags, colors, typography, layout pattern, component rules, imagery, motion, do/don't constraints, and agent implementation notes.
| Name | Type | Req | Description |
|---|---|---|---|
| reference_id | string | yes | Reference id from search_references |
| response_format | string | — | Return markdown or structured JSON |
No output schema declared.
No examples provided.
get_section_code ~254
Finished, art-directed HTML/CSS page sections for a design direction: nav, hero, offer, image band, story, and footer — composed by a designer, seeded to this business (accent + expression already applied). Use AFTER get_design_direction: assemble the sections and replace only the content (copy + images), never the composition. This is what makes the result look like a $10k site instead of a template.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business, e.g. 'barbershop in Suva' - seeds the expression so same-direction sites stay distinct |
| direction | string | — | Direction pack id from get_design_direction (e.g. ink-and-paper, harvest-table, aurora-glass) |
| sections | array | — | Optional filter: section ids or kinds (nav, hero, offer, imageband, story, footer). Omit for the full set |
| signature_move | string | — | The signature move id from get_design_direction's Signature Concept (e.g. editorial_dossier, field_report_layout). Pass it so the sections are ORDERED and FRAMED to that concept - the output then lea… |
No output schema declared.
No examples provided.
get_showpiece ~228
The tier ABOVE the design directions: finished showpiece skeletons for scene-led, art-directed pages - world hero with environment bleed, VIDEO world hero (looping cinematic clip + liquid-glass chrome + word-by-word blur reveals), type-scene interlock (mega type behind a cutout subject), monochrome flood, scene-pinned glass annotations, ghost mega-type band - each with the scene/video-generation prompts that make the world bespoke to THIS business, contrast scrims, mobile behavior and reduced-motion built in. Call with no technique to browse the menu (free); call with a technique id for the full skeleton. Use when the brief says wow, cinematic, premium beyond a normal landing page.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | — | Direction pack id (e.g. coastal-film); fills the skeleton and scene prompts with the pack's hexes |
| technique | string | — | Skeleton id: world-hero, video-world-hero, type-interlock-hero, monochrome-flood-hero, annotation-scene, ghost-type-band. Omit to browse the menu (unmetered). |
No output schema declared.
No examples provided.
get_similar_references ~89
Find references similar to a known reference by shared tags, categories, use cases, and StandOut direction ids. Use after finding one strong reference to broaden the evidence set.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Number of similar references to return, max 12 |
| reference_id | string | yes | Reference id from search_references |
| response_format | string | — | Return markdown or structured JSON |
No output schema declared.
No examples provided.
list_directions ~175
Browse the full 'pick a vibe' menu: all 14 named art directions (9 light-base, 5 dark-base) with their taglines, vibe tags, and what each is best for. Use when the user wants to SEE the available directions and choose one themselves, rather than have get_design_direction auto-pick from the business. Pick an id from the menu and pass it as the `direction` argument to get_section_code, get_asset_pack, get_hero_concept, or synthesize_direction_from_references. Browsing the menu does not consume a metered call.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | — | Return a human-skimmable markdown menu (default) or a structured JSON array |
| tone | string | — | Optionally show only light-base (9) or dark-base (5) directions |
No output schema declared.
No examples provided.
list_watches ~29
List this license's active site watches with their last known scores and check times. Unmetered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
make_it_standout ~226
Detailed transformation plan for power users. For the complete inspect, fix, rerender, and client-proof workflow, prefer polish_and_prove. This tool classifies and scores a site, returns exact fix patches, chooses a creative spine and direction, and emits a paste-ready implementation prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | — | Who the site must convince |
| business | string | — | What the business is, e.g. 'MCP server that gives AI agents design taste'. Used to classify and build from scratch when no url/source. |
| goal | string | — | The primary conversion goal, e.g. 'get users to run an audit and connect the MCP' |
| reference | string | — | A reference site URL or curated reference id whose style to lean toward |
| source | string | — | Raw HTML/CSS/JSX, when the page is not yet published |
| url | string | — | Public URL to audit and improve (best input — enables the live score + screenshots) |
| vibe | string | — | Desired feel, e.g. premium, technical, warm |
No output schema declared.
No examples provided.
polish_and_prove ~333
THE PRIMARY STANDOUT WORKFLOW. Use this when a user wants an AI-built website made client-ready without choosing individual design tools. First call: pass url (best), source, or business. Standout captures the baseline, scores the real phone and desktop render, chooses a coherent direction, and returns the exact implementation contract for the coding agent. The agent MUST apply the fixes in the repository. Final call: pass the original url/source plus after_url/after_source. Standout compares both versions and produces a client-safe before-and-after report and share link. Do not stop after returning advice; the completed outcome is fix, rerender, prove.
| Name | Type | Req | Description |
|---|---|---|---|
| after_source | string | — | Improved page source for proof mode when there is no public preview URL. |
| after_url | string | — | Improved public page URL. Supplying this switches the workflow to proof mode and compares before vs after. |
| agency_name | string | — | Optional agency/studio name for the final client proof report. |
| audience | string | — | Who the page must convince. |
| business | string | — | What the business is and what the page sells. |
| goal | string | — | The primary conversion goal. |
| reference | string | — | Optional approved reference URL or curated reference id. |
| source | string | — | Original/current HTML, CSS, JSX, or TSX when the page is not public. |
| url | string | — | Original or current public page URL. Best first-call input because it enables live phone and desktop rendering. |
| vibe | string | — | Optional visual steer, e.g. premium, light, editorial, technical. |
No output schema declared.
No examples provided.
search_flows ~144
Search reference-backed user journeys such as API key onboarding, pricing selection, hospitality booking, marketplace search, quickstart activation, and portfolio inquiry. Use when the page is part of a multi-step task, not just a visual screen.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Optional category filter, e.g. onboarding, pricing, booking |
| direction | string | — | Optional StandOut direction id |
| limit | integer | — | Number of flows to return, max 12 |
| query | string | — | Search terms like 'api key onboarding', 'pricing', 'booking', 'marketplace', or 'quickstart' |
| response_format | string | — | Return markdown or structured JSON |
No output schema declared.
No examples provided.
search_references ~180
Search Standout's curated reference library: real public-product style, screen, and component patterns with source URLs, color roles, layout notes, component rules, do/don't constraints, and agent implementation notes. Use before or during a build when you need evidence-backed visual patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Optional category filter, e.g. pricing, onboarding, developer tool, restaurant |
| direction | string | — | Optional StandOut direction id, e.g. terminal-grade, coastal-film, harvest-table |
| limit | integer | — | Number of references to return, max 12 |
| query | string | — | Search terms like 'developer tool pricing', 'api key dashboard', 'restaurant booking', or 'dark command center' |
| response_format | string | — | Return markdown or structured JSON |
| type | string | — | Optional reference type filter |
No output schema declared.
No examples provided.
synthesize_direction_from_references ~206
Turn a business brief plus optional reference ids into a reference-backed build direction. Returns the chosen StandOut direction, matching public-product references, relevant flow patterns, a synthesized build plan, implementation lock, and next tool calls. Use when you want the agent to build from evidence instead of vibes.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | — | Who the page must convince |
| business | string | yes | What the website/app is for |
| direction | string | — | Optional StandOut direction id to force, e.g. terminal-grade |
| industry | string | — | Industry or category, e.g. developer tool, restaurant, law firm |
| query | string | — | Optional reference search query. Defaults to business/industry/vibe/audience |
| reference_ids | array | — | Optional exact reference ids from search_references |
| response_format | string | — | Return markdown or structured JSON |
| vibe | string | — | Desired feel, e.g. premium, technical, warm, playful |
No output schema declared.
No examples provided.
unlock_bonus_calls ~118
Unlock 10 bonus calls on this trial key, one time only, in exchange for the user's email address. Call this when the trial limit is reached and the USER has chosen the free-bonus option and given you their email in this conversation. NEVER guess, invent, or reuse an email the user did not explicitly provide for this. The key on this connection is upgraded in place, nothing to reconfigure. Free and unmetered.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email address, exactly as the user gave it in this conversation |
No output schema declared.
No examples provided.
unwatch_site ~45
Stop watching a site's design score. Pass the same URL that was given to watch_site. Unmetered.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The watched page address to stop watching |
No output schema declared.
No examples provided.
watch_site ~129
Watch a live site's design score (Pro). Standout re-audits the URL about once a day and emails an alert when the design regresses: a drop of more than 5 points, or falling below the 85 client-ready bar. Use it right after shipping a client site so a broken deploy is caught before the client sees it. Up to 10 active watches per license.
| Name | Type | Req | Description |
|---|---|---|---|
| string | — | Where regression alerts go. Defaults to the email bound to this license. | |
| url | string | yes | Full public page address to watch, e.g. https://client-site.com |
No output schema declared.
No examples provided.