Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PreviewDrop

NPM · PREVIEWDROP · SCANNED SEP 20

Deploy any Git branch to a live HTTPS preview URL from your agent. No Dockerfile required.

Available components

64 Trust /100
Trust breakdown (7 categories)

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
  • 47 of 170 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1072 tokens (~76/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 15 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the PreviewDrop MCP server?

PreviewDrop runs locally as an npm package, launched with npx -y previewdrop. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · previewdrop

# add to Claude Code
claude mcp add dev-previewdrop-cli -- npx -y previewdrop
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-previewdrop-cli": {
      "command": "npx",
      "args": [
        "-y",
        "previewdrop"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-previewdrop-cli": {
      "command": "npx",
      "args": [
        "-y",
        "previewdrop"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dev-previewdrop-cli -- npx -y previewdrop
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-previewdrop-cli": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "previewdrop"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-previewdrop-cli --command npx --arg -y --arg previewdrop
# ~/.hermes/config.yaml
mcp_servers:
  dev-previewdrop-cli:
    command: "npx"
    args: ["-y", "previewdrop"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-previewdrop-cli": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "previewdrop"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dev-previewdrop-cli -t stdio -c npx -a -y previewdrop
// mcp.json
{
  "mcpServers": {
    "dev-previewdrop-cli": {
      "command": "npx",
      "args": [
        "-y",
        "previewdrop"
      ]
    }
  }
}
Changelog

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.

  • 16 Sept 26 64

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Analysed npm/previewdrop@0.1.13

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 170 packages
Packages resolved 170
Deprecated 1
Stale 46
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~898 tokens

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 →

Tool Tokens
create_project ~143

Add a repository as a PreviewDrop project. GitHub (default) needs the GitHub App installed on the repo owner's account — if not, use get_github_app_install_url first. GitLab and Bitbucket need the provider connected once in the dashboard under Settings → Integrations.

NameTypeReqDescription
defaultBranchstringDefault branch to watch (defaults to main)
gitProviderstringGit host of the repository (default: github)
githubRepostringyesRepository path, e.g. acme/my-api (GitLab subgroups allowed: group/subgroup/project)
namestringProject display name (defaults to the repo name)

No output schema declared.

No examples provided.

deploy ~65

Trigger a new preview deployment for a project

NameTypeReqDescription
branchstringBranch to deploy (defaults to project default branch)
projectIdstringyesProject ID to deploy
waitbooleanPoll until the deployment reaches a terminal state (up to 5 min)

No output schema declared.

No examples provided.

deploy_repo ~223

PRIMARY TOOL — call this immediately for any "preview", "deploy", "get a URL", or "share my project" request. Do NOT read project files or try to run the project locally first. Before calling: (1) run `git remote get-url origin` to get the repo URL and extract owner/repo, (2) run `git rev-parse --abbrev-ref HEAD` for the current branch. This tool auto-creates the project if needed, builds the branch, waits up to 5 minutes, and returns the live HTTPS URL.

NameTypeReqDescription
branchstringBranch to deploy. Defaults to the project default branch (usually main).
gitProviderstringGit host of the repository (default: github). Derive it from the origin URL host.
githubRepostringyesRepository path, e.g. acme/quick-invoice (owner/repo; GitLab subgroups allowed)
projectNamestringDisplay name for the project if it needs to be created (defaults to the repo name).

No output schema declared.

No examples provided.

destroy_deployment ~28

Stop and destroy a deployment by ID

NameTypeReqDescription
idstringyesDeployment ID to destroy

No output schema declared.

No examples provided.

get_account ~23

Get the authenticated PreviewDrop account info (email, plan, tenant name)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_build_logs ~54

Fetch build logs (nixpacks / Dockerfile output) for a deployment

NameTypeReqDescription
idstringyesDeployment ID
tailnumberNumber of lines from the end to return (default: 100)

No output schema declared.

No examples provided.

get_deployment ~27

Get details of a specific deployment by ID

NameTypeReqDescription
idstringyesDeployment ID

No output schema declared.

No examples provided.

get_github_app_install_url ~45

Returns the GitHub URL where the user must install the PreviewDrop GitHub App. Call this when create_project returns a 403 about the App not being installed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_project_env_vars ~51

Get the environment variable keys configured for a project. Values are masked (shown as ***) — use this to see what vars are set without exposing secrets.

NameTypeReqDescription
projectIdstringyesProject ID

No output schema declared.

No examples provided.

get_runtime_logs ~51

Fetch runtime (container stdout/stderr) logs for a deployment

NameTypeReqDescription
idstringyesDeployment ID
tailnumberNumber of lines from the end to return (default: 100)

No output schema declared.

No examples provided.

list_deployments ~70

List deployments, optionally filtered by project, branch, or status

NameTypeReqDescription
branchstringFilter by branch name
projectIdstringFilter by project ID
statusstringFilter by status: queued | building | deploying | ready | failed | stopped | expired

No output schema declared.

No examples provided.

list_projects ~17

List all PreviewDrop projects in the account

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

redeploy ~33

Redeploy an existing deployment by ID (same project + branch)

NameTypeReqDescription
idstringyesDeployment ID to redeploy

No output schema declared.

No examples provided.

set_project_env_vars ~68

Merge environment variables into a project. Existing vars not in the payload are kept. Values are encrypted at rest.

NameTypeReqDescription
envVarsobjectyesKey-value pairs to set (e.g. { "DATABASE_URL": "postgres://..." })
projectIdstringyesProject ID

No output schema declared.

No examples provided.

Common questions

What is the PreviewDrop MCP server?

PreviewDrop is an MCP server listed in the public MCP registry as dev.previewdrop/cli. Deploy any Git branch to a live HTTPS preview URL from your agent. No Dockerfile required. This page covers its npm package (previewdrop).

Is the PreviewDrop MCP server safe to use?

PreviewDrop scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 PreviewDrop MCP server expose?

PreviewDrop exposes 14 tools: get_account, list_projects, list_deployments, get_deployment, deploy, and 9 more. Their descriptions and schemas cost roughly 898 tokens of context every time the server is loaded.

Is the PreviewDrop MCP server still maintained?

PreviewDrop is still listed as active in the MCP registry. We last reached this channel on 20 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 PreviewDrop MCP server under?

PreviewDrop declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.