Dr.Deploy
Scan live deployed sites from your agent—list targets, run scans, pull findings, and check status—without leaving Dr.Deploy’s API workflow.
Overview
Dr.Deploy MCP is an MCP server for the Ship phase that exposes scan, list, findings, and status tools for deployed sites via the drdeploy API.
What is this MCP server?
- MCP tools: scan deployed sites, list, get findings, check status
- npx @drdeploy/mcp v0.1.4 stdio with DRDEPLOY_TOKEN (drdeploy login)
- Optional DRDEPLOY_API_HOST override default https://drdeploy.dev
- Publisher site https://drdeploy.dev, package in Dr-Deploy/drdeploy monorepo
- Package version 0.1.4
- Default API host: https://drdeploy.dev
- Required env: DRDEPLOY_TOKEN
What problem does it solve?
After you deploy, security and configuration issues are easy to miss because scanning live URLs is outside your agent’s default toolset.
Who is it for?
Solo builders using Dr.Deploy who want agent-driven post-deploy scans and finding review on drdeploy.dev or custom API hosts.
Skip if: Teams with no deployed web surface yet, or those who need local SAST only with no live URL scanning service.
What do I get? / Deliverables
Once DRDEPLOY_TOKEN is set and the server is registered, your agent can launch scans and read findings on deployed sites before and after launch.
- Agent-initiated scans of deployed sites
- Structured findings and scan status from Dr.Deploy API
Recommended MCP Servers
Journey fit
How it compares
Live deployment scanning API via MCP, not a generic OWASP ZAP skill or hosting panel.
Common Questions / FAQ
Who is Dr.Deploy MCP for?
Indie developers on Dr.Deploy who want Claude Code or Cursor to scan live sites and read security findings through MCP.
When should I use Dr.Deploy MCP?
Right after deploy or before promoting a release, and again in production when you need to re-scan after infra or config changes.
How do I add Dr.Deploy MCP to my agent?
Run `drdeploy login` to get DRDEPLOY_TOKEN, add npx @drdeploy/mcp as a stdio MCP server with that env var (optional DRDEPLOY_API_HOST), then restart your agent.