Bragproof

← Reports

design-lounge-mcp

Starts with no setup0.2.7npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 3 of 4 tools tried
Contacts while installing and starting: nothing

22tools listed
0hosts contacted
40files written
1.6 sto start
109dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y design-lounge-mcp@0.2.7

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

4 tools that take no input and look read-only were called once with nothing. 3 returned a result.

search_piecesReturned a result under 0.1 s · 5,991 characters
get_iconsReturned a result under 0.1 s · 7,604 characters
search_wadaReturned a result under 0.1 s · 2,167 characters
audit_searchNo usable answer tool reported an error: Give url, path, or html.

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

start_design request, product, project_path
Call first for any new website, app, screen, or UI. Reads their request the way the method does (flow, mode, named style, calm words), ranks the recipes, reads the project folder and the recent picks, and returns the brief to fill and the steps, each naming the tool to use.
get_recipe id, product, history
A recipe (start) with its directions: each a complete look (theme, pairing, family, hero, effect, work, footer). Each direction says whether the recent history blocks it.
pick_direction recipe, product, fitting, calm, history
Apply rules 3 to 5 of Pick a direction and the Recent picks check: calm words narrow to quiet, editorial, or sharp families; the history blocks recent directions, heroes, and effects; the group check blocks two-of-three matches; the name number breaks the tie. You judge which directions fit the subject (rules 1, 2, 4) and pass them as `fitting`.
check_pick recipe, product, direction, hero, work, footer, effect, shape, frame, reuse, history
The uniqueness check from Recent picks: direction, hero, and effect against this recipe; two of hero, work, footer against the related group; hero shape against the last two; frame against the last three. Returns problems and the Unlike line for the sheet.
record_pick product, folder, recipe, direction, theme, pairing, family, hero, work, footer, effect, shape, frame, mode, fonts, colours, status
Append a line to /tmp/.design-lounge/history.jsonl: "claimed" right after you lock, "finished" after the check passes. A claimed line is read back: if another product claimed the same recipe and direction in the last hour, yours loses and the result says so.
17 more tools
search_pieces query, platform, category, style, limit, images
Search 600+ piece briefs by words (job, component, style, tag) and filters. Returns ids, summaries, and demo links. Then get_piece for the brief.
get_piece id, full, image, demo
The spec for one piece, with a picture of its demo: structure, counts, sizes, motion timing, states, hit targets, acceptance checklist. By default stops at "Optional below this line"; full=true adds the demo's exact paint and motion notes. demo=true adds the demo's HTML source, the acceptance file. Its colours and fonts are the demo's: translate them onto the locked kit.
browse_library what, mood, mode, limit
List themes, pairings, families, recipes, piece categories, collections, or kinds. Themes and pairings can be ranked by a mood ("warm craft", "editorial serif", "dark technical").
get_theme id, image
A theme's full CSS (primary, secondary, tertiary, feedback, surfaces, link) and its pair for the other mode. Colour only: fonts come from the pairing, radius and shadow from the family.
get_pairing id, image
A pairing's CSS (Google Fonts import, --font-display, --font-text, mono if any), its numbers face, and any caution to say before you write.
get_family id
A family's rules: radius, button style, density, shadow, and the sentences that lock them. The family wins over a brief for radius, shadow, button, and density.
get_icons names, group
SVG for Lounge Icons by name (24px, stroke 1.75). With no names, lists them by group. Missing names come back as missing: then follow Icon and nav in components.md, never an emoji.
search_wada query, near, limit
Sanzo Wada's 348 combinations, by colour or material word (russet, slate, "dark warm") or nearest to a hex. Only for Free colour, a brand board no theme fits, or colours they asked for. Take one line whole; the header says how to map it to roles.
read_guide file, section, outline
Read a method file or one section of it. Files: SKILL.md, app.md, brief.md, components.md, examples.md, flows.md, locale.md, native.md, practice.md, reference.md, search.md, show.md, styles.md, taste.md, website.md. Give a heading ("Look", "Write the idea", "Recent picks") to get only that section; outline=true lists the headings.
name_number name, count
The tie-break from rule 5 of Pick a direction: the sum of each letter's place in the alphabet, mod the number of fitting directions.
review_page url, path, html, kit, render, out_dir, images, format
The all-in-one check for a built page: AI giveaways and kit drift (the Look fails), SEO, AEO, GEO, and, when Chromium is available, a rendered pass at 1280×800 and 390×844 with axe accessibility, measured labels, faces, primaries, tap targets, and saved screenshots. Returns scores, fails first, each with its evidence and fix.
audit_slop url, path, html, kit, render, out_dir
Design only: the tells of a generated page (stock copy, em dashes, buzzwords, icon-card trios, gradients, the indigo palette, emoji icons, numbered eyebrows, placeholder copy, made-up numbers) and drift from the locked kit (faces, colours, radius, shadow). Static by default; render=true adds the measured checks.
audit_search url, path, html
Whether search engines can index the page and show it well (SEO), answer engines can lift a direct answer (AEO), and AI engines can reach it, read it without JavaScript, and name the entity (GEO): title, description, headings, alt, share card and its 1200×630 image, canonical, robots.txt for search and AI crawlers, sitemap, JSON-LD, question headings with short answers, server-rendered text.
suggest_schema url, path, html, type, name
JSON-LD for the page built only from facts on it: the entity (Organization, LocalBusiness subtypes, Person, Product, SoftwareApplication) with name, url, description, image, phone, email, address, sameAs; and FAQPage from its own questions. Lists the fields it could not find. Never invents ratings, reviews, or prices.
match_reference url, image_path, image, mime_type, type, corners, shadows, buttons, shape, sections
They showed a site or a screenshot and want that feel. Measures its design language (colour roles, type, corners, shadows, density, hero shape, sections, motion) and returns the closest Lounge theme, pairing, family, and pieces per section, with what does not match. Matches the feel only: never copy the reference's logo, name, words, or photos. For a screenshot, also describe the type you see (`type`) and anything else you can tell (corners, shadows, sections).
install_skill project_path, replace
The server installs the skill for this user when it starts. Use this to put it in a project as well (.claude/skills, .cursor/skills, .agents/skills), for clients that only read project skills, or with replace: true to swap a copy installed another way for this server's.
install_browser
Download the headless Chromium that review_page uses to look at the page: screenshots, axe, measured labels and buttons, and theme boards and type specimens. About 100 MB, once. Ask the person first.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Files it wrote

Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.

Install facts

LicenseSEE LICENSE IN skill/LICENSE
Needsnode >=20
Sourcegithub.com/SusanAcharya/Design-Lounge
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-2SU8Mhg4YKyOHUqRy0X2NA2dn8BnKcdd1yJ2qxPwxEB/KXmAk15QsAlfXcpeu7WLsbwx9VmVc0qpoTdlayRS0Q==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/design-lounge-mcp.svg)](https://bragproof.smaverk.com/r/design-lounge-mcp)

New version out? Ask for a fresh report.