DingDawg Loop · MCP package

Know what the loop actually does.

Loop records recurring intentions and lets you request governance evaluations manually. Its stored cron schedule is metadata, not a running scheduler.

Install in an MCP client

Configure your MCP client with command npx and arguments ["-y", "dingdawg-loop"]. This starts a stdio MCP server; it is not an interactive terminal app.

npx -y dingdawg-loop

Read the installed version’s README for environment settings and limits before connecting sensitive workflows.

Six tools, a bounded contract

  • register_loop

    Store the name, intent, risk tier and schedule.

  • execute_loop

    Request a manual governance evaluation; no underlying action is dispatched.

  • list_loops

    Inspect stored loops.

  • pause_loop

    Prevent further evaluations of a loop.

  • resume_loop

    Allow manual evaluations again.

  • loop_audit

    Inspect locally stored evaluation history.

Read outcomes carefully

Published 2.x versions can label an allowed evaluation “executed” despite not dispatching a business action. Treat that field as an evaluation outcome, never as proof that a payment, email or job ran.

Local JSON history is not a signed payment receipt. No-key keyword checks are not sufficient financial authorization. A cloud policy response does not remove the need for an enforced execution boundary.