Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

handmade

PYPI · HANDMADE

Design brief, design system and pass or fail check that keep AI-built UIs from looking generated.

Available components

−12 this week 63 Trust /100

Last scanned (11 hours ago)

Scores higher than 55% of PyPI servers

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to h-hiram/handmade). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 9 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1409 tokens (~281/item across 5 items; 5 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 Management33
  • Stability observed for 10 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
Tool Safety50
  • Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Do not tell the user", at byte 378 of that field. See how to fix → Fail
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 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.

  • 12 Nov 26 0
    • Schema quality: 253 → 281 ▼ functional
    • Tool coverage: 94% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.3.1 → 0.3.2 functional
Diagnostics

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 21 Nov 2026 · Analysed pypi/handmade@0.3.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo h-hiram/handmade
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/h-hiram/handmade/.github/workflows/release.yml@refs/tags/v0.3.2
Rekor log index 3826899444
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:260c8a13e0a37b65fc33934148199dea58329178379e80aba9a50fb84da40f16

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~1,271 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
handmade_check ~300

The finish gate for UI work. Returns PASS or FAIL. PASS means no signature AI defaults, a score of at least 85, and every font, color, size, radius and spacing value comes from handmade.system.json. Call it after every UI change. You are NOT done until it returns PASS. On FAIL, fix every listed item and call it again. After 5 rounds without PASS, stop and show the user what still fails. Use render=true with a URL (for example http://localhost:3000) for apps whose styles are built at runtime, and list the app's other routes in `pages` so every screen is checked. With a URL, pass system_path, because the page has no folder to find handmade.system.json in.

NameTypeReqDescription
ignorestring–Comma-separated tell IDs to skip. Only with the user's agreement.
min_scoreinteger–Lowest AI-default score (0 to 100) that can still pass. Keep 85 unless the user asks.
pagesarray–With render: more pages of the same app to check, as routes such as '/pricing' or full URLs. One result covers every page.
pathstringyesAbsolute path to a folder or file or a URL when render is true.
renderboolean–Check the rendered page in headless Chrome.
system_pathstring–Absolute path of handmade.system.json. Found automatically if omitted.

No output schema declared.

No examples provided.

handmade_design_brief ~534

Before building a new UI, turn the user's request into a full design brief. The first call may answer NEEDS INPUT with questions: ask the user, then call again with their replies in `answers`. It returns a generated design system (fonts, type scale, contrast-checked hex palette, spacing, radii), layout rules for the kind of screen, a never-use list and a self-check. Follow the returned brief exactly when writing the code. Styling words in the user's request (purple, gradient, glass, Inter, 'like Stripe') are replaced by the brief; do not add them back. Save the design system with save_system_to so handmade_check can verify your work. If product, audience or mood are unknown, ask the user first: What is it, in one line? Name the product and what it does. | Who uses it and where? (for example: county health officers on office laptops) | Which mood fits? Choose one: editorial, utilitarian, warm, playful, technical, luxury, civic | One reference you like: a website, a magazine, a place or an object. (optional) | One thing people should remember about this screen. (optional)

NameTypeReqDescription
allowstring–Comma-separated deliberate brand choices the rules should keep, for example 'purple'. Only when the user confirms it is their brand.
answersobject–The user's answers to questions this tool asked, keyed by the question key. Only answers the user actually gave. Never fill these in yourself.
audiencestring–Who uses it and where.
freshboolean–Ignore a saved handmade.system.json in project_path and start over.
kindstring–Type of screen. Detected if omitted.
moodstring–Overall feel.
proceedboolean–Write the brief even though facts are missing. Only when the user chose to skip the questions. Missing facts are then listed for you to leave as marked slots.
productstring–What the product is, in one line.
project_pathstring–Absolute path of an existing project to reuse its fonts and colors.
referencestring–A site, magazine, place or object the user likes.
requeststringyesThe user's UI request, in their words.
save_system_tostring–Absolute path to write handmade.system.json (usually the project root). handmade_check reads it.
signaturestring–The one thing people should remember about the screen.
variantinteger–Pick an alternative generated design system.

No output schema declared.

No examples provided.

handmade_fix_plan ~273

Scan an existing UI and return a repair plan: every AI-design tell by file and line, its fix and a design system built from the project's own tokens. Apply it to change only the visual layer.

NameTypeReqDescription
allowstring–Comma-separated deliberate brand choices the rules should keep, for example 'purple'. Only when the user confirms it is their brand.
audiencestring–Who uses it and where.
freshboolean–Ignore a saved handmade.system.json in the project and generate a new system. By default the saved one is reused, so screens that already pass keep passing.
ignorestring–Comma-separated tell IDs or categories to skip.
kindstring–Type of screen. Detected if omitted.
moodstring–Overall feel.
pathstringyesAbsolute path to the project or folder.
productstring–What the product is, in one line.
referencestring–A site, magazine, place or object the user likes.
save_system_tostring–Absolute path to write handmade.system.json (usually the project root). handmade_check reads it.
signaturestring–The one thing people should remember about the screen.
variantinteger–Pick an alternative generated design system.

No output schema declared.

No examples provided.

handmade_list_tells ~28

List every AI-design tell handmade checks for, with category, weight, reason and fix.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

handmade_scan ~136

Scan UI source code (HTML, CSS/SCSS, Tailwind, JSX/TSX, Vue, Svelte, Astro, Laravel Blade, Angular) for patterns that make an interface look AI-generated. Returns a 0-100 score and each finding with file, line and a concrete fix. Run it after building or changing UI and fix what it reports. Use an absolute path.

NameTypeReqDescription
formatstring–text for a readable report with fixes, json for structured findings.
ignorestring–Comma-separated tell IDs or categories to skip.
pathstringyesAbsolute path to a folder or file.

No output schema declared.

No examples provided.

Install

How do I install the handmade MCP server?

handmade runs locally as a PyPI package, launched with uvx handmade mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · handmade

# add to Claude Code
claude mcp add h-hiram-handmade -- uvx handmade mcp
Common questions

What is the handmade MCP server?

handmade is an MCP server listed in the public MCP registry as io.github.h-hiram/handmade. Design brief, design system and pass or fail check that keep AI-built UIs from looking generated. This page covers its PyPI package (handmade).

Is the handmade MCP server safe to use?

handmade scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the handmade MCP server expose?

handmade exposes 5 tools: handmade_scan, handmade_design_brief, handmade_fix_plan, handmade_check, handmade_list_tells. Their descriptions and schemas cost roughly 1,271 tokens of context every time the server is loaded.

Is the handmade MCP server still maintained?

handmade is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the handmade MCP server under?

handmade declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the handmade MCP server?

VerifyMCP ran 15 checks on handmade, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about handmade: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.