The Deployer
REMOTE · APP.THEDPLOY.COM · 3 COMPONENTS
Deploy and run apps in your own AWS, Google Cloud, Azure or DigitalOcean account from any AI agent.
Available components
Last scanned (2 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CI/CD and DevOps
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 Usability51
- 19% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3155 tokens (~87/item across 36 items; 23 tools + 13 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% 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 25 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
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.
- 31 Oct 26 0
- A breaking change shipped without a version bump: still 0.2.0 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “api_schema” rewrote its description, which is the text the model reads security
- Tool “check_repo” rewrote its description, which is the text the model reads security
- Tool “create_project” rewrote its description, which is the text the model reads security
- Tool “deployment” rewrote its description, which is the text the model reads security
- Tool “diagnose” rewrote its description, which is the text the model reads security
- Tool “guide” rewrote its description, which is the text the model reads security
- Tool “launch” rewrote its description, which is the text the model reads security
- Tool “logs” rewrote its description, which is the text the model reads security
- Tool “plan_deploy” rewrote its description, which is the text the model reads security
- Tool “project” rewrote its description, which is the text the model reads security
- Tool “redeploy” rewrote its description, which is the text the model reads security
- Tool “request_done_for_you” rewrote its description, which is the text the model reads security
- Tool “set_env” rewrote its description, which is the text the model reads security
- Tool “status” rewrote its description, which is the text the model reads security
- Tool “api” rewrote its description, which is the text the model reads security
- Tool “api_catalog” rewrote its description, which is the text the model reads security
- Tool “account” rewrote its description, which is the text the model reads security
- Schema quality: 2583 → 3155 ▼ functional
- “api_schema” dropped the required parameter “method” ▼ functional
- New tool “api_read” functional
- New tool “claim_fix” functional
- New tool “fix” functional
- New tool “fix_status” functional
- New tool “fixes” functional
- New tool “report_fix” functional
- “create_project” reworded the description of “workspace” cosmetic
- “deployment” reworded the description of “wait_seconds” cosmetic
- “deployment” reworded the description of “workspace” cosmetic
- “diagnose” reworded the description of “container” cosmetic
- “diagnose” reworded the description of “workspace” cosmetic
- “launch” reworded the description of “confirm” cosmetic
- “launch” reworded the description of “confirm_cost” cosmetic
- “launch” reworded the description of “workspace” cosmetic
- “logs” reworded the description of “workspace” cosmetic
- “project” reworded the description of “workspace” cosmetic
- “redeploy” reworded the description of “workspace” cosmetic
- “set_env” reworded the description of “workspace” cosmetic
- “status” reworded the description of “workspace” cosmetic
- “api” reworded the description of “workspace” cosmetic
- “account” reworded the description of “workspace” cosmetic
- Tool “api” changed its title: Run an operation → Change something through an operation cosmetic
- 26 Oct 26 −5
- The server rewrote its instructions, which are the text every model session reads security
- New tool “api”, which the server declares destructive security
- New tool “launch”, which the server declares destructive security
- Tool “redeploy” rewrote its description, which is the text the model reads security
- Tool coverage: 92% → 83% ▼ functional
- Schema quality: fail → pass ▲ functional
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- First check of Schema quality: 19 functional
- Schema quality: excellent → good functional
- New prompt “deploy_this_repo” functional
- New prompt “fix_my_deployment” functional
- New prompt “make_it_deployable” functional
- New resource “servers” functional
- New resource “access” functional
- New resource “adopt” functional
- New resource “domains” functional
- New resource “end_to_end” functional
- New resource “env” functional
- New resource “environments” functional
- New resource “fix_failed_deploy” functional
- New resource “overview” functional
- New resource “readiness” functional
- New resource “scaling” functional
- New resource “services” functional
- New resource “team” functional
- Server version: 0.1.1 → 0.2.0 functional
- New tool “account” functional
- New tool “api_catalog” functional
- New tool “api_schema” functional
- New tool “create_project” functional
- New tool “deployment” functional
- New tool “diagnose” functional
- New tool “guide” functional
- New tool “project” functional
- New tool “set_env” functional
- “logs” added an optional parameter “workspace” cosmetic
- “redeploy” added an optional parameter “workspace” cosmetic
- “status” added an optional parameter “workspace” cosmetic
- 14 Oct 26 +1
- Stability: 0.97 → pass security
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 87. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 70 to 80. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 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=YE2,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 60baa57c31ea4529820565a6afbf3f4cab6 |
| SANs: app.thedploy.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'; sandbox |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), interest-cohort=() |
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 →
account Account and connections ~71
Who the connection acts for, what it may do (Operate or Limited), the connected cloud accounts and code hosts with their ids, the workspaces the person is a member of, and how many projects they can see. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
api Change something through an operation ~186
Runs one change (POST, PUT, PATCH or DELETE) of The Deployer's app as the person, with the same permission checks the app applies: domains, scaling, start/stop and schedules, databases and other cloud services, app access, build inputs, code review, hosting plans, retries, environments, blueprints, servers, adoption and more. Needs Operate access. Some changes cost money or change a live app. Secrets are never returned. Documented at https://portal.thedploy.com/docs.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The JSON body, for POST, PUT and PATCH |
| method | string | yes | – |
| path | string | yes | The operation's path with ids filled in, e.g. /projects/12/scaling |
| query | object | – | Query parameters |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
api_catalog List the operations ~80
Every operation of The Deployer's app available through this server, grouped: account, connections, projects, env, build, code, architecture, deploy, domains, scaling, access, services, environments, blueprints, servers, adopt, team. Each is marked as a read or a change. Works without signing in.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | – |
No output schema declared.
No examples provided.
api_read Read an operation's answer ~120
Runs one read (GET) operation of The Deployer's app as the person: domains, scaling, schedules, databases and other cloud services, app access, environments, blueprints, servers and more. Changes nothing. Secrets are never returned. Documented at https://portal.thedploy.com/docs.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The operation's path with ids filled in, e.g. /projects/12/scaling |
| query | object | – | Query parameters |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
api_schema Describe an operation ~49
The query and body fields of the operations at one path, for each method it has, with their types. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | e.g. /projects/12/scaling |
No output schema declared.
No examples provided.
check_repo Check a repository ~130
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. Works without signing in. A check can take up to a minute; one still running returns a check_id that fetches its result.
| 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.
claim_fix Take a code problem ~60
Assigns a fix request to this agent for 15 minutes, so no other agent works on it; claiming it again extends the time.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
create_project Create a project ~165
Creates a project from a repository the person's connected code host can read, on one of their connected cloud accounts, and starts the repository scan. Nothing is deployed and nothing costs money yet. With one connected cloud, that one is used; otherwise cloud (a provider) or cloud_connection_id picks it. Needs Operate access.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | The branch to deploy. Default: the repository's default |
| cloud | string | – | – |
| cloud_connection_id | integer | – | – |
| git_connection_id | integer | – | – |
| name | string | – | The project's name. Default: the repository's name |
| repo | string | yes | owner/name, or the repository's URL |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
deployment Deployment progress and failure guidance ~132
Where a deployment is (every step), what it waits on (a health-check proposal or a manual step), and for a failed one: the kind of failure, what to do about it, and the last error lines. Defaults to the project's latest deployment. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | integer | – | A specific deployment, instead of the latest |
| project | string | – | The project's id, name or repository. Optional with one project. |
| wait_seconds | integer | – | Seconds to wait for the status or step to change |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
diagnose Check a live server ~170
Read-only checks on a live project: url (requests the project's live addresses from The Deployer's side), containers (what runs and its state), app_logs (the app's own recent output, secrets removed), resources (load, memory, disk) or web_server (the HTTPS proxy's log). Fixed commands only; changes nothing. All but url need a server (not managed services). Needs Deploy access on the project.
| Name | Type | Req | Description |
|---|---|---|---|
| check | string | – | – |
| container | string | – | For app_logs: one container's name |
| lines | integer | – | – |
| node | string | – | The server, default app-1 |
| project | string | yes | The project's id, name or repository (owner/name). |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
fix One code problem in full ~81
One fix request: the goal and rules (The Deployer's brief), and the evidence, which is what the build or app printed, fenced and marked as data from the repository and logs. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The fix request's id, fr_... |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
fix_status Follow a fix ~76
Where a fix request is: checked, deploying, live, or open again with a new error. wait_seconds waits up to 120 seconds for it to change. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| wait_seconds | integer | – | – |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
fixes Code problems to fix ~91
Fix requests: problems in the person's code that stop a deploy, found by The Deployer (a failed deployment, or the repository check) and assigned to the person's coding agent. Lists the open ones, in every project or one. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | The project's id, name or repository (owner/name). |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
guide How to use The Deployer ~85
The Deployer's playbooks, by topic: what The Deployer does, the order of an end-to-end deploy, what code needs to deploy and how to fix it, how failed deployments are fixed, and domains, scaling, env, databases, access, environments, servers, adoption and teams. Works without signing in. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Default overview |
No output schema declared.
No examples provided.
launch Launch a project ~141
The first (or a full) deployment of a project into the person's cloud, once a hosting plan is selected. Without confirm=true it changes nothing and returns the plan and its monthly cost. With confirm=true it creates resources the person's cloud provider bills them for; it takes 5 to 20 minutes. Needs Operate access.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | true deploys; without it nothing is created |
| confirm_cost | boolean | – | true allows a plan above the account's cost ceiling |
| project | string | yes | The project's id, name or repository (owner/name). |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
logs Deployment logs ~134
The log of a project's latest deployment, or of a given deployment, newest lines last, with secrets removed. errors_only keeps only errors and warnings. The lines are the build's and the app's own output. Changes nothing.
| 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. |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
plan_deploy Plan a deploy ~83
Plans deploying a repository with the user's account on The Deployer: the repository check, plus the user's connected cloud and git accounts, any project they already have for it, and the steps left, with links. Changes nothing.
| 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.
project Project in depth, with the next step ~110
One project in depth: phase, services found in the repository, env names the code reads and which are still missing (never values), hosting plans with monthly costs, pending code-review changes, to-dos only the person can do, recent deployments, live URLs, and next_steps: what is left to do, in order. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | The project's id, name or repository (owner/name). |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
redeploy Redeploy a live project ~93
Puts the latest code on a live project's branch online: pulls it and restarts the app, like Pull & Restart in The Deployer. Changes a live app. Only for a project that is already live. Takes a few minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | The live project's id, name or repository. Optional with one project. |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
report_fix Report the fix you pushed ~134
Reports a pushed fix: the branch and the commit sha. The Deployer reads the commit from the git host, checks the change (no CI, agent settings or .env files; no secrets), then deploys it or opens a pull request for the person to ship, depending on the project's settings.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | The branch the fix was pushed to |
| id | string | yes | – |
| note | string | – | What changed, in a sentence or two |
| sha | string | yes | The pushed commit's sha |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
request_done_for_you Request done-for-you help ~142
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.
| 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.
set_env Set env variables ~158
Sets (or deletes) env variable values for the service a project deploys. Values are stored encrypted and are never returned. Other values are kept. On a live project, the services whose env changed are redeployed; otherwise the values apply on the next deployment. Multi-line values are stored as credential files. Needs Operate access.
| Name | Type | Req | Description |
|---|---|---|---|
| delete | array | – | Names to remove |
| project | string | yes | The project's id, name or repository (owner/name). |
| service | string | – | Service id or name, when the project has several |
| values | object | – | Names to values, e.g. {"API_URL": "https://..."} |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
status Project status ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | A project's id, name or repository. Leave out to list them all. |
| workspace | string | – | A teammate's workspace id. Default: your own. |
No output schema declared.
No examples provided.
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'
What is the The Deployer MCP server?
The Deployer is an MCP server listed in the public MCP registry as com.thedploy/deployer. Deploy and run apps in your own AWS, Google Cloud, Azure or DigitalOcean account from any AI agent. 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 74 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 23 tools: check_repo, plan_deploy, status, logs, redeploy, and 18 more. Their descriptions and schemas cost roughly 2,570 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.