appCN
NPM · @APP-CN/MCP
Install & correctly use appCN React Native / Expo components, streamed from the live registry.
Available components
Last scanned (20 hours ago)
Scores higher than 69% of npm servers
Category Developer Tools
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 174 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 482 tokens (~96/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.93 functional
- 14 Nov 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: pass → unverified ▼ functional
- 10 Nov 26 0
- Security disclosure: unverified → pass ▲ functional
- Stability: pass → 0.93 functional
- 9 Nov 26 −1
- Security disclosure: pass → unverified ▼ functional
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.93 functional
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 · Analysed npm/@app-cn/mcp@0.1.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
get_component Get an appCN component ~108
Everything an agent needs to add and correctly use one appCN component: its docs (anatomy, delight detail, props, usage examples, accessibility notes), the actual source file contents, the npm packages and registry helpers it depends on, and the install command. Prefer installing via the install command rather than pasting `files` by hand — that resolves dependencies for you.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Component slug, e.g. 'button', 'stream-bubble', 'voice-sphere'. |
No output schema declared.
No examples provided.
get_design_guide Get the appCN design guide ~84
appCN's taste layer: the motion duration/easing/spring tokens, the press-scale and haptics conventions, the variant API rules, accessibility requirements, and the explicit 'what NOT to do' list. Read this before writing or modifying any React Native component so the code feels like appCN — never hand-type durations or easings, reach for these tokens.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_install_command Get an appCN install command ~119
The exact command to add an appCN component to a project. Returns three install methods — the appCN CLI (recommended; handles NativeWind + Reanimated setup), shadcn namespaced, and shadcn by URL (zero setup) — for the requested package manager (or all of them).
| Name | Type | Req | Description |
|---|---|---|---|
| manager | string | – | Package manager: npm, pnpm, yarn, or bun. Omit to get commands for all four. |
| slug | string | yes | Component slug, e.g. 'button' or 'voice-sphere'. |
No output schema declared.
No examples provided.
list_components List appCN components ~93
List every appCN component, optionally filtered by category. Returns each component's slug, title, category, one-line description, and its signature 'delight' detail. Start here to see what's available, then call get_component for the full source and docs.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter to 'base' (the broad mobile library) or 'ai' (the featured AI-native collection). Omit for all. |
No output schema declared.
No examples provided.
search_components Search appCN components ~78
Find appCN components by intent or keyword — e.g. 'chat input', 'voice indicator', 'streaming message', 'reasoning'. Returns ranked matches with their delight detail. Use get_component on the best match for the full source and docs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What you're looking for, in plain words (intent or keywords). |
No output schema declared.
No examples provided.
How do I install the appCN MCP server?
appCN runs locally as an npm package, launched with npx -y @app-cn/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @app-cn/mcp
claude mcp add digital-shineup-appcn -- npx -y @app-cn/mcp
What is the appCN MCP server?
appCN is an MCP server listed in the public MCP registry as digital.shineup/appcn. Install & correctly use appCN React Native / Expo components, streamed from the live registry. This page covers its npm package (@app-cn/mcp).
Is the appCN MCP server safe to use?
appCN scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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 appCN MCP server expose?
appCN exposes 5 tools: list_components, search_components, get_component, get_install_command, get_design_guide. Their descriptions and schemas cost roughly 482 tokens of context every time the server is loaded.
Is the appCN MCP server still maintained?
appCN 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 licence is the appCN MCP server under?
appCN declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the appCN MCP server?
VerifyMCP ran 16 checks on appCN, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.