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.

DesignAround

PYPI · DESIGNAROUND

Design-patent screening, design-around and drawings for US, CN and EU products.

Available components

69 Trust /100

Last scanned (3 hours ago)

Scores higher than 64% 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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 19 of 84 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 671 tokens (~95/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 28% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 5 Nov 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.

  • 3 Nov 26 +1

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

  • 1 Nov 26 +16
    • Provenance: unverified → fail ▼ security
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 0
    • Provenance: fail → unverified ▼ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.3.post1 → 0.1.4 functional
  • 30 Oct 26 51

    First indexed and scored.

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 5 Nov 2026 · Analysed pypi/designaround@0.1.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 84 packages
Packages resolved 84
Stale 7
No linked repository 12
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~553 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
case_list ~24

Free. The cases on this machine (one product each) with their status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

compare ~59

Free, local. Same-scale overlay of two versions in every view, with changed parameters, size and risk; returns the comparison sheet as an image.

NameTypeReqDescription
astringyes–
bstringyes–
case_idstringyes–

No output schema declared.

No examples provided.

decision_card ~58

Free. Where a case stands: verdict (proceed / redesign / abandon / pending), reasons from the evaluations, next steps with credits and time, and the nearest deadline.

NameTypeReqDescription
case_idstringyes–
langstring––

No output schema declared.

No examples provided.

design_around ~161

Paid. Starts the agent team in the background: a designer proposes candidates, originality and manufacturability gates check them, an isolated observer scores them against the closest prior art, and it repeats. Returns a run_id at once; follow it with run_status (runs take 10-60 minutes). depth: quick (1 round) | standard (3 rounds, default) | deep (6 rounds); standard and deep refund 50% of the spend automatically when no candidate qualifies.

NameTypeReqDescription
case_idstringyes–
depthstring––
max_creditsintegeryesHard cap for the whole run (standard default 5900).
topinteger–How many prior-art rights to design around (default 3).

No output schema declared.

No examples provided.

run_status ~54

Free. State of a background run started by design_around: status, recent progress events and, when done, the outcome (qualified candidates, where it got stuck, result guarantee refund).

NameTypeReqDescription
run_idstringyes–

No output schema declared.

No examples provided.

screen ~133

Paid. Search registered designs (US, CN, EU) for the case's product on the DesignAround server, add the candidates as prior art and rank them by silhouette locally. Quick screen 50 credits (5 free a month), deep (image + text) 350. Takes 1-3 minutes.

NameTypeReqDescription
case_idstringyes–
deepboolean––
jurisdictionsarray–Default: the case's offices.
max_creditsintegeryesBudget the user agreed to; must cover the price.
querystring–Text query (default: the case's article).

No output schema declared.

No examples provided.

viewpack ~64

Free, local. Patent line drawings of a version for US (with surface shading), CN or EU, with the office's rule checks. Free plan: watermarked.

NameTypeReqDescription
case_idstringyes–
officestringyes–
versionstringyes–

No output schema declared.

No examples provided.

Install

How do I install the DesignAround MCP server?

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

pypi · designaround

# add to Claude Code
claude mcp add elidot007-designaround -- uvx designaround
Common questions

What is the DesignAround MCP server?

DesignAround is an MCP server listed in the public MCP registry as io.github.elidot007/designaround. Design-patent screening, design-around and drawings for US, CN and EU products. This page covers its PyPI package (designaround).

Is the DesignAround MCP server safe to use?

DesignAround scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 DesignAround MCP server expose?

DesignAround exposes 7 tools: case_list, decision_card, screen, design_around, run_status, and 2 more. Their descriptions and schemas cost roughly 553 tokens of context every time the server is loaded.

Is the DesignAround MCP server still maintained?

DesignAround is still listed as active in the MCP registry. We last reached this channel on 5 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 DesignAround MCP server under?

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