Monthly Update Detector runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 12 May 2026.
"Nightly 03:00 CT scan: identifies skills whose newest file mtime crossed 25 days
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
root.innerHTML = html.join('');
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Monthly Update Detector
same job, measured the same wayScan AI agent skills for 25 attack classes + runtime monitoring. 1,316+ findings.
Date/time math for agents: business days, holidays, time zones, cron, RRULE. 25 free calls/day.
Local-first MCP server for agent skills. Validate, lint, diff, and convert across IDEs.
Share agent skills across your team, scan them for risk, and track what's actually used.
Daily 09:00 CDT. Picks a skill from the catalog (weighted random; prefers skills not spotlit in l...
Compare STEP CAD files locally: identical, moved, or different, and what changed.
The fix desk for AI agents: human fixes become skills the whole fleet reuses.
Builds optimal 24/7 staff rosters with a real MILP solver: rest rules, skills, nights, fairness.
Monthly Update Detector — questions
Answers built from our own checks of this server.