dingdawg-data-agent

Name: dingdawg-data-agent
Author: dingdawg

Local

github.com/dingdawgDatabases1Updated 12w ago

Repository

About dingdawg-data-agent

dingdawg-data-agent is presented in the supplied README as a governance service for AI agents, rather than with data-agent capabilities. It routes agent calls through governance checks and records decisions in signed audit receipts.

Key features

01Signed receipts for agent actions
02Governed execution with metering and audit
03Compliance classification and regulation lookup
04Agent trust scores and live stream

Use cases

01Recording evidence of agent decisions
02Reviewing an agent’s trust score
03Classifying compliance requirements

MCP support

The input describes HTTP API endpoints and npm packages but does not specify an MCP 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-data-agent": {
      "command": "npx",
      "args": [
        "-y",
        "dingdawg-data-agent"
      ],
      "env": {
        "DINGDAWG_API_KEY": "<DINGDAWG_API_KEY>"
      }
    }
  }
}

Run commandnpx -y dingdawg-data-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-data-agent2.0.7stdio

Tools

Saved tool list · updated 2w ago

Parameter	Type	Required	Description
schema	string	Yes	Dataset schema, DDL, or description of your data
database	string	No	Database type (postgres, mysql, sqlite, mongodb, etc.)

Details

From the project README

DingDawg Agent 1

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

Capability	Endpoint
Developer signup — issues a scoped API key	`POST /v1/developers/signup`
Governed execution — routes agent calls through metering + audit	`POST /v1/govern/execute`
Compliance classification	`POST /api/v1/compliance/classify`
Regulation lookup	`GET /api/v1/compliance/regulations`
Agent trust score + live stream	`GET /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.

Read the getting-started guide

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.