digital.shineup/appcn

MCPcommunity
v0.1.2digital.shineupUnknownUpdated 4mo agonpmGitHub

Install & correctly use appCN React Native / Expo components, streamed from the live registry.

The appCN MCP server — gives AI coding agents (Claude Code, Cursor, Windsurf, Codex, …) first-class access to the appCN React Native component library. Agents can discover components, read their full docs (anatomy, the delight detail, props, usage examples, a11y notes), get the exact install command, and learn appCN's motion/haptic design tokens — so the code they write matches the system instead…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3GitHub stars
4mo agoLast update
Package
Authordigital.shineup
LicenseUnknown
Version0.1.2
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · 1 privileged
Security scan✓ Cleanv0.1.2 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · 1 privileged
Statically extracted from the published packagev0.1.2 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_componentNo description published

This tool published no description. Forge does not invent one.

get_design_guideNo description published

This tool published no description. Forge does not invent one.

get_install_commandprivilegedNo description published

This tool published no description. Forge does not invent one.

list_componentsNo description published

This tool published no description. Forge does not invent one.

search_componentsNo description published

This tool published no description. Forge does not invent one.

0 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

The appCN MCP server — gives AI coding agents (Claude Code, Cursor, Windsurf, Codex, …) first-class access to the appCN React Native component library. Agents can discover components, read their full docs (anatomy, the delight detail, props, usage examples, a11y notes), get the exact install command, and learn appCN's motion/haptic design tokens — so the code they write matches the system instead of guessing. It reads from the live appCN registry (), so it always reflects the latest published…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.