dingdawg-shield

MCPcommunity
v1.0.9Innovative Systems GlobalBUSL-1.1Updated 4mo agonpmGitHub

Governance receipts for AI agents — AI-driven security scanning with a stack-specific threat model, signed audit receipts for every scan, and trust scores that improve with verified fixes. Supports EU AI Act, Colorado AI Act (SB 24-205), and NIST AI RMF a

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
42Downloads/wk
4mo agoLast update
Reads these credentials
  • DINGDAWG_API_KEYAPI keyoptional

    API key for paid tier access — get free at dingdawg.com

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorInnovative Systems Global
LicenseBUSL-1.1
Version1.0.9
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv1.0.9 · 3d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged
Statically extracted from the published packagev1.0.9 · 3d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

security_scanScan a codebase for AI security vulnerabilities. Free tier: 1 local scan per day. Checks SQL injection, XSS, SSRF, path traversal, prompt injection, hardcoded secrets, insecure deserialization, missing auth, data leakage, and more.

Scan a codebase for AI security vulnerabilities. Free tier: 1 local scan per day. Checks SQL injection, XSS, SSRF, path traversal, prompt injection, hardcoded secrets, insecure deserialization, missing auth, data leakage, and more.

No input schema was published for this tool.

governance_checkCheck if an AI system meets governance requirements. Evaluates transparency, accountability, fairness, safety, and privacy controls. Free — runs locally.

Check if an AI system meets governance requirements. Evaluates transparency, accountability, fairness, safety, and privacy controls. Free — runs locally.

No input schema was published for this tool.

trust_scoreGet a quantified trust score for an AI agent or system. $0.05 per check via API, or free local assessment. Returns a 0-100 score with breakdown across reliability, safety, transparency, fairness, and accountability.

Get a quantified trust score for an AI agent or system. $0.05 per check via API, or free local assessment. Returns a 0-100 score with breakdown across reliability, safety, transparency, fairness, and accountability.

No input schema was published for this tool.

3 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Governance receipts for AI agents — AI-driven security scanning with a stack-specific threat model, signed audit receipts for every scan, and trust scores that improve with verified fixes. Supports EU AI Act, Colorado AI Act (SB 24-205), and NIST AI RMF a

Keywords
mcpai-securityvulnerability-scanningtrust-scoregovernancedingdawgclaude-codecursorai-agentgovernance-receiptsreceiptsaudit-trailtamper-proofai-governanceresponsible-aillm-governancesigned-receiptsai-agentseu-ai-actcompliancemodel-context-protocol
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in security