PluginBench
MCP Server
Maintained
MIT

io.github.dailyaiagents-cpu/monthly-update-detector MCP Server

io.github.dailyaiagents-cpu/monthly-update-detector

RepositoryRegistry
How to choose

What this kind of tool is for

  • Chain multi-step workflows across the other tools in this directory.
  • Run a scheduled or triggered job instead of retyping the same request.
  • Have your agent watch a feed, queue, or repo and act on new items.

How to compare servers like this

Trigger model:
Understand what starts the automation — a command, a schedule, or an event — before relying on it.
Blast radius:
Prefer tools that hand you a review point before an irreversible action runs.
Chaining cost:
Each chained step adds a failure point; keep critical paths on the fewest tools.
Maintenance signal:
Automations break quietly; a maintained tool is the difference between repair and rediscovery.

What is the io.github.dailyaiagents-cpu/monthly-update-detector MCP server?

"Nightly 03:00 CT scan: identifies skills whose newest file mtime crossed 25 days

How to install io.github.dailyaiagents-cpu/monthly-update-detector

Copy-paste configuration for popular MCP clients.

No machine-readable install method is published for this server in the registry. Check the repository or website for setup instructions.

Related MCP servers

Daily Stripe MRR query against a configured floor

0
Shell
MIT
View repository →

Every 6h, compare loaded launchd labels (launchctl list) against source-of-truth plists in config...

0
Shell
MIT
View repository →

Hourly publish of an operational ticker — last 24h commits, voice-gate pass/fail counts, P-gate c...

0
Shell
MIT
View repository →

Walks every skill directory in skills/ and ~/.openclaw/skills/, validates each has SOUL.md (voice...

0
Shell
MIT
View repository →

Append-only telemetry helpers — track_start and track_end

0
Shell
MIT
View repository →

Auto-wire newly-shipped skills into owner-agent SOUL.md by reading `owner_agent:` frontmatter and...

0
Shell
MIT
View repository →