dingdawg-devops-agent
FlaggedDevOps AI. Deploy checks, incident analysis, infra audit. Learns from past failures.
Our take
The published npm package is a real MCP server, but the registry points users to `dingdawg/dingdawg-agent-1`, a different ISG/DingDawg governance platform repo that does not contain this DevOps MCP package. The package metadata points to `dingdawg/dingdawg-devops-agent`, and that repository is 404, so the advertised source cannot be audited from the listing. That is submitted-source/package-source misrepresentation, not just stale branding.
Verification record
- today
- 1
- 2 mo ago
- no
- MIT
- 2.0.9
- 2026-04-09