# Cloud DevOps MCP Server (npm · cloud-devops-mcp-server)

Cloud DevOps analysis with guarded Git, infrastructure, cloud and observability operations.

- Trust score: 87/100 (high trust)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- npm · `cloud-devops-mcp-server`: 87/100 (this document), [markdown](https://verifymcp.io/servers/alexcgodwin-cloud-devops-mcp-server/cloud-devops-mcp-server.md), [page](https://verifymcp.io/servers/alexcgodwin-cloud-devops-mcp-server/cloud-devops-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `cloud-devops-mcp-server`
- Version: `0.14.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-10-16.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 15 of 56 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to alexcgodwin/cloud-devops-mcp-server).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2642 tokens (~220/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Cloud DevOps MCP Server server?

Cloud DevOps MCP Server runs locally as an npm package, launched with npx -y cloud-devops-mcp-server. 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 alexcgodwin-cloud-devops-mcp-server -- npx -y cloud-devops-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "alexcgodwin-cloud-devops-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "cloud-devops-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "alexcgodwin-cloud-devops-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "cloud-devops-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add alexcgodwin-cloud-devops-mcp-server -- npx -y cloud-devops-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alexcgodwin-cloud-devops-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "cloud-devops-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add alexcgodwin-cloud-devops-mcp-server --command npx --arg -y --arg cloud-devops-mcp-server
```

### Hermes

```yaml
mcp_servers:
  alexcgodwin-cloud-devops-mcp-server:
    command: "npx"
    args: ["-y", "cloud-devops-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "alexcgodwin-cloud-devops-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "cloud-devops-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add alexcgodwin-cloud-devops-mcp-server -t stdio -c npx -a -y cloud-devops-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "alexcgodwin-cloud-devops-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "cloud-devops-mcp-server"
      ]
    }
  }
}
```

## 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-10-15 (score 87, +1)

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

### 2026-10-13 (score 86, +1)

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

### 2026-10-12 (score 85, +16)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Security disclosure: unverified → pass

### 2026-10-11 (score 69, −12)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: pass → unverified

### 2026-10-03 (score 81, +26)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.90

### 2026-10-02 (score 55, +4)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 6% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Dependency health: unverified → 0.90
- [functional] Schema quality: fair → excellent
- [functional] Package version: 0.4.0 → 0.14.0
- [functional] Package version: 0.4.0 → 0.13.0
- [functional] Package version: 0.4.0 → 0.12.0
- [functional] Package version: 0.4.0 → 0.11.0
- [functional] Package version: 0.4.0 → 0.10.0
- [functional] Package version: 0.4.0 → 0.8.1
- [functional] Package version: 0.4.0 → 0.7.0

### 2026-10-01 (score 51)

First indexed and scored.

## MCP tools (12)

### `assess_terraform_change` (~253 tokens)

Assess Terraform Change

Evaluate Terraform/IaC release risk using plan evidence plus change-governance facts such as rollback, peer review and stateful impact. Use this for overall change/release decisions; for security-only inspection of a raw Terraform plan, use review_terraform_security. It analyzes supplied evidence only and never applies a plan, changes infrastructure, or writes Terraform state.

Input parameters:

- `changedResources` (array): Infrastructure resource classes changed by the pull request or deployment.
- `hasPeerReview` (boolean): Whether another qualified reviewer has reviewed the proposed change.
- `hasRollbackPlan` (boolean): Whether a documented rollback or recovery path exists for this change.
- `hasTerraformPlan` (boolean): Whether a Terraform plan artifact was generated and reviewed for this change.
- `includesIamChanges` (boolean): Whether the change adds, removes or modifies IAM permissions, roles or policies.
- `includesPublicIngress` (boolean): Whether the change introduces or modifies internet-accessible ingress or public network exposure.
- `modifiesStatefulResources` (boolean): Whether databases, persistent volumes or other stateful resources are changed or replaced.
- `terraformPlanJson` (string): Optional raw Terraform plan JSON. When supplied, the server derives resource classes and evidence.

Output parameters:

- `assessmentConfidence` (string)
- `changedResources` (array)
- `checklist` (array)
- `evidence` (array)
- `recommendedReleasePath` (string)
- `riskLevel` (string)
- `riskScore` (number)
- `uncertainties` (array)

### `assess_cloud_change_bundle` (~222 tokens)

Assess Cloud Change Bundle

Correlate evidence from at least two domains (Terraform, IAM, Kubernetes, GitHub Actions) into one deployment-risk assessment and identify cross-domain change paths. Use domain-specific review tools when only one evidence domain is available. It analyzes caller-supplied artifacts only and does not query providers, clusters, GitHub, or deploy changes.

Input parameters:

- `changeName` (string, required): Name or identifier for the cloud change bundle being assessed.
- `environment` (string, required): Target deployment environment; production increases the consequence of correlated risk.
- `githubWorkflows` (array): Optional GitHub Actions evidence domain with up to 10 workflows; combine with at least one other domain.
- `iamPolicies` (array): Optional IAM evidence domain with up to 10 policies; combine with at least one other domain.
- `kubernetesWorkloads` (array): Optional Kubernetes evidence domain with up to 10 workloads; combine with at least one other domain.
- `terraform` (object): Optional Terraform evidence domain. Supply this plus at least one other domain for cross-domain assessment.

Output parameters:

- `assessmentConfidence` (string)
- `baseRiskScore` (number)
- `bundleRiskLevel` (string)
- `bundleRiskScore` (number)
- `changeName` (string)
- `changePaths` (array)
- `correlatedFindingCount` (number)
- `correlatedFindings` (array)
- `correlationAdjustment` (number)
- `domainSummary` (array)
- `environment` (string)
- `environmentRiskAdjustment` (number)
- `recommendedActions` (array)
- `releaseGate` (string)
- `suppliedDomains` (array)
- `uncertainties` (array)

### `build_incident_runbook` (~150 tokens)

Build Incident Runbook

Generate a practical incident-response runbook from a known service symptom, severity, environment and optional signals. Use this to structure response actions and evidence collection; do not use it to fetch or diagnose from live telemetry. It does not execute remediation or make changes to the service.

Input parameters:

- `environment` (string, required): Environment where the symptom is occurring.
- `service` (string, required): Service or application name affected by the incident.
- `severity` (string, required): Incident severity used to scale response urgency and communications.
- `signals` (array): Optional known alerts, metrics, logs or traces that should guide triage.
- `symptom` (string, required): Observed user-facing or operational symptom to build the runbook around.

Output parameters:

- `communication` (array)
- `context` (object)
- `firstFifteenMinutes` (array)
- `mitigation` (array)
- `rcaEvidence` (array)
- `title` (string)
- `triageSteps` (array)

### `review_cicd_pipeline` (~224 tokens)

Review CI/CD Pipeline

Evaluate generic CI/CD production-readiness controls from structured pipeline facts, separating missing evidence from failed controls. Use this for platform-agnostic delivery process review; for raw GitHub Actions YAML, use review_github_actions_workflow. It is analysis-only and does not trigger builds, deployments, approvals, or pipeline changes.

Input parameters:

- `deploymentStrategy` (string, required): Primary deployment strategy used to release changes.
- `environments` (array, required): Deployment environments handled by the pipeline, for example dev, staging and production.
- `hasArtifactVersioning` (boolean): Whether build artifacts are immutable and versioned for traceability.
- `hasAutomatedTests` (boolean): Whether automated tests run as a release gate.
- `hasManualApprovalForProduction` (boolean): Whether production deployment requires an explicit human approval gate.
- `hasRollback` (boolean): Whether the pipeline has a defined rollback or recovery mechanism.
- `hasSecurityScan` (boolean): Whether the pipeline performs automated security scanning before deployment.
- `pipelineName` (string, required): Human-readable name of the CI/CD pipeline being reviewed.

Output parameters:

- `assessmentConfidence` (string)
- `deploymentStrategy` (string)
- `findings` (array)
- `pipelineName` (string)
- `readinessLevel` (string)
- `readinessScore` (number)
- `recommendedGates` (array)
- `strengths` (array)
- `uncertainties` (array)

### `estimate_slo_error_budget` (~166 tokens)

Estimate SLO Error Budget

Calculate remaining SLO downtime budget and, when request counts are supplied, remaining failed-request budget for a fixed period. Use this as a deterministic budget calculator; do not use it to fetch monitoring data or forecast reliability. It performs no external calls and changes no service state.

Input parameters:

- `failedRequests` (integer): Optional failed request count; provide together with requestVolume.
- `observedDowntimeMinutes` (number, required): Downtime already observed during the measurement period, in minutes.
- `periodDays` (integer, required): Length of the SLO measurement period in calendar days.
- `requestVolume` (integer): Optional total request count for calculating a request-failure error budget.
- `sloTargetPercent` (number, required): Target service availability percentage for the measurement period, such as 99.9.

Output parameters:

- `allowedDowntimeMinutes` (number)
- `allowedFailedRequests` (number)
- `budgetStatus` (string)
- `failedRequests` (number)
- `observedDowntimeMinutes` (number)
- `periodDays` (number)
- `remainingDowntimeMinutes` (number)
- `remainingFailedRequests` (number)
- `sloTargetPercent` (number)

### `review_iam_policy` (~264 tokens)

Review IAM Policy

Evaluate AWS IAM policy risk from structured facts or raw policy JSON, including wildcard scope, privilege-escalation actions and conditions. Use this for AWS IAM operational risk; for provider-specific AWS/Azure/GCP policy-pack checks, use review_cloud_identity_policy. It analyzes supplied policy data only and does not call AWS or modify IAM.

Input parameters:

- `actions` (array): Explicit allowed IAM actions when raw policy JSON is not supplied.
- `allowsPrivilegeEscalationActions` (boolean): Whether the policy contains actions that can enable privilege escalation.
- `hasConditionBlocks` (boolean): Whether policy statements include Condition constraints that narrow access.
- `hasWildcardActions` (boolean): Whether the policy permits wildcard actions such as * or service:* patterns.
- `hasWildcardResources` (boolean): Whether the policy grants permissions against wildcard resources.
- `policyJson` (string): Raw AWS IAM policy JSON. When supplied, the server derives actions, resources, wildcard scope and privilege-escalation evidence.
- `policyName` (string, required): Name of the AWS IAM policy being assessed.
- `resources` (array): Explicit IAM resource ARNs or patterns when raw policy JSON is not supplied.
- `usedByProduction` (boolean): Whether the policy is attached to or used by production identities or workloads.

Output parameters:

- `actions` (array)
- `assessmentConfidence` (string)
- `evidence` (array)
- `findings` (array)
- `policyName` (string)
- `recommendedControls` (array)
- `resources` (array)
- `riskLevel` (string)
- `riskScore` (number)
- `strengths` (array)
- `uncertainties` (array)

### `review_kubernetes_deployment` (~301 tokens)

Review Kubernetes Deployment

Evaluate Kubernetes workload production readiness and reliability from structured facts or multi-document YAML, including probes, resources, replicas, disruption protection and exposure. Use this for deployability/readiness; for workload security hardening, use review_kubernetes_security. It examines supplied evidence only and does not connect to a Kubernetes cluster.

Input parameters:

- `exposesPublicService` (boolean): Whether the workload is exposed through a public Service or ingress path.
- `hasLivenessProbe` (boolean): Whether workload containers define liveness probes.
- `hasPodDisruptionBudget` (boolean): Whether a PodDisruptionBudget protects workload availability during voluntary disruption.
- `hasReadinessProbe` (boolean): Whether workload containers define readiness probes.
- `hasResourceLimits` (boolean): Whether workload containers define CPU or memory limits.
- `hasResourceRequests` (boolean): Whether workload containers define CPU or memory requests.
- `manifestYaml` (string): Deployment, StatefulSet or DaemonSet YAML, optionally with Service, Ingress and PodDisruptionBudget documents.
- `namespace` (string): Kubernetes namespace containing the workload.
- `replicas` (integer): Configured replica count used to assess availability and redundancy.
- `runsAsRoot` (boolean): Whether the workload is configured to run containers as root.
- `usesLatestTag` (boolean): Whether any container image uses the mutable latest tag.
- `workloadName` (string): Workload name when raw manifest YAML is not the only source of identity.

Output parameters:

- `assessmentConfidence` (string)
- `evidence` (array)
- `findings` (array)
- `namespace` (string)
- `readinessLevel` (string)
- `readinessScore` (number)
- `recommendedControls` (array)
- `strengths` (array)
- `uncertainties` (array)
- `workloadName` (string)

### `review_github_actions_workflow` (~292 tokens)

Review GitHub Actions Workflow

Evaluate GitHub Actions workflow security and deployment readiness from structured facts or raw workflow YAML, including triggers, action pinning, token permissions, caching, environment protection and concurrency. Use review_cicd_pipeline for generic non-GitHub delivery-process review. It examines supplied evidence only and does not call GitHub or dispatch workflows.

Input parameters:

- `deploysToProduction` (boolean): Whether the workflow can deploy directly or indirectly to production.
- `hasConcurrencyControl` (boolean): Whether concurrency settings prevent overlapping or conflicting workflow runs.
- `hasDependencyCaching` (boolean): Whether dependency caching is configured for repeatable and efficient builds.
- `hasEnvironmentProtection` (boolean): Whether protected GitHub environments or equivalent approval controls guard production deployments.
- `hasLeastPrivilegePermissions` (boolean): Whether GITHUB_TOKEN permissions are explicitly restricted to least privilege.
- `hasSecretScanning` (boolean): Whether the workflow or surrounding delivery process performs automated secret scanning.
- `triggers` (array): Workflow trigger events when raw YAML is not supplied, such as push, pull_request or workflow_dispatch.
- `usesPinnedActions` (boolean): Whether third-party actions are pinned to immutable commit SHAs.
- `workflowName` (string, required): Human-readable name of the GitHub Actions workflow being reviewed.
- `workflowYaml` (string): Raw GitHub Actions workflow YAML. The server derives triggers, action pinning, token permissions, caching and concurrency.

Output parameters:

- `assessmentConfidence` (string)
- `evidence` (array)
- `findings` (array)
- `readinessLevel` (string)
- `recommendedControls` (array)
- `strengths` (array)
- `triggers` (array)
- `uncertainties` (array)
- `workflowName` (string)
- `workflowScore` (number)

### `review_cloud_identity_policy` (~165 tokens)

Review Cloud Identity Policy

Apply deterministic provider-specific identity policy packs to raw AWS IAM, Azure RBAC or GCP IAM policy documents. Use this for cross-cloud identity security analysis; use review_iam_policy when assessing AWS IAM from mixed structured facts or policy JSON. It analyzes supplied policy JSON only and does not call cloud APIs or change permissions.

Input parameters:

- `environment` (string): Optional deployment environment used to contextualize policy risk; defaults are handled by the policy pack.
- `policyJson` (string, required): Raw provider policy document in JSON form; AWS IAM, Azure role definition/assignment data, or GCP IAM policy.
- `policyName` (string, required): Name or identifier of the identity policy being reviewed.
- `provider` (string, required): Cloud provider whose identity policy syntax and policy pack should be applied.

Output parameters:

- `assessmentConfidence` (string)
- `criticalFindings` (number)
- `environment` (string)
- `facts` (array)
- `findingCount` (number)
- `findings` (array)
- `highFindings` (number)
- `mediumFindings` (number)
- `policyName` (string)
- `policyPack` (string)
- `provider` (string)
- `recommendedGate` (string)
- `riskLevel` (string)
- `riskScore` (number)

### `review_terraform_security` (~121 tokens)

Review Terraform Security

Inspect raw Terraform plan JSON for security-relevant changes such as destructive actions, public exposure, encryption gaps, deletion protection and IAM wildcard risk. Use this for Terraform security posture; use assess_terraform_change for broader release/change risk and governance. It parses the supplied plan only and does not execute Terraform or write state.

Input parameters:

- `environment` (string): Optional target environment used to contextualize the severity of findings.
- `terraformPlanJson` (string, required): Raw Terraform plan JSON, typically produced by terraform show -json, to inspect for security-relevant resource changes.

Output parameters:

- `assessmentConfidence` (string)
- `changedResources` (number)
- `criticalFindings` (number)
- `destructiveChanges` (number)
- `environment` (string)
- `findingCount` (number)
- `findings` (array)
- `highFindings` (number)
- `mediumFindings` (number)
- `policyPack` (string)
- `recommendedGate` (string)
- `replacements` (number)
- `riskLevel` (string)
- `riskScore` (number)

### `review_kubernetes_security` (~115 tokens)

Review Kubernetes Security

Apply Kubernetes workload security rules to manifest YAML for privileged mode, host access, Linux capabilities, service accounts, seccomp, filesystem settings and network policy. Use this for security hardening; use review_kubernetes_deployment for reliability and production-readiness checks. It analyzes supplied YAML only and does not connect to a cluster.

Input parameters:

- `environment` (string): Optional target environment used to contextualize security findings.
- `manifestYaml` (string, required): Raw multi-document Kubernetes YAML containing workloads and related policy objects to evaluate for security hardening.

Output parameters:

- `assessmentConfidence` (string)
- `criticalFindings` (number)
- `environment` (string)
- `findingCount` (number)
- `findings` (array)
- `highFindings` (number)
- `mediumFindings` (number)
- `networkPolicyPresent` (boolean)
- `policyPack` (string)
- `publicExposureObjects` (number)
- `recommendedGate` (string)
- `riskLevel` (string)
- `riskScore` (number)
- `workloadCount` (number)

### `review_software_supply_chain` (~212 tokens)

Review Software Supply Chain

Correlate CycloneDX/SPDX SBOM quality with CI action pinning, Kubernetes image immutability, artifact signing and build provenance to assess software-supply-chain risk. Use this when an SBOM is available and supply-chain evidence needs to be evaluated together. It analyzes supplied artifacts only and does not call registries, CI systems, or clusters.

Input parameters:

- `artifactSigned` (boolean): Whether released artifacts or images are cryptographically signed.
- `environment` (string): Optional target environment used to contextualize supply-chain risk.
- `hasProvenance` (boolean): Whether verifiable build provenance or attestation is produced for released artifacts.
- `kubernetesManifestYaml` (string): Optional Kubernetes manifest YAML used to inspect runtime image immutability.
- `sbomJson` (string, required): CycloneDX or SPDX SBOM JSON used as the primary software-supply-chain evidence.
- `workflowYaml` (string): Optional GitHub Actions workflow YAML used to inspect action pinning and build controls.

Output parameters:

- `artifactSigned` (boolean|null)
- `assessmentConfidence` (string)
- `componentCount` (number)
- `correlationPaths` (array)
- `criticalFindings` (number)
- `environment` (string)
- `findingCount` (number)
- `findings` (array)
- `hasProvenance` (boolean|null)
- `highFindings` (number)
- `mediumFindings` (number)
- `metadataCoverage` (object)
- `mutableActionReferences` (boolean)
- `mutableRuntimeImages` (boolean)
- `policyPack` (string)
- `recommendedGate` (string)
- `riskLevel` (string)
- `riskScore` (number)
- `sbomFormat` (string)
- `sbomSpecVersion` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/alexcgodwin-cloud-devops-mcp-server/cloud-devops-mcp-server#diagnostics

## Score history

- 2026-10-16: 87
- 2026-10-15: 87
- 2026-10-14: 86
- 2026-10-13: 86
- 2026-10-12: 85
- 2026-10-11: 69
- 2026-10-04: 81
- 2026-10-03: 81
- 2026-10-02: 55
- 2026-10-01: 51

## Common questions

### What is the Cloud DevOps MCP Server server?

Cloud DevOps MCP Server is listed in the public MCP registry as io.github.alexcgodwin/cloud-devops-mcp-server. Cloud DevOps analysis with guarded Git, infrastructure, cloud and observability operations. This page covers its npm package (cloud-devops-mcp-server).

### Is the Cloud DevOps MCP Server server safe to use?

Cloud DevOps MCP Server scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Cloud DevOps MCP Server server expose?

Cloud DevOps MCP Server exposes 12 tools: assess_terraform_change, assess_cloud_change_bundle, build_incident_runbook, review_cicd_pipeline, estimate_slo_error_budget, and 7 more. Their descriptions and schemas cost roughly 2,485 tokens of context every time the server is loaded.

### Is the Cloud DevOps MCP Server server still maintained?

Cloud DevOps MCP Server is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Cloud DevOps MCP Server server under?

Cloud DevOps MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/cloud-devops-mcp-server
- Socket report: https://socket.dev/npm/package/cloud-devops-mcp-server
- Repository: https://github.com/alexcgodwin/cloud-devops-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/alexcgodwin-cloud-devops-mcp-server/cloud-devops-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/alexcgodwin-cloud-devops-mcp-server/cloud-devops-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/alexcgodwin-cloud-devops-mcp-server/cloud-devops-mcp-server