Skip to content

The Deployer MCP server

com.thedploy/deployerthedploy.comstreamable-httpv0.3.0Scanned

Deploy and run apps in your own AWS, Google Cloud, Azure or DigitalOcean account from any AI agent.

17 tools: 3 can delete or cancel things, 10 change things and 4 only read.

Tools: 3 delete, 0 irreversible, 10 write, 4 read.
  • Reads private data · 2
  • Reads text others write · 6
  • Can send data out · 0
  • 3 findings, 1 high

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the The Deployer MCP server can do

The The Deployer MCP server is published by thedploy.com, a domain the MCP Registry verified. It has 17 tools. It can delete or cancel things (3 tools: redeploy, launch and api) and create or change data (10 tools: check_repo, plan_deploy, request_done_for_you, guide and 6 more). 4 tools only read.

2 tools read private data (logs and diagnose); 6 tools bring in text other people can write (check_repo, plan_deploy, request_done_for_you and 3 more).

The fixed checks matched 3 findings, 1 of them high severity (annotation-conflict, sensitive-path and credentials-mention). Each one comes with the text it matched.

Its remote endpoint asks for sign-in and publishes OAuth metadata, and its tools changed once since Anlyon Radar first saw them.

Last scanned Oct 29, 2026, version 0.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Deletes or cancels 3Claude Code: deny
  • apiRuns one operation from api_catalog as the person, with the same permission checks The Deployer's app applies: domains, scaling, start/stop and schedules, databases and other cloud…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Runs one operation from api_catalog as the person, with the same permission checks The Deployer's 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. Reads work with any key; changes need a key with Operate access, and ones that cost money or change a live app need the person's yes first. Secrets are never returned.

    Annotations the server declares

    • title: Run an operation
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • launchThe first (or a full) deployment of a project into the person's cloud, once a hosting plan is selected.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The first (or a full) deployment of a project into the person's cloud, once a hosting plan is selected. Without confirm it changes nothing and answers with the plan and its monthly cost: tell the person and wait for their yes. Then call again with confirm=true. It creates resources their cloud provider bills them for. Takes 5 to 20 minutes; follow it with deployment. Needs a key with Operate access.

    Annotations the server declares

    • title: Launch a project
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • redeployPuts the latest code on a live project's branch online: pulls it and restarts the app, like Pull & Restart in The Deployer.No findings

    Why it is in this group

    • The description's first verb is "put": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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 is launch. Takes a few minutes; follow it with deployment. Works with any API key.

    Annotations the server declares

    • title: Redeploy a live project
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Changes things 10Claude Code: ask
  • accountWho this key acts for, what it may do (Operate or Limited), the connected cloud accounts and code hosts (with their ids, for create_project), the workspaces the person is a member …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Who this key acts for, what it may do (Operate or Limited), the connected cloud accounts and code hosts (with their ids, for create_project), the workspaces the person is a member of, and how many projects they can see. Changes nothing.

    Annotations the server declares

    • title: Account and connections
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • api_catalogEvery other operation agents can run with api, grouped: account, connections, projects, env, build, code, architecture, deploy, domains, scaling, access, services, environments, bl…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Every other operation agents can run with api, grouped: account, connections, projects, env, build, code, architecture, deploy, domains, scaling, access, services, environments, blueprints, servers, adopt, team. Each says whether it only reads or changes something. No API key needed.

    Annotations the server declares

    • title: List the operations
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_repoChecks 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 …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a repository
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_projectCreates 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.No findings

    Why it is in this group

    • The name "create_project" says "create": a word for a change.
    Description, as the server wrote it
    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 you don't need to name it; otherwise pass cloud (a provider) or cloud_connection_id (from account). Then follow project's next_steps. Needs a key with Operate access.

    Annotations the server declares

    • title: Create a project
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • deploymentWhere a deployment is (every step), what it waits on (a health-check proposal or a manual step, and the call that answers it), and for a failed one: the kind of failure, what to do…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Where a deployment is (every step), what it waits on (a health-check proposal or a manual step, and the call that answers it), and for a failed one: the kind of failure, what to do, and the last error lines. Defaults to the project's latest deployment. Changes nothing.

    Annotations the server declares

    • title: Deployment progress and failure guidance
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • guideThe playbooks for agents: what The Deployer does, which tool fits which job, the order of an end-to-end deploy, what code needs to deploy and how to fix it locally, how to fix a fa…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The playbooks for agents: what The Deployer does, which tool fits which job, the order of an end-to-end deploy, what code needs to deploy and how to fix it locally, how to fix a failed deployment, and domains, scaling, env, databases, access, environments, servers, adoption and teams. Read topic overview first, and end_to_end before a first deploy. No API key needed.

    Annotations the server declares

    • title: How to use The Deployer
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • plan_deployPlans 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…Reads text others write1 finding

    Why it is in this group

    • The name "plan_deploy" says "deploy": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "plan_deploy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "plan_deploy" says "deploy": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Plan a deploy
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • projectOne 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-r…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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: the exact next call to make. Call it after every step of a deploy. Changes nothing.

    Annotations the server declares

    • title: Project in depth, with the next step
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • request_done_for_youAsks 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 f…Reads text others writeNo findings

    Why it is in this group

    • The name "request_done_for_you" says "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Request done-for-you help
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • set_envSets (or deletes) env variable values for the service a project deploys.2 findings

    Why it is in this group

    • The name "set_env" says "set": a word for a change.

    Findings

    • High

      The description refers to ".env".

      Matched text

      description: "...nt. Read values from the person's local .env only with their OK; never invent secret..."

      What this check looks for
    • Info

      The description mentions "credential".

      Matched text

      description: "...r invent secrets. Multi-line values are credential files (guide topic env). Needs a key wi..."

      What this check looks for
    Description, as the server wrote it
    Sets (or deletes) env variable values for the service a project deploys. Values are stored encrypted and never shown back to any agent. Other values are kept. On a live project the services whose env changed are redeployed (so confirm first); otherwise they apply on the next deployment. Read values from the person's local .env only with their OK; never invent secrets. Multi-line values are credential files (guide topic env). Needs a key with Operate access.

    Annotations the server declares

    • title: Set env variables
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • api_schemaThe query and body fields of one operation from api_catalog, with their types.No findings

    Why it is in this group

    • The description's first verb is "query": a word for reading.
    Description, as the server wrote it
    The query and body fields of one operation from api_catalog, with their types. Changes nothing.

    Annotations the server declares

    • title: Describe an operation
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • diagnoseRead-only checks on a live project, for when an app misbehaves after deploying: url (request the project's own live addresses from The Deployer's side, for when you can't reach the…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "secret": it reads secrets.
    • untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Read-only checks on a live project, for when an app misbehaves after deploying: url (request the project's own live addresses from The Deployer's side, for when you can't reach them yourself), containers (what runs and its state), app_logs (the app's own recent output, secrets removed; container picks one), resources (load, memory, disk) or web_server (the HTTPS proxy's log). Fixed commands only, nothing changes. Everything but url needs a server (not managed services). Needs Deploy on the project.

    Annotations the server declares

    • title: Check a live server
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • logsShows the log of a project's latest deployment, or of a given deployment, newest lines last, with secrets removed.Reads private dataNo findings

    Why it is in this group

    • The name "logs" says "log": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "show" and "secret": it reads secrets.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Deployment logs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • statusLists 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.No findings

    Why it is in this group

    • The name "status" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Project status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 18:48 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://app.thedploy.com/.well-known/oauth-protected-resource/mcp
RFC 9728 protected resource metadata
https://app.thedploy.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://app.thedploy.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Posture changes

  1. Nov 20, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 401
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://app.thedploy.com/.well-known/oauth-protected-resource/mcp
    • RFC 9728 protected resource metadata: none to https://app.thedploy.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://app.thedploy.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes
  2. Nov 13, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 401 to none
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://app.thedploy.com/.well-known/oauth-protected-resource/mcp to none
    • RFC 9728 protected resource metadata: https://app.thedploy.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://app.thedploy.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed
  3. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 13 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://app.thedploy.com/.well-known/oauth-protected-resource/mcp
    • RFC 9728 protected resource metadata: none to https://app.thedploy.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://app.thedploy.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes
  4. Oct 29, 2026
    • Tools that change things, listed without credentials: 4 to 13

Findings

Matches of fixed checks, with the text they matched.

1 high1 warn1 info
  • The description refers to ".env".

    Matched text

    description: "...nt. Read values from the person's local .env only with their OK; never invent secret..."

    What this check looks for
  • The server marks "plan_deploy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "plan_deploy" says "deploy": a word for a change.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...r invent secrets. Multi-line values are credential files (guide topic env). Needs a key wi..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 401; WWW-Authenticate on 401: not observed -> yes (and 5 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 401
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://app.thedploy.com/.well-known/oauth-protected-resource/mcp
    • RFC 9728 protected resource metadata: none to https://app.thedploy.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://app.thedploy.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 401 -> none; WWW-Authenticate on 401: yes -> not observed (and 5 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 401 to none
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://app.thedploy.com/.well-known/oauth-protected-resource/mcp to none
    • RFC 9728 protected resource metadata: https://app.thedploy.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://app.thedploy.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed
  3. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 13 -> 0 (and 7 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 13 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://app.thedploy.com/.well-known/oauth-protected-resource/mcp
    • RFC 9728 protected resource metadata: none to https://app.thedploy.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://app.thedploy.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 13.View diff
    • Tools that change things, listed without credentials: 4 to 13
  5. Tools11 added, 3 changed.+11 added~3 changedView diff

Install

Pinned to version 0.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http deployer https://app.thedploy.com/mcp
claude mcp add --transport http deployer https://app.thedploy.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__deployer__status",
      "mcp__deployer__logs",
      "mcp__deployer__diagnose",
      "mcp__deployer__api_schema"
    ],
    "ask": [
      "mcp__deployer__check_repo",
      "mcp__deployer__plan_deploy",
      "mcp__deployer__request_done_for_you",
      "mcp__deployer__guide",
      "mcp__deployer__account",
      "mcp__deployer__project",
      "mcp__deployer__deployment",
      "mcp__deployer__create_project",
      "mcp__deployer__set_env",
      "mcp__deployer__api_catalog"
    ],
    "deny": [
      "mcp__deployer__redeploy",
      "mcp__deployer__launch",
      "mcp__deployer__api"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as deployer. Review it before you use it.

Capability tags behind 7 rules
  • mcp__deployer__check_repo untrusted-input
  • mcp__deployer__plan_deploy untrusted-input
  • mcp__deployer__logs private-data
  • mcp__deployer__request_done_for_you untrusted-input
  • mcp__deployer__diagnose private-data, untrusted-input
  • mcp__deployer__launch untrusted-input
  • mcp__deployer__api untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.thedploy/deployer/verify?hash=b6f3d220f2175e97ec37d6589a150e7a11cc40c7c42c5e7e485adbcd88ec1174" | jq -e '.changed == false'

Pinned hash b6f3d220f217, from Oct 29, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.thedploy/deployer/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.thedploy/deployer
[![Anlyon Radar](https://radar.anlyon.com/badge/com.thedploy/deployer.svg)](https://radar.anlyon.com/servers/com.thedploy/deployer)

Source: MCP Registry · repository. Synced Oct 31, 2026, 16:17 UTC.

The Deployer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the The Deployer MCP server safe?

No scan can promise that. What its definitions show: 17 tools, 13 of which can change, send or delete something, and 3 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the The Deployer MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: redeploy, launch and api.

Can the The Deployer MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the The Deployer MCP server have?

17 tools: 3 destructive, 10 write, 4 read. redeploy, launch, api, check_repo, plan_deploy, request_done_for_you, guide, account and 9 more.

Does the The Deployer MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the The Deployer MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the The Deployer MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.