shadcn (xingarr/shadcn) is an MCP server listed on the M8ven Trust Index. It scores 46 out of 100, grade D. It declares 7 tools. No publisher has claimed this listing.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

xingarr

Source: github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 7 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 6 credentials: API_KEY, API_TOKEN, AUTH_TOKEN, EMPTY_TOKEN, TEST_TOKEN, TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes7 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_project_registries

Get configured registry names from components.json - Returns error if no components.json exists (use init_project to create one)

list_items_in_registries

List items from registries (requires components.json - use init_project if missing)

search_items_in_registries

Search for components in registries using fuzzy matching (requires components.json). After finding an item, use get_item_examples_from_registries to see usage examples.

view_items_in_registries

View detailed information about specific registry items including the name, description, type and files content. For usage examples, use get_item_examples_from_registries instead.

get_item_examples_from_registries

Find usage examples and demos with their complete code. Search for patterns like 'accordion-demo', 'button example', 'card-demo', etc. Returns full implementation code with dependencies.

get_add_command_for_items

Get the shadcn CLI add command for specific items in a registry. This is useful for adding one or more components to your project.

get_audit_checklist

After creating new components or generating new code files, use this tool for a quick checklist to verify that everything is working as expected. Make sure to run the tool after all required steps have been completed.

// known CVEs in dependencies7 high1 medium4 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.17.2GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.17.2GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.17.2GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highbrowserslist@4.26.2GHSA-73wf-gq98-2v4g

Browserslist: Uncaught crash / prototype write via untrusted browserslist-stats.json custom stats (normalizeStats)

highbrowserslist@4.26.2GHSA-c83g-rgw3-j3cx

Browserslist: Unbounded memory growth (no cache eviction) via distinct query results, leading to eventual OOM

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretAPI_KEY
🔐 secretAPI_TOKEN
configAPI_URL
configAPI_VERSION
🔐 secretAUTH_TOKEN
configCLIENT_ID
🔐 secretEMPTY_TOKEN
configREGISTRY_URL
🔐 secretTEST_TOKEN
🔐 secretTOKEN
confighttps_proxy
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/7 tools missing one or more hints — get_project_registries (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_items_in_registries (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_items_in_registries (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 0/7 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

0 critical, 7 high severity in production deps — @modelcontextprotocol/sdk@1.17.2 (high), @modelcontextprotocol/sdk@1.17.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

4/34 production deps abandoned (no release in 2+ years): deepmerge@2023-03-16 (3.5y), kleur@2023-07-09 (3.2y), prompts@2023-10-21 (2.9y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/xingarr/shadcn?variant=verified)](https://m8ven.ai/mcp/xingarr/shadcn)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 2ba756427ac045667b047ab75c4bb9bd730b2fb2
code hash: 48246c13613dcef7813d6186833f3bcbcb359b2e06f3de1fafcf618192a8f73c
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client