io.github.dingdawg/dingdawg-devops-agentcloud

dingdawg-devops-agent

Flagged

DevOps 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.

reviewed by hand · 2026-07-06

Something wrong or dead here? Report it

Verification record

last verified
today
github stars
1
last commit
2 mo ago
archived
no
license
MIT
latest version
2.0.9
in registry since
2026-04-09

github.com/dingdawg/dingdawg-agent-1