Dingdawg Legal Agent

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

AI contract review, clause drafting, compliance checklists & legal research.

Overview

AI-generated overview

Local npm MCP server for Dingdawg's legal agent: AI contract review, clause drafting, compliance checklists and legal research, backed by a metered API.

What you can do
  • Review contracts and draft clauses through the Dingdawg legal agent
  • Run compliance checks and classification against regulations
  • Look up regulations and retrieve legal research material
  • Route agent calls through governed execution that logs and scores each action
  • Generate signed governance receipts and agent trust scores
  • Manage developer signup and billing through the hosted API
When to use it
Worth adding when an assistant should help with contract review, clause drafting, compliance checklists or regulation lookup, and when you want those calls metered and recorded as audit receipts.
Requirements
Runs as a local stdio process via the npm package dingdawg-legal-agent (Node.js with npx). Needs a DINGDAWG_API_KEY environment variable, obtained by signing up with an email at the provider's developer endpoint; the key is shown once. Network access to the provider's API is required.
Before you install
The API key is a secret passed in DINGDAWG_API_KEY and grants access to a paid tier, so billing and Stripe metering may apply. Contract text and other prompts are sent to the provider's hosted API for governance, scoring and audit logging. Signup requires an email address, and the key is displayed only once.

Installation

In SourceWeft

  1. Open Dingdawg Legal 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