# DeployAngel (pypi · deployangel)

Wait for production to clear each deploy, and read the evidence when a release fails.

- Trust score: 83/100 (high trust)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `deployangel`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-deployangel-deployangel/deployangel.md), [page](https://verifymcp.io/servers/com-deployangel-deployangel/deployangel)

## Channel facts

- Registry: `pypi`
- Package: `deployangel`
- Version: `0.1.29`
- 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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to DeployAngel/deployangel-python).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 961 tokens (~160/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**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 72% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the DeployAngel MCP server?

DeployAngel runs locally as a PyPI package, launched with uvx deployangel 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 com-deployangel-deployangel -- uvx deployangel mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-deployangel-deployangel": {
      "command": "uvx",
      "args": [
        "deployangel",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-deployangel-deployangel": {
      "command": "uvx",
      "args": [
        "deployangel",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-deployangel-deployangel -- uvx deployangel mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-deployangel-deployangel": {
      "type": "local",
      "command": [
        "uvx",
        "deployangel",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-deployangel-deployangel --command uvx --arg deployangel --arg mcp
```

### Hermes

```yaml
mcp_servers:
  com-deployangel-deployangel:
    command: "uvx"
    args: ["deployangel", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-deployangel-deployangel": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "deployangel",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-deployangel-deployangel -t stdio -c uvx -a deployangel mcp
```

### Other

```json
{
  "mcpServers": {
    "com-deployangel-deployangel": {
      "command": "uvx",
      "args": [
        "deployangel",
        "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-11-05 (score 83, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.47 → unverified
- [security regression] Malware scan: pass → unverified
- [security regression] Provenance: pass → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.26 → 0.1.28
- [functional] Package version: 0.1.26 → 0.1.27

### 2026-11-04 (score 83, +15)

- [security regression] Stability: 0.43 → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Schema quality: 139 → 156
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.24 → 0.1.26
- [functional] Package version: 0.1.24 → 0.1.25

### 2026-11-03 (score 68, +1)

- [security improvement] Malware scan: unverified → pass
- [functional] Package version: 0.1.23 → 0.1.24

### 2026-11-02 (score 67, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-01 (score 82, +20)

- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.37
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.20 → 0.1.23
- [functional] Package version: 0.1.20 → 0.1.21

### 2026-10-31 (score 62, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 77, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-25 (score 62, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (6)

### `get_verification` (~102 tokens)

Current verdict document for a deployment: state, verdict, confidence, coverage, findings, new exceptions, clearance report, and what is still watched. Defaults to the current git HEAD.

Input parameters:

- `commit` (string): Commit SHA (prefix of 7+ characters is fine).
- `deployment_id` (string): DeployAngel deployment ID.
- `latest` (boolean): Use the most recent deployment.
- `version` (string): Release version, e.g. v184.

### `wait_for_verification` (~156 tokens)

Wait for a deployment's verification. until=initial returns at the 15-minute initial check ("no problems so far" is NOT clearance); until=verdict waits for verified, failed, or inconclusive. Returns the in-progress document if timeout_seconds (max 300) is reached; call again while it is still in progress. Inconclusive means not verified.

Input parameters:

- `commit` (string): Commit SHA (prefix of 7+ characters is fine).
- `deployment_id` (string): DeployAngel deployment ID.
- `latest` (boolean): Use the most recent deployment.
- `timeout_seconds` (integer)
- `until` (string)
- `version` (string): Release version, e.g. v184.

### `get_exercise_plan` (~157 tokens)

What stands between a release and clearance, and what to exercise against production so it clears sooner: normally active routes short of their runs, routes this release changed that haven't run, and critical flows. needed marks what clearance waits on; the rest are only worth running. Routes marked mutating change data: use a test account or ask first. Your requests count as ordinary traffic; report what you ran with report_with. Defaults to the current git HEAD.

Input parameters:

- `commit` (string): Commit SHA (prefix of 7+ characters is fine).
- `deployment_id` (string): DeployAngel deployment ID.
- `latest` (boolean): Use the most recent deployment.
- `version` (string): Release version, e.g. v184.

### `list_deployments` (~26 tokens)

Recent deployments with their verification state and verdict.

Input parameters:

- `limit` (integer)

### `get_exception` (~40 tokens)

Sanitized details and a representative stack trace (application frames, or library frames when there are none) for an exception fingerprint.

Input parameters:

- `fingerprint` (string, required)

### `list_late_regressions` (~71 tokens)

Failures found after a release was cleared, on paths the clearance did not cover. One with dismissed set was dismissed by a person as a false alarm, with their reason: it needs no action.

Input parameters:

- `limit` (integer)
- `since` (string): ISO 8601 time

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-deployangel-deployangel/deployangel#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 68
- 2026-11-02: 67
- 2026-11-01: 82
- 2026-10-31: 62
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 62
- 2026-10-27: 62
- 2026-10-26: 62
- 2026-10-25: 62
- 2026-10-24: 77
- 2026-10-23: 62
- 2026-10-22: 77
- 2026-10-21: 62

## Common questions

### What is the DeployAngel MCP server?

DeployAngel is an MCP server listed in the public MCP registry as com.deployangel/deployangel. Wait for production to clear each deploy, and read the evidence when a release fails. This page covers its PyPI package (deployangel).

### Is the DeployAngel MCP server safe to use?

DeployAngel scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 DeployAngel MCP server expose?

DeployAngel exposes 6 tools: get_verification, wait_for_verification, get_exercise_plan, list_deployments, get_exception, list_late_regressions. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.

### Is the DeployAngel MCP server still maintained?

DeployAngel 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 DeployAngel MCP server under?

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

### What did VerifyMCP test on the DeployAngel MCP server?

VerifyMCP ran 16 checks on DeployAngel, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/deployangel/
- Socket report: https://socket.dev/pypi/package/deployangel
- Repository: https://github.com/DeployAngel/deployangel-python
- Website: https://www.deployangel.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-deployangel-deployangel/deployangel.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-deployangel-deployangel/deployangel/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-deployangel-deployangel/deployangel.json
- HTML version of this page: https://verifymcp.io/servers/com-deployangel-deployangel/deployangel