MCP.Market

Dingdawg Loop MCP server

by dingdawg·io.github.dingdawg/dingdawg-loop·v2.0.8
No reviews yet

Safe scheduled AI agents with governance gates. Verified, receipted, fail-closed.

B77/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
New

0 stars53 downloads/wk

Reviews

Write one

Nobody has reviewed Dingdawg Loop yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Dingdawg Loop tools (6, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • execute_loopwrite action

    Manually trigger a loop execution. ALWAYS runs the governance gate first — if governance denies or errors, the loop body does NOT execute. Returns the governance receipt and execution outcome. This is the core DDLP safety mechanism: declare intent, get governed, then act.

  • list_loops

    List all registered loops with their current status, schedule, risk tier, and last execution result. Use this to see what loops exist and their governance health.

  • loop_audit

    Get the execution history for a specific loop. Shows every governance decision, outcome, and timestamp. Use this to audit how a loop has been behaving over time.

  • pause_loop

    Pause a loop so it cannot be executed. Paused loops reject execute_loop calls until resumed. Use this to safely stop a loop without deleting its history.

  • register_loop

    Register a scheduled agent loop. Stores the loop definition with its cron schedule, action type, and risk tier. The loop is created in 'active' status but does NOT auto-execute in v1 — use execute_loop to trigger manually. The schedule is stored for v2 daemon support.

  • resume_loop

    Resume a paused loop so it can be executed again. Clears the pause reason from metadata.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 52 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Dingdawg Loop compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
17%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
53
more than 44% of 12,191 servers with a package

What its tools let an agent do: 4 read · 1 create · 1 run or deploy

Install Dingdawg Loop in Claude Code, Cursor or VS Code

Runs npx -y dingdawg-loop on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add dingdawg-loop -- npx -y dingdawg-loop
Add to Cursor

What the publisher says

From the Dingdawg Loop repository's README, as published. We do not edit it. Read it on GitHub

dingdawg-loop

DingDawg Loop Protocol (DDLP) — safe scheduled AI agents with governance gates.

Every loop execution is verified, receipted, and fail-closed. MCP-native. Works with CrewAI, LangGraph, Claude Code, and Cursor.

Install

npx dingdawg-loop

Or as an MCP server in Claude Desktop / Claude Code:

{
  "mcpServers": {
    "dingdawg-loop": {
      "command": "npx",
      "args": ["dingdawg-loop"]
    }
  }
}

What it does

DDLP wraps any scheduled agent action with a governance gate that:

  • Evaluates the loop description before execution
  • Blocks destructive, financial, or sensitive operations until policy thresholds are met
  • Signs every execution with an Ed25519 receipt
  • Provides full audit history per loop

MCP Tools

Governance gates

DDLP classifies every loop at registration time. High-risk categories require elevated approval:

  • Destructive operations — file deletion, database mutations, DROP statements
  • External communications — email sends, Slack messages, webhook calls
  • Financial operations — any spend, transfer, or payment action
  • Sensitive data access — PII reads, credential access, health records
  • Bulk operations — mass updates, batch sends, bulk deletes

Compatibility

Works with any MCP-compatible AI client:

  • Claude Desktop / Claude Code
  • Cursor
  • CrewAI (via MCP bridge)
  • LangGraph (via MCP bridge)

License

BUSL-1.1 — see LICENSE

Publisher

DingDawg Enterprise — hello@dingdawg.com — dingdawg.com

Nothing above is checked by us. What we check is on the safety report.

Dingdawg Loop: common questions

Is Dingdawg Loop MCP server safe?
Mostly: it is graded B (77/100). Read the Dingdawg Loop safety report
How do I install Dingdawg Loop?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Dingdawg Loop need an API key?
Yes. The registry entry asks for DINGDAWG_API_KEY.
Is Dingdawg Loop maintained?
The last commit was 90 days ago (2026-08-06). The latest release is v2.0.8.
How does Dingdawg Loop compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from dingdawg →