Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.dingdawg/dingdawg-compliance

NPM · DINGDAWG-COMPLIANCE

EU AI Act + Colorado AI Act compliance scoring. 87/100 in 60 seconds. Free local scan.

Available components

0 this week 80 Trust /100

Last scanned (15 hours ago)

Scores higher than 66% of npm servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency26
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 258 tokens (~64/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 4 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.97 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/dingdawg-compliance@2.0.11

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~258 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_status ~37

Check the status of a compliance report. Requires DINGDAWG_API_KEY.

NameTypeReqDescription
report_idstringyesReport ID from generate_report

No output schema declared.

No examples provided.

generate_report ~111

Generate a full AI compliance report via DingDawg API. Requires DINGDAWG_API_KEY. LLM-powered analysis with legal citations, remediation steps, and certification docs. Tiers: starter=$199, standard=$499, pro=$999, enterprise=$1499.

NameTypeReqDescription
ai_system_descriptionstringyesAI system description for assessment
company_namestringyesCompany name for the report
emailstringyesEmail to receive the report
tierstringyesReport tier

No output schema declared.

No examples provided.

list_frameworks ~19

List available compliance frameworks and what each tier covers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

quick_check ~91

Free AI compliance quick check. Scores your system against EU AI Act and Colorado ADMT Law (SB26-189). Returns top findings locally. Deep LLM-powered remediation available with API key.

NameTypeReqDescription
ai_system_descriptionstringyesDescribe your AI system: what it does, what data it uses, who it affects
industrystring–Your industry (healthcare, finance, education, etc.)

No output schema declared.

No examples provided.

Install

How do I install the io.github.dingdawg/dingdawg-compliance MCP server?

io.github.dingdawg/dingdawg-compliance runs locally as an npm package, launched with npx -y dingdawg-compliance. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · dingdawg-compliance

# add to Claude Code
claude mcp add dingdawg-dingdawg-compliance -- npx -y dingdawg-compliance
Common questions

What is the io.github.dingdawg/dingdawg-compliance MCP server?

io.github.dingdawg/dingdawg-compliance is an MCP server listed in the public MCP registry as io.github.dingdawg/dingdawg-compliance. EU AI Act + Colorado AI Act compliance scoring. 87/100 in 60 seconds. Free local scan. This page covers its npm package (dingdawg-compliance).

Is the io.github.dingdawg/dingdawg-compliance MCP server safe to use?

io.github.dingdawg/dingdawg-compliance scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.dingdawg/dingdawg-compliance MCP server expose?

io.github.dingdawg/dingdawg-compliance exposes 4 tools: quick_check, generate_report, list_frameworks, check_status. Their descriptions and schemas cost roughly 258 tokens of context every time the server is loaded.

Is the io.github.dingdawg/dingdawg-compliance MCP server still maintained?

io.github.dingdawg/dingdawg-compliance is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.dingdawg/dingdawg-compliance MCP server under?

io.github.dingdawg/dingdawg-compliance declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the io.github.dingdawg/dingdawg-compliance MCP server?

VerifyMCP ran 16 checks on io.github.dingdawg/dingdawg-compliance, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.