Octopus Deploy MCP Server
@octopusdeploy/mcp-server
npm
v2.3.2
Source verified
Published by octopusdeploy — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Official Octopus Deploy server that lets AI assistants inspect, query, and diagnose problems within an Octopus instance.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
medium Unconstrained URL/host parameter "url" on "get_deployment_from_url"MTC-CAP-007
Tool "get_deployment_from_url" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool get_deployment_from_url · inputSchema.properties.url
medium Unconstrained URL/host parameter "uri" on "read_resource"MTC-CAP-007
Tool "read_resource" takes a URL/host parameter "uri" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool read_resource · inputSchema.properties.uri
Tools 30
Each tool and what it can reach — statically extracted from the published source.
find_interruptionsingests untrusted inputfind_releasesingests untrusted inputfind_runbooksingests untrusted inputget_deployment_from_urlingests untrusted inputread_resourceingests untrusted inputcreate_releaseno sensitive capabilitydeploy_releaseno sensitive capabilityexecuteno sensitive capabilityfind_accountsno sensitive capabilityfind_certificatesno sensitive capability
Show 20 more tools ↓
find_deployment_targetsno sensitive capabilityfind_eventsno sensitive capabilityfind_feature_togglesno sensitive capabilityfind_tenantsno sensitive capabilityget_branchesno sensitive capabilityget_current_userno sensitive capabilityget_deployment_processno sensitive capabilityget_kubernetes_live_statusno sensitive capabilityget_missing_tenant_variablesno sensitive capabilityget_task_from_urlno sensitive capabilityget_tenant_variablesno sensitive capabilityget_variablesno sensitive capabilitygrep_llms_txtno sensitive capabilitygrep_task_logno sensitive capabilitylist_deploymentsno sensitive capabilitylist_environmentsno sensitive capabilitylist_projectsno sensitive capabilitylist_spacesno sensitive capabilityrun_runbookno sensitive capabilityupdate_feature_toggleno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (30 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.3.2 latest |
A 97/100 | 2 | 1.13.0 | 2026-08-25 |
v2.3.1 |
A 97/100 | 2 | 1.12.1 | 2026-07-27 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @octopusdeploy/mcp-server --onlineMore in Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.