io.github.dingdawg/dingdawg-devops-agent
NPM · DINGDAWG-DEVOPS-AGENT
DevOps AI. Deploy checks, incident analysis, infra audit. Learns from past failures.
Available components
Last scanned (19 hours ago)
Scores higher than 55% of npm servers
Category CI/CD and DevOps
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 120 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 362 tokens (~72/item across 5 items; 5 tools + 0 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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; "deploy_check" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 5 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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.87 → pass security
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 4 Nov 2026 · Analysed npm/dingdawg-devops-agent@2.0.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
cost_optimize ~69
AI-powered cloud cost optimization. Right-sizing, reserved instances, savings estimates. Requires DINGDAWG_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| cloud_provider | string | – | Cloud provider (aws, gcp, azure, railway, vercel) |
| services | string | yes | Service list with current resources and monthly costs |
No output schema declared.
No examples provided.
deploy_check ~90
Free pre-deployment verification. Scans for exposed secrets, insecure defaults, and missing health checks. Deep LLM-powered analysis with API key.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | Deployment config content (Dockerfile, docker-compose, k8s manifest, railway.toml, vercel.json, etc.) |
| platform | string | – | Target platform (docker, k8s, railway, vercel, aws) |
No output schema declared.
No examples provided.
incident_analyze ~78
AI-powered incident analysis from logs or metrics. Root cause analysis, severity classification, remediation steps. Requires DINGDAWG_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| logs | string | yes | Incident logs, error messages, or metrics dump |
| service | string | – | Affected service name |
| severity | string | – | Initial severity (sev1-sev4) |
No output schema declared.
No examples provided.
infra_audit ~54
AI infrastructure audit for security, cost, compliance, and reliability. Requires DINGDAWG_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | – | Audit focus area |
| infrastructure | string | yes | Infrastructure description or IaC file content |
No output schema declared.
No examples provided.
runbook_generate ~71
Generate operational runbooks with detection, triage, mitigation, and post-mortem steps. Requires DINGDAWG_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| failure_modes | string | – | Known failure modes |
| on_call_info | string | – | On-call escalation information |
| service | string | yes | Service name and description |
No output schema declared.
No examples provided.
How do I install the io.github.dingdawg/dingdawg-devops-agent MCP server?
io.github.dingdawg/dingdawg-devops-agent runs locally as an npm package, launched with npx -y dingdawg-devops-agent. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dingdawg-devops-agent
claude mcp add dingdawg-dingdawg-devops-agent -- npx -y dingdawg-devops-agent
What is the io.github.dingdawg/dingdawg-devops-agent MCP server?
io.github.dingdawg/dingdawg-devops-agent is an MCP server listed in the public MCP registry as io.github.dingdawg/dingdawg-devops-agent. DevOps AI. Deploy checks, incident analysis, infra audit. Learns from past failures. This page covers its npm package (dingdawg-devops-agent).
Is the io.github.dingdawg/dingdawg-devops-agent MCP server safe to use?
io.github.dingdawg/dingdawg-devops-agent scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.dingdawg/dingdawg-devops-agent MCP server expose?
io.github.dingdawg/dingdawg-devops-agent exposes 5 tools: deploy_check, incident_analyze, infra_audit, runbook_generate, cost_optimize. Their descriptions and schemas cost roughly 362 tokens of context every time the server is loaded.
Is the io.github.dingdawg/dingdawg-devops-agent MCP server still maintained?
io.github.dingdawg/dingdawg-devops-agent is still listed as active in the MCP registry. We last reached this channel on 4 November 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 io.github.dingdawg/dingdawg-devops-agent MCP server under?
io.github.dingdawg/dingdawg-devops-agent declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.