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.

Wisty UI

REMOTE · UI.WISTY.AI

Find, read and install shadcn components with Salesforce Lightning's look, for Radix and Base UI.

Available components

+3 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 926 tokens (~185/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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% 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 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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

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

  • 11 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.

  • 10 Nov 26 0
    • Server version: 2026.11.08-2a79c45-dirty → 2026.11.09-d6e9451-dirty functional
  • 9 Nov 26 +1
    • Tool “get_component” rewrote its description, which is the text the model reads security
    • Tool “get_example” rewrote its description, which is the text the model reads security
    • Tool “get_install_command” rewrote its description, which is the text the model reads security
    • Tool “list_components” rewrote its description, which is the text the model reads security
    • Tool “search_components” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 94% ▼ functional
    • Schema quality: 225 → 185 ▲ functional
    • Schema quality: excellent → good functional
    • Server version: 2026.11.06-3de83f6-dirty → 2026.11.08-2a79c45-dirty functional
    • “get_component” reworded the description of “name” cosmetic
    • “get_component” reworded the description of “sections” cosmetic
    • “get_component” reworded the description of “source” cosmetic
    • “get_component” reworded the description of “style” cosmetic
    • “get_example” reworded the description of “example” cosmetic
    • “get_example” reworded the description of “name” cosmetic
    • “get_example” reworded the description of “style” cosmetic
    • “get_install_command” reworded the description of “name” cosmetic
    • “get_install_command” reworded the description of “srcDir” cosmetic
    • “get_install_command” reworded the description of “style” cosmetic
    • “get_install_command” reworded the description of “tailwindCss” cosmetic
    • “get_install_command” reworded the description of “themed” cosmetic
    • “search_components” reworded the description of “limit” cosmetic
    • “search_components” reworded the description of “query” cosmetic
  • 7 Nov 26 +1
    • Server version: 2026.11.05-d7ef741-dirty → 2026.11.06-3de83f6-dirty 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 · Probed https://ui.wisty.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.wisty.ai CN=YR1,O=Let's Encrypt,C=US 22 Sept 2026 21 Dec 2026 RSA 2048 SHA256-RSA 5e104a8c9b06dd7089237b437c49e530ec6
SANs: *.wisty.ai, wisty.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ui.wisty.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
wisty.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ui.wisty.ai/mcp Verified 200
http (plaintext) http://ui.wisty.ai/mcp HTTPS enforced 308 https://ui.wisty.ai/mcp
MCP tools · 5 exposed · ~759 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
get_component ~177

Read one Wisty UI item to choose and compose it: its install command, examples by name, When to use, When not to use, Usage, Rules, API reference.

NameTypeReqDescription
namestringyesThe item's name, like "lookup".
sectionsarray–Only these parts, under the title and install command. Without it, the parts above; the rest, on how the item already behaves, come only when named here.
sourceboolean–Add the installable files, for reading or copying by hand. Rarely needed: install with the shadcn command.
stylestring–The "style" in the project's components.json, like "radix-nova" or "base-nova": it picks the Radix or Base UI version. Leave it out for the Radix version.

No output schema declared.

No examples provided.

get_example ~132

Get one example's code for a Wisty UI item, for the project's base: a complete, working use to adapt.

NameTypeReqDescription
examplestring–The example's name, like "default", as get_component lists them. Leave it out for the first, which shows the job the item is for.
namestringyesThe item's name, like "lookup".
stylestring–The "style" in the project's components.json, like "radix-nova" or "base-nova": it picks the Radix or Base UI version. Leave it out for the Radix version.

No output schema declared.

No examples provided.

get_install_command ~228

Get the steps to install one Wisty UI item: the shadcn command, and the theme and icon steps it needs. First read style and tailwind.css from the project's components.json, and whether it has a src/ folder; a project without components.json runs npx shadcn@latest init first.

NameTypeReqDescription
namestringyesThe item's name, like "lookup".
srcDirboolean–Whether the project has a src/ folder. Left out, a tailwindCss under src/ means yes.
stylestringyesThe "style" in the project's components.json, like "radix-nova" or "base-nova": it picks the Radix or Base UI version.
tailwindCssstring–The "tailwind.css" path as components.json gives it, like "src/index.css", for the exact theme import lines.
themedboolean–True when the stylesheet already has Wisty UI's theme (--color-page in its @theme inline, or a tokens.css import), to leave the theme step out.

No output schema declared.

No examples provided.

list_components ~86

List every Wisty UI item by kind, with its first sentence. Primitives are shadcn's own components with the Salesforce look; components are what shadcn lacks, like lookup; blocks are finished Salesforce sections over sample data; helpers turn records into a block's props. Prefer search_components when you know the job.

NameTypeReqDescription
kindstring–Only items of this kind.

No output schema declared.

No examples provided.

search_components ~136

Find Wisty UI items by the job they do, best first. Each match gives its name, kind (primitive, component, block, helper) and description. A block is a finished section built from components and primitives over sample data, to install and edit: when the job is a whole section, start from its block, not its parts. Read a match with get_component.

NameTypeReqDescription
kindstring–Only items of this kind.
limitinteger––
querystringyesOne to three keywords for the job, like "record picker", "picklist" or "confirm delete", not a sentence.

No output schema declared.

No examples provided.

Install

How do I install the Wisty UI MCP server?

Wisty UI is a hosted endpoint at https://ui.wisty.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ui.wisty.ai

# add to Claude Code
claude mcp add --transport http ai-wisty-ui 'https://ui.wisty.ai/mcp'
Common questions

What is the Wisty UI MCP server?

Wisty UI is an MCP server listed in the public MCP registry as ai.wisty/ui. Find, read and install shadcn components with Salesforce Lightning's look, for Radix and Base UI. This page covers its hosted endpoint (https://ui.wisty.ai/mcp).

Is the Wisty UI MCP server safe to use?

Wisty UI scores 79 out of 100 on VerifyMCP. 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 Wisty UI MCP server expose?

Wisty UI exposes 5 tools: search_components, list_components, get_component, get_example, get_install_command. Their descriptions and schemas cost roughly 759 tokens of context every time the server is loaded.

Does the Wisty UI MCP server require authentication?

No. We connected to Wisty UI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Wisty UI MCP server still maintained?

Wisty UI 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 did VerifyMCP test on the Wisty UI MCP server?

VerifyMCP ran 13 checks on Wisty UI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.