io.github.francesco0242/matchcn
NPM · MATCHCN · SCANNED SEP 25
Semantic index across shadcn-format component registries: find components by what they do.
Available components
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
- 32 of 125 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 166 tokens (~166/item across 1 items; 1 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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.
How do I install the io.github.francesco0242/matchcn MCP server?
io.github.francesco0242/matchcn runs locally as an npm package, launched with npx -y matchcn. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · matchcn
claude mcp add francesco0242-matchcn -- npx -y matchcn
{
"mcpServers": {
"francesco0242-matchcn": {
"command": "npx",
"args": [
"-y",
"matchcn"
]
}
}
} {
"servers": {
"francesco0242-matchcn": {
"command": "npx",
"args": [
"-y",
"matchcn"
]
}
}
} codex mcp add francesco0242-matchcn -- npx -y matchcn
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"francesco0242-matchcn": {
"type": "local",
"command": [
"npx",
"-y",
"matchcn"
],
"enabled": true
}
}
} openclaw mcp add francesco0242-matchcn --command npx --arg -y --arg matchcn
mcp_servers:
francesco0242-matchcn:
command: "npx"
args: ["-y", "matchcn"] {
"McpServers": {
"francesco0242-matchcn": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"matchcn"
]
}
}
} assistant mcp add francesco0242-matchcn -t stdio -c npx -a -y matchcn
{
"mcpServers": {
"francesco0242-matchcn": {
"command": "npx",
"args": [
"-y",
"matchcn"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.88 ▲ functional
- 23 Sept 26 45
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 25 Sept 2026 · Analysed npm/matchcn@0.2.2
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 125 packages
| Packages resolved | 125 |
|---|---|
| Stale | 32 |
| 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 →
pick_component Pick a shadcn-format component ~166
Given a plain-language description of a UI need, finds the best-matching component across the indexed shadcn-format registries (react-bits, magicui, aceternity, kokonutui, animate-ui, motion-primitives, shadcn-dashboard, assistant-ui, bundui). Returns one of three outcomes: confident (one clear winner), shortlist (several strong candidates with the differentiating dimension named), or no_match (nothing fits, closest candidates shown but marked rejected). Never a forced best guess.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | yes | Plain-language description of the component needed, any language |
| maxResults | integer | – | Max candidates to return for a shortlist or no_match outcome (default 3) |
| registry | string | – | Restrict the search to one registry |
No output schema declared.
No examples provided.
What is the io.github.francesco0242/matchcn MCP server?
io.github.francesco0242/matchcn is an MCP server listed in the public MCP registry as io.github.francesco0242/matchcn. Semantic index across shadcn-format component registries: find components by what they do. This page covers its npm package (matchcn).
Is the io.github.francesco0242/matchcn MCP server safe to use?
io.github.francesco0242/matchcn scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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.francesco0242/matchcn MCP server expose?
io.github.francesco0242/matchcn exposes 1 tool: pick_component. Their descriptions and schemas cost roughly 166 tokens of context every time the server is loaded.
Is the io.github.francesco0242/matchcn MCP server still maintained?
io.github.francesco0242/matchcn is still listed as active in the MCP registry. We last reached this channel on 25 September 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.francesco0242/matchcn MCP server under?
io.github.francesco0242/matchcn declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.