Dingdawg Marketing Agent

io.github.dingdawgPublished by GitHub account dingdawgv2.0.6Updated Oct 27, 2026

AI content generation, SEO audits, campaign planning & social scheduling.

Overview

AI-generated overview

Local npm MCP server that routes an assistant's agent calls through Dingdawg's metered governance API, producing signed audit receipts.

What you can do
  • Route agent calls through a governed execution endpoint that scores, logs and receipts each action
  • Generate cryptographically signed governance receipts recording decisions, model and version
  • Classify compliance and look up regulations for AI governance frameworks
  • Retrieve an agent's trust score and follow a live trust stream
  • Create Stripe checkout sessions for metered billing
  • Sign up as a developer to obtain a scoped API key
When to use it
Worth considering if you need auditable evidence of what an AI agent did and why, for example to support EU AI Act, Colorado AI Act or NIST AI RMF compliance work, or if you want metered, receipted execution of agent calls through a hosted service.
Requirements
Runs locally over stdio via the npm package dingdawg-marketing-agent (Node.js/npx). Requires a DINGDAWG_API_KEY, obtainable through a developer signup endpoint, and network access to the provider's hosted API.
Before you install
The API key is a secret sent to the provider's API and is shown only once at signup. Calls are metered and billed through Stripe, so usage can cost money. Agent actions and their details are sent to a third-party service and logged in its audit trail.

Installation

In SourceWeft

  1. Open Dingdawg Marketing 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.6LatestSep 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