io.github.CloudCorpRecords/designmind
NPM · @RENETURCIOS/DESIGNMIND · 2 COMPONENTS
Local design knowledge: principles, patterns, tokens, brand, content and metrics.
Available components
Last scanned (23 hours ago)
Scores higher than 35% of npm servers
Category Design and Media
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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 860 tokens (~43/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "compose_system" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 53
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 4 Nov 2026 · Analysed npm/@reneturcios/designmind@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
compose_system ~49
Merge token sets from catalogue design systems; later sources win on conflicts and conflicts are listed.
| Name | Type | Req | Description |
|---|---|---|---|
| sources | array | yes | Names of design systems to merge, in order; later sources win on token conflicts. |
No output schema declared.
No examples provided.
evaluate_design ~63
Evaluate a design description against the local principles catalogue: scores plus matching principles and violations.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | Whether to return only the overall score, grade, and per-dimension scores. |
| description | string | yes | Design description text to evaluate against the principles catalogue. |
No output schema declared.
No examples provided.
get_brand_principles ~45
Get brand principles, optionally for a topic.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Brand topic: distinctiveness, voice, positioning, or governance; omit to return all principles. |
No output schema declared.
No examples provided.
get_brand_system ~43
Get the brand system for a named brand in the catalogue.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name: govuk, polaris, atlassian, or conversational. |
No output schema declared.
No examples provided.
get_brand_trends ~20
Get current brand design trends from the local catalogue.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_business_strategy ~45
Get business strategy guidance, optionally for a topic.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Strategy topic: positioning, pricing, growth, retention, or trust; omit to list all topics. |
No output schema declared.
No examples provided.
get_checklist ~49
Get a design checklist for a UI type.
| Name | Type | Req | Description |
|---|---|---|---|
| ui_type | string | yes | UI type to look up: form, dashboard, checkout, landing-page, navigation, onboarding, mobile, or accessibility. |
No output schema declared.
No examples provided.
get_content_pattern ~48
Get a content pattern by pattern type.
| Name | Type | Req | Description |
|---|---|---|---|
| pattern_type | string | yes | Content pattern type: error-message, empty-state, confirmation, onboarding, help-text, notification, or form-labels. |
No output schema declared.
No examples provided.
get_content_principles ~47
Get content design principles, optionally for a topic.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Content topic: clarity, voice, structure, accessibility, or errors; omit to return all principles. |
No output schema declared.
No examples provided.
get_content_system ~48
Get the content (voice and tone) system for a named brand in the catalogue.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name: govuk, polaris, atlassian, or conversational. |
No output schema declared.
No examples provided.
get_d4d_framework ~57
Get the D4D (Discover, Define, Develop, Deliver) framework, optionally one template.
| Name | Type | Req | Description |
|---|---|---|---|
| template | string | – | D4D template: standard, sprint, workshop, or audit; omit for the framework overview. |
No output schema declared.
No examples provided.
get_design_system ~45
Get one design system and its token set by name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Design system name: material, carbon, polaris, atlassian, or govuk. |
No output schema declared.
No examples provided.
get_metrics_framework ~41
Get a product metrics framework by name.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Metrics framework name: heart, aarrr, north-star, rice, or okr. |
No output schema declared.
No examples provided.
get_pattern ~52
Get UI pattern guidance for a UI type.
| Name | Type | Req | Description |
|---|---|---|---|
| ui_type | string | yes | UI type to look up: dashboard, form, navigation, onboarding, search, checkout, empty-state, modal, table, or settings. |
No output schema declared.
No examples provided.
get_principles ~40
Get design principles relevant to a context.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Design context to match principles against, such as forms, navigation, or accessibility. |
No output schema declared.
No examples provided.
get_research_method ~52
Get a UX research method by method type.
| Name | Type | Req | Description |
|---|---|---|---|
| method_type | string | yes | Research method type: interview, usability-test, survey, diary-study, card-sort, a-b-test, or heuristic-evaluation. |
No output schema declared.
No examples provided.
get_service_pattern ~51
Get a service design pattern by name.
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | Service pattern name: start-page, check-eligibility, collect-information, check-answers, pay, confirmation, or status-tracking. |
No output schema declared.
No examples provided.
get_service_standard ~20
Get the GOV.UK Service Standard (14 points).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_design_systems ~19
List the design systems in the local catalogue.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_knowledge ~26
Search the local design knowledge catalogue.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query text. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/designmind MCP server?
io.github.CloudCorpRecords/designmind runs locally as an npm package, launched with npx -y @reneturcios/designmind. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/designmind
claude mcp add cloudcorprecords-designmind -- npx -y @reneturcios/designmind
What is the io.github.CloudCorpRecords/designmind MCP server?
io.github.CloudCorpRecords/designmind is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/designmind. Local design knowledge: principles, patterns, tokens, brand, content and metrics. This page covers its npm package (@reneturcios/designmind).
Is the io.github.CloudCorpRecords/designmind MCP server safe to use?
io.github.CloudCorpRecords/designmind scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 io.github.CloudCorpRecords/designmind MCP server expose?
io.github.CloudCorpRecords/designmind exposes 20 tools: get_principles, get_pattern, get_business_strategy, evaluate_design, search_knowledge, and 15 more. Their descriptions and schemas cost roughly 860 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/designmind MCP server still maintained?
io.github.CloudCorpRecords/designmind is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.CloudCorpRecords/designmind MCP server under?
io.github.CloudCorpRecords/designmind declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.