io.github.drumst0ck/uploadkit
NPM · @UPLOADKITDEV/MCP
UploadKit MCP — 40+ upload components, route scaffolds, BYOS setup, full docs search.
Available components
Last scanned (38 minutes ago)
Scores higher than 90% 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 Security98
- 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
- 30 of 92 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 Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 774 tokens (~55/item across 14 items; 11 tools + 3 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.90 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −3
- Stability: pass → 0.83 functional
- 13 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ 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 5 Nov 2026 · Analysed npm/@uploadkitdev/mcp@0.3.1
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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_byos_config ~54
Return environment + handler configuration for Bring-Your-Own-Storage mode with S3, R2, GCS, or Backblaze B2. Credentials never reach the browser.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | – |
No output schema declared.
No examples provided.
get_component ~46
Return full metadata + a ready-to-paste usage example for a specific UploadKit component.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Exact component name, e.g. "UploadDropzoneAurora". |
No output schema declared.
No examples provided.
get_doc ~78
Return the full content of a docs page by path (e.g. "core-concepts/byos", "sdk/next/middleware", "api-reference/rest-api"). Use this after search_docs to read a specific page in depth.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Page path relative to /docs (no leading slash, no .mdx extension). |
No output schema declared.
No examples provided.
get_install_command ~69
Return the install command for UploadKit packages. Defaults to pnpm + the full stack (react + next).
| Name | Type | Req | Description |
|---|---|---|---|
| packageManager | string | – | – |
| packages | array | – | Which UploadKit packages to install. Default: ["@uploadkitdev/react", "@uploadkitdev/next"]. |
No output schema declared.
No examples provided.
get_quickstart ~24
Full end-to-end quickstart guide for UploadKit on Next.js.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_components ~63
List every component available in @uploadkitdev/react. Optionally filter by category (classic, dropzone, button, progress, motion, specialty, gallery). Use this before suggesting a component so you pick one that actually exists.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional filter. |
No output schema declared.
No examples provided.
list_docs ~33
List every docs page with title, description, URL, and path. Use this to discover what documentation is available before searching.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scaffold_provider ~29
Return a ready-to-paste snippet that adds <UploadKitProvider> to the Next.js root layout.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scaffold_route_handler ~144
Generate the file content for a Next.js App Router route handler at app/api/uploadkit/[...uploadkit]/route.ts — with a file router typed to your route name.
| Name | Type | Req | Description |
|---|---|---|---|
| allowedTypes | array | – | MIME types allowed. Default: ["image/*"]. |
| maxFileCount | number | – | Default: 1. |
| maxFileSize | string | – | Max file size, e.g. "4MB", "1GB". Default: "4MB". |
| routeName | string | yes | Name of the file route, e.g. "media", "avatar", "attachments". This is the value you pass as the `route` prop on components. |
No output schema declared.
No examples provided.
search_components ~48
Fuzzy-search components by keyword, inspiration, or use case (e.g. "terminal", "apple", "progress ring", "kanban").
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text search. |
No output schema declared.
No examples provided.
search_docs ~114
Full-text search across every UploadKit docs page (88+ pages: getting-started, core-concepts, SDK reference, API reference, dashboard, guides). Use this whenever the user asks about UploadKit behaviour, APIs, middleware, webhooks, theming, BYOS, type safety, or any topic not covered by the component tools. Returns ranked matches with title, URL, snippet, and path.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results. Default: 8. |
| query | string | yes | Free-text query. |
No output schema declared.
No examples provided.
How do I install the io.github.drumst0ck/uploadkit MCP server?
io.github.drumst0ck/uploadkit runs locally as an npm package, launched with npx -y @uploadkitdev/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 · @uploadkitdev/mcp
claude mcp add drumst0ck-uploadkit -- npx -y @uploadkitdev/mcp
What is the io.github.drumst0ck/uploadkit MCP server?
io.github.drumst0ck/uploadkit is an MCP server listed in the public MCP registry as io.github.drumst0ck/uploadkit. UploadKit MCP, 40+ upload components, route scaffolds, BYOS setup, full docs search. This page covers its npm package (@uploadkitdev/mcp).
Is the io.github.drumst0ck/uploadkit MCP server safe to use?
io.github.drumst0ck/uploadkit scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 io.github.drumst0ck/uploadkit MCP server expose?
io.github.drumst0ck/uploadkit exposes 11 tools: list_components, get_component, search_components, get_install_command, scaffold_route_handler, and 6 more. Their descriptions and schemas cost roughly 702 tokens of context every time the server is loaded.
Is the io.github.drumst0ck/uploadkit MCP server still maintained?
io.github.drumst0ck/uploadkit is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.drumst0ck/uploadkit MCP server under?
io.github.drumst0ck/uploadkit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.