mcpField
D
dingdawg-devops-agent

dingdawg-devops-agent

Local
github.com/dingdawgCloud & Infra1Updated 12w ago

About dingdawg-devops-agent

dingdawg-devops-agent is a governed-agent package in the DingDawg system, with API endpoints for execution, compliance checks, regulation lookup, and agent trust scores. It is intended for teams building agents that need metered, auditable execution and signed governance receipts.

Key features

  1. 01Governed agent execution with audit logging
  2. 02Compliance classification and regulation lookup
  3. 03Agent trust scores and live stream
  4. 04Signed receipts for agent actions
  5. 05Scoped API key signup

Use cases

  1. 01Routing agent calls through governance checks
  2. 02Classifying activity for compliance review
  3. 03Monitoring agent trust scores
  4. 04Keeping signed records of agent decisions

MCP support

The input describes API endpoints and npm packages but does not specify an MCP server interface.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"dingdawg-dingdawg-devops-agent": {
"command": "npx",
"args": [
"-y",
"dingdawg-devops-agent"
],
"env": {
"DINGDAWG_API_KEY": "<DINGDAWG_API_KEY>"
}
}
}
}
Run commandnpx -y dingdawg-devops-agent
Environment variables to set
DINGDAWG_API_KEYSecretAPI key for paid tier access — get free at dingdawg.com

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmdingdawg-devops-agent2.0.7

Tools

5

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
configstringYesDeployment config content (Dockerfile, docker-compose, k8s manifest, railway.toml, vercel.json, etc.)
platformstringNoTarget platform (docker, k8s, railway, vercel, aws)

Details

From the project 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

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
export DINGDAWG_API_KEY=dd_your_key
npx 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.