Drop2Run
NPM · @DROP2RUN/MCP · SCANNED SEP 25
Publishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link.
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 → 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
- 31 of 95 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 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1158 tokens (~193/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 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
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 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
How do I install the Drop2Run MCP server?
Drop2Run runs locally as an npm package, launched with npx -y @drop2run/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 · @drop2run/mcp
claude mcp add run-dropto-drop2run -- npx -y @drop2run/mcp
{
"mcpServers": {
"run-dropto-drop2run": {
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
} {
"servers": {
"run-dropto-drop2run": {
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
} codex mcp add run-dropto-drop2run -- npx -y @drop2run/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"run-dropto-drop2run": {
"type": "local",
"command": [
"npx",
"-y",
"@drop2run/mcp"
],
"enabled": true
}
}
} openclaw mcp add run-dropto-drop2run --command npx --arg -y --arg @drop2run/mcp
mcp_servers:
run-dropto-drop2run:
command: "npx"
args: ["-y", "@drop2run/mcp"] {
"McpServers": {
"run-dropto-drop2run": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@drop2run/mcp"
]
}
}
} assistant mcp add run-dropto-drop2run -t stdio -c npx -a -y @drop2run/mcp
{
"mcpServers": {
"run-dropto-drop2run": {
"command": "npx",
"args": [
"-y",
"@drop2run/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.
- 25 Sept 26 +16
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.5.1 → 0.6.0 functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 +9
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Schema quality: 141 → 188 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → 0.84 ▲ functional
- Package version: 0.4.3 → 0.5.1 functional
- Package version: 0.4.3 → 0.5.0 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 25 Sept 2026 · Analysed npm/@drop2run/mcp@0.6.0
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 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
delete_site Delete a site ~124
Takes a site down permanently — its files, its history and its subdomain. Nothing here undoes it, and the subdomain becomes available for anybody to claim. Requires `confirm` to repeat the site's own subdomain exactly; ask the person for it rather than filling it in from what you already know, because that is the step this asks for.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | yes | The subdomain of the site being deleted, repeated exactly. A mismatch refuses the call rather than guessing which site was meant. |
| site | string | yes | Subdomain or site id to delete. |
| Name | Type | Req | Description |
|---|---|---|---|
| siteId | string | yes | Identifier of the site that was deleted. |
| subdomain | string | yes | Its subdomain, now unclaimed. |
No examples provided.
list_sites List sites ~25
Lists the sites on this account, so a publish can go to one of them.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| sites | array | yes | Every site on this account. |
No examples provided.
login Sign in to Drop2Run ~126
Signs in through a browser on this machine and stores an access token, which every other tool then uses. Opens the browser here and waits for the person to approve. If it answers that nothing has been approved yet, call it again to keep waiting — that is not a failure. Needs no command line and no token pasted by hand.
| Name | Type | Req | Description |
|---|---|---|---|
| replace | boolean | – | Sign in even though a token is already stored. Use when switching accounts, or when the stored token is being refused. |
| waitSeconds | integer | – | How long this call waits for the approval before answering. Default 120. |
No output schema declared.
No examples provided.
login_code Sign in with a code ~97
Signs in where no browser can be opened on this machine — a container, a remote host. The first call returns a short code and a URL to enter it at, which the person opens anywhere; call it again to wait for the approval and store the token.
| Name | Type | Req | Description |
|---|---|---|---|
| replace | boolean | – | Sign in even though a token is already stored. |
| waitSeconds | integer | – | How long a waiting call polls before answering. Default 120. |
No output schema declared.
No examples provided.
publish_dir Publish a folder ~182
Publishes a folder from disk and returns its URL. The folder needs an index.html at its root, or documents (.md, .pdf, .docx, .xlsx, .epub), which are served through the reader.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path of the folder to publish. |
| site | string | – | Subdomain or site id to publish over. Omit to create a new site. |
| subdomain | string | – | Subdomain to create the new site under, when the person asked for a particular address. Only for a new site: leave it out to publish over an existing one, and do not pass it together with `site`. Ask… |
| Name | Type | Req | Description |
|---|---|---|---|
| files | integer | yes | How many files the site now serves. |
| siteId | string | yes | Identifier of the site, stable across publishes. |
| subdomain | string | yes | The site's subdomain, which is what `site` accepts. |
| unchanged | boolean | yes | True when every file already matched what the site served, so no new version was published. |
| url | string | yes | The live URL of the published site. |
No examples provided.
publish_files Publish files you wrote ~208
Publishes one or more files written here — markdown, HTML, CSS, JSON — as a site, and returns its URL. A single page goes at index.html; a single .md, .markdown or .pdf file is a site on its own, served through the documents viewer. Text only: a PDF or an image has to be published from disk with publish_dir.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | The files to publish. |
| site | string | – | Subdomain or site id to publish over. Omit to create a new site. |
| subdomain | string | – | Subdomain to create the new site under, when the person asked for a particular address. Only for a new site: leave it out to publish over an existing one, and do not pass it together with `site`. Ask… |
| Name | Type | Req | Description |
|---|---|---|---|
| files | integer | yes | How many files the site now serves. |
| siteId | string | yes | Identifier of the site, stable across publishes. |
| subdomain | string | yes | The site's subdomain, which is what `site` accepts. |
| unchanged | boolean | yes | True when every file already matched what the site served, so no new version was published. |
| url | string | yes | The live URL of the published site. |
No examples provided.
What is the Drop2Run MCP server?
Drop2Run is an MCP server listed in the public MCP registry as run.dropto/drop2run. Publishes what an AI made, a page, a markdown or PDF doc, or a whole site, to a live HTTPS link. This page covers its npm package (@drop2run/mcp).
Is the Drop2Run MCP server safe to use?
Drop2Run scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 Drop2Run MCP server expose?
Drop2Run exposes 6 tools: login, login_code, publish_files, publish_dir, delete_site, list_sites. Their descriptions and schemas cost roughly 762 tokens of context every time the server is loaded.
Is the Drop2Run MCP server still maintained?
Drop2Run is still listed as active in the MCP registry. We last reached this channel on 25 September 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 Drop2Run MCP server under?
Drop2Run declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.