appCN
NPM · @APP-CN/MCP · SCANNED AUG 3
Install & correctly use appCN React Native / Expo components, streamed from the live registry.
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 64 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @app-cn/mcp
claude mcp add digital-shineup-appcn -- npx -y @app-cn/mcp
codex mcp add digital-shineup-appcn -- npx -y @app-cn/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"digital-shineup-appcn": {
"type": "local",
"command": [
"npx",
"-y",
"@app-cn/mcp"
],
"enabled": true
}
}
} openclaw mcp add digital-shineup-appcn --command npx --arg -y --arg @app-cn/mcp
mcp_servers:
digital-shineup-appcn:
command: "npx"
args: ["-y", "@app-cn/mcp"] {
"mcpServers": {
"digital-shineup-appcn": {
"command": "npx",
"args": [
"-y",
"@app-cn/mcp"
]
}
}
} 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.
- 3 Aug 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.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Licence: MIT functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +22
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
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 3 Aug 2026 · Analysed npm/@app-cn/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.