Ds3 MCP Server

@uxuissk/ds3-mcp npm v1.4.0

Published by @uxuissk — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
90/100
Last scanned
Trust
A · 90/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 98 − adoption risk = 90/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 2.1 = 98. What the published surface and source actually contain:

PointsWhat was foundCategory
−2.1 Package has no source repository MTC-SUP-011 supply-chain

2. Client adoption risk — 98 − 8 = 90. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−5 publisher verification (unlocatable) — no provenance and no public repository to inspect
inspection depth (source) — how much of the target the scan could see

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

low Package has no source repositoryMTC-SUP-011

"@uxuissk/ds3-mcp" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package @uxuissk/ds3-mcp

Tools 15

Each tool and what it can reach — statically extracted from the published source.

  • get_token_valuereads sensitive data
  • generate_formno sensitive capability
  • generate_page_layoutno sensitive capability
  • get_brand_rulesno sensitive capability
  • get_color_paletteno sensitive capability
  • get_componentno sensitive capability
  • get_design_tokensno sensitive capability
  • get_icon_catalogno sensitive capability
  • get_quick_startno sensitive capability
  • get_version_infono sensitive capability
  • list_componentsno sensitive capability
  • list_country_iconsno sensitive capability
  • list_iconsno sensitive capability
  • suggest_componentsno sensitive capability
  • validate_usageno sensitive capability

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.4.0 latest A 90/100 1 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 90/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/uxuissk-ds3-mcp/badge.svg)](https://mcptrustchecker.com/registry/uxuissk-ds3-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/uxuissk-ds3-mcp"><img src="https://mcptrustchecker.com/registry/uxuissk-ds3-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/uxuissk-ds3-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @uxuissk/ds3-mcp --online

Use the free API → How scoring works

More in Developer Tools