# The Deployer (remote · app.thedploy.com)

Check if a repo will deploy, plan a deploy to your own cloud, and see status, logs and redeploys.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `app.thedploy.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-thedploy-deployer/api-v1-mcp.md), [page](https://verifymcp.io/servers/com-thedploy-deployer/api-v1-mcp)
- npm · `thedeployer-mcp`: 40/100, [markdown](https://verifymcp.io/servers/com-thedploy-deployer/thedeployer-mcp.md), [page](https://verifymcp.io/servers/com-thedploy-deployer/thedeployer-mcp)

## Channel facts

- Endpoint: `https://app.thedploy.com/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (redeploy).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 831 tokens (~138/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**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "plan_deploy" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does.
  - 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 The Deployer MCP server?

The Deployer is a hosted endpoint at https://app.thedploy.com/api/v1/mcp, so there is nothing to install locally. 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 --transport http com-thedploy-deployer 'https://app.thedploy.com/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-thedploy-deployer": {
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-thedploy-deployer": {
      "type": "http",
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-thedploy-deployer]
url = "https://app.thedploy.com/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-thedploy-deployer": {
      "type": "remote",
      "url": "https://app.thedploy.com/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-thedploy-deployer --url 'https://app.thedploy.com/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-thedploy-deployer:
    url: "https://app.thedploy.com/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-thedploy-deployer": {
      "Transport": "http",
      "Url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-thedploy-deployer -t streamable-http -u 'https://app.thedploy.com/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-thedploy-deployer": {
      "type": "http",
      "url": "https://app.thedploy.com/api/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-19 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 66, +1)

- [security] Tool “request_done_for_you” rewrote its description, which is the text the model reads

### 2026-09-15 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-14 (score 65)

First indexed and scored.

## MCP tools (6)

### `check_repo` (~131 tokens)

Check a repository

Checks whether a public GitHub, GitLab or Bitbucket repository will deploy: the services it found, what's missing (each with its fix), the environment variables it needs, and what it would cost a month on DigitalOcean, AWS, Google Cloud and Azure. Reads the code and changes nothing. No API key needed. A check can take up to a minute; if it's still running, call again with the check_id it returned.

Input parameters:

- `check_id` (string): The check_id of an earlier check, to get its result
- `repo` (string): owner/name, or the repository's URL

### `plan_deploy` (~92 tokens)

Plan a deploy

Plans deploying a repository with the user's account on The Deployer: checks the repository like check_repo, then adds the user's connected cloud and git accounts, any project they already have for it, and the next steps, with links. Changes nothing. Needs an API key.

Input parameters:

- `cloud` (string): The cloud to plan for. Optional.
- `repo` (string, required): owner/name, or the repository's URL

### `status` (~67 tokens)

Project status

Lists the user's projects on The Deployer, or one project: whether each is live, its live addresses, and its latest deployment and where that is. Changes nothing. Needs an API key.

Input parameters:

- `project` (string): A project's id, name or repository. Leave out to list them all.

### `logs` (~125 tokens)

Deployment logs

Shows the log of a project's latest deployment, or of a given deployment, newest lines last, with secrets removed. Set errors_only to see only errors and warnings. The lines are the build's and the app's own output. Changes nothing. Needs an API key.

Input parameters:

- `deployment_id` (integer): A specific deployment, instead of the latest
- `errors_only` (boolean): Only errors and warnings
- `lines` (integer): How many lines, newest last. Default 80.
- `project` (string): The project's id, name or repository. Optional with one project.

### `redeploy` (~104 tokens)

Redeploy a live project

Puts the latest code on a live project's branch online: pulls it and restarts the app, like Pull & Restart in The Deployer. It changes a live app, so confirm with the user first. Only for a project that's already live; a project's first deployment starts in the app. Takes a few minutes; follow it with status or logs. Needs an API key.

Input parameters:

- `project` (string): The live project's id, name or repository. Optional with one project.

### `request_done_for_you` (~147 tokens)

Request done-for-you help

Asks The Deployer's team to do it for the user: launch (put an app online in the user's own cloud account), launch_secure (the same, with exposed keys and other security problems fixed first) or move (move an app from another host, such as Heroku, into it). Tells the team, and returns the price, the delivery promise and the link where the user finishes the order and pays. Never charges anything. Needs an API key.

Input parameters:

- `note` (string): Anything the team should know, such as the current host or a deadline
- `offer` (string, required)
- `repo` (string): The repository, if there is one

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-thedploy-deployer/api-v1-mcp#diagnostics

## Score history

- 2026-09-20: 67
- 2026-09-19: 67
- 2026-09-18: 66
- 2026-09-17: 66
- 2026-09-16: 66
- 2026-09-15: 65
- 2026-09-14: 65

## Common questions

### What is the The Deployer MCP server?

The Deployer is an MCP server listed in the public MCP registry as com.thedploy/deployer. Check if a repo will deploy, plan a deploy to your own cloud, and see status, logs and redeploys. This page covers its hosted endpoint (https://app.thedploy.com/api/v1/mcp).

### Is the The Deployer MCP server safe to use?

The Deployer scores 67 out of 100 on VerifyMCP. 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 The Deployer MCP server expose?

The Deployer exposes 6 tools: check_repo, plan_deploy, status, logs, redeploy, request_done_for_you. Their descriptions and schemas cost roughly 666 tokens of context every time the server is loaded.

### Does the The Deployer MCP server require authentication?

No. We connected to The Deployer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the The Deployer MCP server still maintained?

The Deployer 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.

## Links

- Remote endpoint: https://app.thedploy.com/api/v1/mcp
- Repository: https://github.com/Avinash147-1193/thedeployer-mcp
- Website: https://thedploy.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-thedploy-deployer/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-thedploy-deployer/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-thedploy-deployer/api-v1-mcp