Dingdawg Devops Agent

io.github.dingdawgPublished by GitHub account dingdawgv2.0.7Updated Oct 24, 2026

DevOps AI. Deploy checks, incident analysis, infra audit. Learns from past failures.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local DevOps agent that runs deploy checks, incident analysis, and infrastructure audits, with governed execution and signed audit receipts.

What you can do
DingDawg Devops Agent is a local stdio MCP server for DevOps work: deploy checks, incident analysis, and infrastructure audits, with the claim that it learns from past failures. The README describes a broader governance platform behind it, including governed execution that meters and audits agent calls, compliance classification, regulation lookup, agent trust scores, and signed receipts for each action. It is one of a family of governed-agent packages covering areas such as compliance, finance, and code review.
When to use it
Consider it if you want an assistant to help with deployment verification, incident triage, or infrastructure review, and you also want those actions recorded as auditable receipts. It is less relevant if you only need plain DevOps tooling without governance or metering.
Requirements
Runs as a local process, installed from the npm package dingdawg-devops-agent and started with npx. Requires Node.js and network access to the provider's API. An API key is supplied through the environment variable DINGDAWG_API_KEY; the README says a scoped key is issued by a developer signup endpoint and shown once. Desktop only.
Before you install
The API key DINGDAWG_API_KEY is a secret and is shown only once at signup, so store it securely. The README describes metering, billing through Stripe, and paid tier access, so usage may cost money. Governed execution routes agent calls through the provider's servers, meaning prompts and actions may be sent to and logged by a third party. Audit receipts and trust scores are generated and stored by that service.

Installation

In SourceWeft

  1. Open Dingdawg Devops Agent in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

DingDawg Agent 1

[License: MIT] [Python 3.11+]

Governance receipts for AI agents.

Every action a governed agent takes generates a cryptographically-signed receipt: what it decided, why, which model, which version, at what time. Built toward EU AI Act Art. 12, Colorado AI Act (SB 24-205), and NIST AI RMF requirements.

The receipt is what turns a policy document into evidence.

What's live today

CapabilityEndpoint
Developer signup — issues a scoped API keyPOST /v1/developers/signup
Governed execution — routes agent calls through metering + auditPOST /v1/govern/execute
Compliance classificationPOST /api/v1/compliance/classify
Regulation lookupGET /api/v1/compliance/regulations
Agent trust score + live streamGET /api/v1/agents/{id}/trust, WS .../trust/stream
Billing (Stripe)POST /api/v1/payments/create-checkout-session

Backed by 10 governed-agent npm packages (compliance, legal, healthcare, finance, devops, marketing, sales, support, code-review, planning).

Quickstart

bash
curl -X POST https://api.dingdawg.com/v1/developers/signup \  -H "Content-Type: application/json" \  -d '{"email":"[email protected]","name":"Your Name","role":"consumer"}'# -> {"api_key": "dd_...", ...}  store it — shown once
bash
export DINGDAWG_API_KEY=dd_your_keynpx dingdawg-compliance quick-check

Architecture

Client (npm package / your agent) --auth: DINGDAWG_API_KEY-->  api.dingdawg.com (FastAPI, Railway)    -> Tier isolation + rate limiting    -> Governance gate (score, log, decide)    -> Audit trail (signed receipt)    -> Stripe metering / billing  -> Response (governed, scored, receipted)

Documentation

Contributing

See CONTRIBUTING.md for contribution guidelines.

Security

See SECURITY.md for our responsible disclosure policy.

License

MIT License. See LICENSE for details.

Innovative Systems Global. The name is not aspirational. It is a statement of fact.

Source: README.md at commit 0489d0b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.0.7LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts