UploadKit MCP — 40+ upload components, route scaffolds, BYOS setup, full docs search.
Model Context Protocol server for UploadKit — gives AI coding assistants (Claude Code, Cursor, Windsurf, Zed) first-class knowledge of the UploadKit SDK. Every one of UploadKit's 40+ React components (name, category, inspiration, usage) How to scaffold the Next.js route handler "args": ["-y", "@uploadkitdev/mcp"] claude mcp add uploadkit -- npx -y @uploadkitdev/mcp Command: npx -y…
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 1 source file from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Model Context Protocol server for UploadKit — gives AI coding assistants (Claude Code, Cursor, Windsurf, Zed) first-class knowledge of the UploadKit SDK. Every one of UploadKit's 40+ React components (name, category, inspiration, usage) How to scaffold the Next.js route handler "args": ["-y", "@uploadkitdev/mcp"] claude mcp add uploadkit -- npx -y @uploadkitdev/mcp Command: npx -y @uploadkitdev/mcp npx -y…
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.