Everything here was measured by our prober or read from a registry. Nothing is self-reported.
30-day availability1/1 checks ok
30 days agotoday
Endpoints
https://mozaika.design/mcpmcp streamable http · checked on a schedule
Registry facts
Not distributed through a package registry we index.
when
check
result
http
latency
detail
2 h ago
mcp initialize
ok
200
28 ms
server mozaika 1.29.1 · protocol 2025-06-18 · 23 tools
Tools observed via MCP handshake
search_screens — Search real product UI screens for design reference.
Use this BEFORE designing any page/component so your output matches how the
best-designed products
get_screen_sections — List the distinct sections of a page (hero, pricing cards, testimonial/feedback,
footer, ...) so you can emulate a specific part. Each section links back to
list_user_flows — List real product user flows (ordered screen journeys) — e.g. signup→dashboard,
browse→checkout. Use to understand how a whole journey is structured before
get_user_flow — Get one user flow with its ordered steps, each including full screen metadata and
image_url. Returns an error dict if the flow is not found.
get_screen — Get full metadata + image_url for a single screen by slug.
get_design_system — Get a product's full, LLM-verified design system so you can match its exact look.
Use this for "design like <product>" (e.g. site="Linear", "Stripe", "Figma
get_design_history — Measured design CHANGE HISTORY for a live-decoded domain — the Decode Ledger.
Token-level diffs between deep decodes over time: "radius 4px→8px", "primary h
audit_code — When the user says a screen looks generic, cheap or off and you need to know WHY —
paste the code and get numbers back. This is the one tool here that reads
validate_design — Grade YOUR design values against the measured corpus (hundreds of real products,
decoded live — not opinions). Pass whichever metrics you have; each returns
get_web_benchmark — The Measured Web — how the web is ACTUALLY designed, measured live across hundreds of real
products (not opinions): the median design score, border-radius,
get_design_drift — Has this product's design system CHANGED since it was decoded — and which of its numbers
are safe to hard-code? Mozaika re-measures the most-referenced prod
list_design_changes — What actually changed in the web's design systems lately — the nightly Drift Ledger feed.
Mozaika re-measures ~100 of the most-referenced products every nig
Declared by sources
What the publisher says
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
kind ← Official MCP Registry
name ← Official MCP Registry
summary ← Official MCP Registry
version ← Official MCP Registry
description ← Official MCP Registry
homepageUrl ← Official MCP Registry
publisherName ← Official MCP Registry
Derived by Wellknown
Capabilities
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
4 h ago · declared · summary → "Measured design systems decoded from 588 real products, for coding agents."
4 h ago · declared · description → "Measured design systems decoded from 588 real products, for coding agents."
4 h ago · declared · publisherName → "design.mozaika"
4 h ago · declared · homepageUrl → "https://mozaika.design"
4 h ago · declared · version → "1.1.0"
4 h ago · declared · protocols → ["mcp"]
get_section — Get one product's specific section fully specified — its decoded spec + reference
image_url + the parent product's design tokens — in a single call. Use thi
compare_sections — See how the BEST products each solve the same section — one call, cross-product.
Use before designing any section: e.g. compare_sections("Pricing / Plans")
get_component — Get one product's UI component fully specified — its anatomy read from the LIVE DOM
(exact padding / height / border_radius / border / box_shadow / font_wei
compare_components — See how the BEST products each build the same UI atom — one call, cross-product, each
with its anatomy read from the live DOM. Use before building any compo
get_recipe — The universal BUILD-KIT fetcher — the measured spec + code to reproduce a piece of UI.
`recipe_type` selects which library across three families (all agent-
compare_recipes — See how the BEST products each build the same hard pattern — one call, cross-product.
Use before building any complex pattern: compare_recipes("Command Pale
get_product — Pull an entire product as an agent-ready build kit: the full multi-format design
system (tokens + DESIGN.md/Tailwind/CSS/JSON), every curated page, every se
list_my_design_systems — List YOUR private design systems (BYODS) — the sites you decoded into your own/your team's
scope. Each item has name + slug; pass the slug/name to get_desig
get_asset_pack — Get a ready-made AI-generated icon pack (12 consistent icons) — e.g. a house style
like 'clay-starter' / 'line-minimal-starter', or a pack generated in the
generate_asset — Generate ON-BRAND icons with AI: subjects (1-12 short nouns, e.g. ["settings gear",
"credit card"]) rendered in ONE consistent style. style_from is either a
get_score — Design Score: a 0-100 design audit MEASURED from the site's live DOM (real WCAG
contrast pairs, detected type ladder, spacing grid, forced hover states, mot
commerce.pricing
Pricing & Quotes
51%
Provide AI-powered real-time analysis and intelligence on NPM packages, including security, depend…