The Deployer
REMOTE · APP.THEDPLOY.COM · 2 COMPONENTS · SCANNED SEP 20
Check if a repo will deploy, plan a deploy to your own cloud, and see status, logs and redeploys.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (redeploy). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 7 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
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.
remote · app.thedploy.com
claude mcp add --transport http com-thedploy-deployer 'https://app.thedploy.com/api/v1/mcp'
{
"mcpServers": {
"com-thedploy-deployer": {
"url": "https://app.thedploy.com/api/v1/mcp"
}
}
} {
"servers": {
"com-thedploy-deployer": {
"type": "http",
"url": "https://app.thedploy.com/api/v1/mcp"
}
}
} [mcp_servers.com-thedploy-deployer] url = "https://app.thedploy.com/api/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-thedploy-deployer": {
"type": "remote",
"url": "https://app.thedploy.com/api/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-thedploy-deployer --url 'https://app.thedploy.com/api/v1/mcp' --transport streamable-http
mcp_servers:
com-thedploy-deployer:
url: "https://app.thedploy.com/api/v1/mcp" {
"McpServers": {
"com-thedploy-deployer": {
"Transport": "http",
"Url": "https://app.thedploy.com/api/v1/mcp"
}
}
} assistant mcp add com-thedploy-deployer -t streamable-http -u 'https://app.thedploy.com/api/v1/mcp'
{
"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.
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.
- 19 Sept 26 +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.
- 16 Sept 26 +1
- Tool “request_done_for_you” rewrote its description, which is the text the model reads security
- 15 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Sept 26 65
First indexed and scored.
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 · Probed https://app.thedploy.com/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.thedploy.com | CN=YE1,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 650e78e1da2893900bcda3fcde975a43fa3 |
| SANs: app.thedploy.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.thedploy.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| thedploy.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.thedploy.com/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://app.thedploy.com/api/v1/mcp | HTTPS enforced | 308 | https://app.thedploy.com/api/v1/mcp |
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 →
check_repo Check a repository ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | – | The check_id of an earlier check, to get its result |
| repo | string | – | owner/name, or the repository's URL |
No output schema declared.
No examples provided.
logs Deployment logs ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
plan_deploy Plan a deploy ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cloud | string | – | The cloud to plan for. Optional. |
| repo | string | yes | owner/name, or the repository's URL |
No output schema declared.
No examples provided.
redeploy Redeploy a live project ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | The live project's id, name or repository. Optional with one project. |
No output schema declared.
No examples provided.
request_done_for_you Request done-for-you help ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Anything the team should know, such as the current host or a deadline |
| offer | string | yes | – |
| repo | string | – | The repository, if there is one |
No output schema declared.
No examples provided.
status Project status ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | A project's id, name or repository. Leave out to list them all. |
No output schema declared.
No examples provided.
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.