# io.github.dingdawg/dingdawg-loop (npm · dingdawg-loop)

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

- Trust score: 69/100 (medium)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- npm · `dingdawg-loop`: 69/100 (this document), [markdown](https://verifymcp.io/servers/dingdawg-dingdawg-loop/dingdawg-loop.md), [page](https://verifymcp.io/servers/dingdawg-dingdawg-loop/dingdawg-loop)

## Channel facts

- Registry: `npm`
- Package: `dingdawg-loop`
- Version: `2.0.8`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 576 tokens (~96/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add dingdawg-dingdawg-loop -- npx -y dingdawg-loop
```

### Codex

```bash
codex mcp add dingdawg-dingdawg-loop -- npx -y dingdawg-loop
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dingdawg-dingdawg-loop": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "dingdawg-loop"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dingdawg-dingdawg-loop --command npx --arg -y --arg dingdawg-loop
```

### Hermes

```yaml
mcp_servers:
  dingdawg-dingdawg-loop:
    command: "npx"
    args: ["-y", "dingdawg-loop"]
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 69, 0)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-02 (score 69, +48)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security improvement] Install scripts: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 21, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 28, +4)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-29 (score 24, −22)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (6)

### `register_loop` (~245 tokens)

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.

Input parameters:

- `action_type` (string, required): Type of action this loop performs (e.g., 'send_email', 'generate_report', 'sync_data', 'health_check')
- `description` (string, required): Detailed description of what this loop does each cycle. Be specific — governance evaluates this text.
- `metadata` (object): Optional key-value metadata (e.g., owner, team, target_system)
- `name` (string, required): Human-readable name for this loop (e.g., 'daily-report-sender', 'hourly-health-check')
- `risk_tier` (string, required): Risk tier — determines governance gate strictness. 'critical' loops will almost always require human review.
- `schedule` (string, required): Cron expression for the schedule (e.g., '0 9 * * *' for daily at 9am, '@hourly'). Stored but not auto-executed in v1.

### `execute_loop` (~93 tokens)

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.

Input parameters:

- `execution_notes` (string): Optional notes about why this manual execution was triggered
- `loop_id` (string, required): The loop_id returned from register_loop

### `list_loops` (~56 tokens)

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.

Input parameters:

- `status_filter` (string): Filter by loop status (default: all)

### `pause_loop` (~70 tokens)

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.

Input parameters:

- `loop_id` (string, required): The loop_id to pause
- `reason` (string): Why this loop is being paused (recorded in metadata)

### `resume_loop` (~39 tokens)

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

Input parameters:

- `loop_id` (string, required): The loop_id to resume

### `loop_audit` (~73 tokens)

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.

Input parameters:

- `limit` (number): Maximum number of execution records to return (default: 20)
- `loop_id` (string, required): The loop_id to audit

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/dingdawg-dingdawg-loop/dingdawg-loop#diagnostics

## Score history

- 2026-08-04: 69
- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 21
- 2026-07-31: 28
- 2026-07-29: 24
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/dingdawg-loop
- Socket report: https://socket.dev/npm/package/dingdawg-loop
- Repository: https://github.com/dingdawg/loop-protocol
- Changelog RSS feed: https://verifymcp.io/servers/dingdawg-dingdawg-loop/dingdawg-loop/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dingdawg-dingdawg-loop/dingdawg-loop/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dingdawg-dingdawg-loop/dingdawg-loop