# Drop2Run (npm · @drop2run/mcp)

Publishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `@drop2run/mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/run-dropto-drop2run/drop2run-mcp.md), [page](https://verifymcp.io/servers/run-dropto-drop2run/drop2run-mcp)

## Channel facts

- Registry: `npm`
- Package: `@drop2run/mcp`
- Version: `0.6.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add run-dropto-drop2run -- npx -y @drop2run/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "run-dropto-drop2run": {
      "command": "npx",
      "args": [
        "-y",
        "@drop2run/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "run-dropto-drop2run": {
      "command": "npx",
      "args": [
        "-y",
        "@drop2run/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add run-dropto-drop2run -- npx -y @drop2run/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "run-dropto-drop2run": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@drop2run/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add run-dropto-drop2run --command npx --arg -y --arg @drop2run/mcp
```

### Hermes

```yaml
mcp_servers:
  run-dropto-drop2run:
    command: "npx"
    args: ["-y", "@drop2run/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "run-dropto-drop2run": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@drop2run/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add run-dropto-drop2run -t stdio -c npx -a -y @drop2run/mcp
```

### Other

```json
{
  "mcpServers": {
    "run-dropto-drop2run": {
      "command": "npx",
      "args": [
        "-y",
        "@drop2run/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 76, +16)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 60, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.5.1 → 0.6.0

### 2026-09-22 (score 75, +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.

### 2026-09-20 (score 74, +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.

### 2026-09-18 (score 73, +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.

### 2026-09-16 (score 72, +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.

### 2026-09-14 (score 71, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-13 (score 55, +9)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional regression] Schema quality: 141 → 188
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Dependency health: unverified → 0.84
- [functional] Package version: 0.4.3 → 0.5.1
- [functional] Package version: 0.4.3 → 0.5.0

## MCP tools (6)

### `login` (~126 tokens)

Sign in to Drop2Run

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.

Input parameters:

- `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.

### `login_code` (~97 tokens)

Sign in with a code

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.

Input parameters:

- `replace` (boolean): Sign in even though a token is already stored.
- `waitSeconds` (integer): How long a waiting call polls before answering. Default 120.

### `publish_files` (~208 tokens)

Publish files you wrote

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.

Input parameters:

- `files` (array, required): 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…

Output parameters:

- `files` (integer): How many files the site now serves.
- `siteId` (string): Identifier of the site, stable across publishes.
- `subdomain` (string): The site's subdomain, which is what `site` accepts.
- `unchanged` (boolean): True when every file already matched what the site served, so no new version was published.
- `url` (string): The live URL of the published site.

### `publish_dir` (~182 tokens)

Publish a folder

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.

Input parameters:

- `path` (string, required): 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…

Output parameters:

- `files` (integer): How many files the site now serves.
- `siteId` (string): Identifier of the site, stable across publishes.
- `subdomain` (string): The site's subdomain, which is what `site` accepts.
- `unchanged` (boolean): True when every file already matched what the site served, so no new version was published.
- `url` (string): The live URL of the published site.

### `delete_site` (~124 tokens)

Delete a site

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.

Input parameters:

- `confirm` (string, required): The subdomain of the site being deleted, repeated exactly. A mismatch refuses the call rather than guessing which site was meant.
- `site` (string, required): Subdomain or site id to delete.

Output parameters:

- `siteId` (string): Identifier of the site that was deleted.
- `subdomain` (string): Its subdomain, now unclaimed.

### `list_sites` (~25 tokens)

List sites

Lists the sites on this account, so a publish can go to one of them.

Output parameters:

- `sites` (array): Every site on this account.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/run-dropto-drop2run/drop2run-mcp#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 60
- 2026-09-23: 75
- 2026-09-22: 75
- 2026-09-21: 74
- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 55
- 2026-09-12: 46

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@drop2run/mcp
- Socket report: https://socket.dev/npm/package/@drop2run/mcp
- Repository: https://github.com/Drop-to-run/drop2run-cli
- Website: https://dropto.run/
- Changelog RSS feed: https://verifymcp.io/servers/run-dropto-drop2run/drop2run-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/run-dropto-drop2run/drop2run-mcp.json
- HTML version of this page: https://verifymcp.io/servers/run-dropto-drop2run/drop2run-mcp