io.github.dingdawg/dingdawg-loop
NPM · DINGDAWG-LOOP · SCANNED SEP 22
Safe scheduled AI agents with governance gates. Verified, receipted, fail-closed.
Available components
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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 68 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 576 tokens (~96/item across 6 items; 6 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_loop" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 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
How do I install the io.github.dingdawg/dingdawg-loop MCP server?
io.github.dingdawg/dingdawg-loop runs locally as an npm package, launched with npx -y dingdawg-loop. 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-loop
claude mcp add dingdawg-dingdawg-loop -- npx -y dingdawg-loop
{
"mcpServers": {
"dingdawg-dingdawg-loop": {
"command": "npx",
"args": [
"-y",
"dingdawg-loop"
]
}
}
} {
"servers": {
"dingdawg-dingdawg-loop": {
"command": "npx",
"args": [
"-y",
"dingdawg-loop"
]
}
}
} codex mcp add dingdawg-dingdawg-loop -- npx -y dingdawg-loop
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dingdawg-dingdawg-loop": {
"type": "local",
"command": [
"npx",
"-y",
"dingdawg-loop"
],
"enabled": true
}
}
} openclaw mcp add dingdawg-dingdawg-loop --command npx --arg -y --arg dingdawg-loop
mcp_servers:
dingdawg-dingdawg-loop:
command: "npx"
args: ["-y", "dingdawg-loop"] {
"McpServers": {
"dingdawg-dingdawg-loop": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"dingdawg-loop"
]
}
}
} assistant mcp add dingdawg-dingdawg-loop -t stdio -c npx -a -y dingdawg-loop
{
"mcpServers": {
"dingdawg-dingdawg-loop": {
"command": "npx",
"args": [
"-y",
"dingdawg-loop"
]
}
}
} 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.
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.83 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 12 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
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 22 Sept 2026 · Analysed npm/dingdawg-loop@2.0.8
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
execute_loop ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_notes | string | – | Optional notes about why this manual execution was triggered |
| loop_id | string | yes | The loop_id returned from register_loop |
No output schema declared.
No examples provided.
list_loops ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| status_filter | string | – | Filter by loop status (default: all) |
No output schema declared.
No examples provided.
loop_audit ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of execution records to return (default: 20) |
| loop_id | string | yes | The loop_id to audit |
No output schema declared.
No examples provided.
pause_loop ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| loop_id | string | yes | The loop_id to pause |
| reason | string | – | Why this loop is being paused (recorded in metadata) |
No output schema declared.
No examples provided.
register_loop ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | Type of action this loop performs (e.g., 'send_email', 'generate_report', 'sync_data', 'health_check') |
| description | string | yes | 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 | yes | Human-readable name for this loop (e.g., 'daily-report-sender', 'hourly-health-check') |
| risk_tier | string | yes | Risk tier — determines governance gate strictness. 'critical' loops will almost always require human review. |
| schedule | string | yes | Cron expression for the schedule (e.g., '0 9 * * *' for daily at 9am, '@hourly'). Stored but not auto-executed in v1. |
No output schema declared.
No examples provided.
resume_loop ~39
Resume a paused loop so it can be executed again. Clears the pause reason from metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| loop_id | string | yes | The loop_id to resume |
No output schema declared.
No examples provided.
What is the io.github.dingdawg/dingdawg-loop MCP server?
io.github.dingdawg/dingdawg-loop is an MCP server listed in the public MCP registry as io.github.dingdawg/dingdawg-loop. Safe scheduled AI agents with governance gates. Verified, receipted, fail-closed. This page covers its npm package (dingdawg-loop).
Is the io.github.dingdawg/dingdawg-loop MCP server safe to use?
io.github.dingdawg/dingdawg-loop scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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-loop MCP server expose?
io.github.dingdawg/dingdawg-loop exposes 6 tools: register_loop, execute_loop, list_loops, pause_loop, resume_loop, loop_audit. Their descriptions and schemas cost roughly 576 tokens of context every time the server is loaded.
Is the io.github.dingdawg/dingdawg-loop MCP server still maintained?
io.github.dingdawg/dingdawg-loop is still listed as active in the MCP registry. We last reached this channel on 22 September 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-loop MCP server under?
io.github.dingdawg/dingdawg-loop declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.