cron-monitor MCP server
io.github.lazymac2x/cron-monitorlazymac2xstreamable-httpv1.0.0Scanned
Cloudflare Workers MCP server: cron-monitor
6 tools: 1 do something that can't be undone, 1 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the cron-monitor MCP server can do
The cron-monitor MCP server is published by the GitHub account lazymac2x. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (ping_monitor) and create or change data (1 tool: create_monitor), but cannot delete data. 4 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Can't be undone 1Claude Code: ask
ping_monitorSend a heartbeat ping to a cron monitor to confirm the job ran successfully.No findings
Why it is in this group
- The name "ping_monitor" says "ping": a word for reading.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it Send a heartbeat ping to a cron monitor to confirm the job ran successfully. Use ping_type='ping' for simple heartbeats, 'start'+'complete' for duration tracking, or 'fail' to immediately mark it down.
Changes things 1Claude Code: ask
create_monitorRegister a new cron job monitor.No findings
Why it is in this group
- The name "create_monitor" says "create": a word for a change.
Description, as the server wrote it Register a new cron job monitor. Returns the monitor ID to use in ping URLs. Requires API key.
Only reads 4Show 4 read-only tools
get_dashboardGet an overview of all cron monitors — total count, counts per status (up/down/grace/new), and a summary list.No findings
Why it is in this group
- The name "get_dashboard" says "get": a word for reading.
Description, as the server wrote it Get an overview of all cron monitors — total count, counts per status (up/down/grace/new), and a summary list. Requires API key.
get_monitor_statusGet the current status (up/down/grace/new) of a specific cron monitor along with last ping time and total ping count.No findings
Why it is in this group
- The name "get_monitor_status" says "get": a word for reading.
Description, as the server wrote it Get the current status (up/down/grace/new) of a specific cron monitor along with last ping time and total ping count.
get_ping_historyRetrieve the last 100 ping events for a monitor (type, timestamp, IP, duration for complete events).No findings
Why it is in this group
- The name "get_ping_history" says "get": a word for reading.
Description, as the server wrote it Retrieve the last 100 ping events for a monitor (type, timestamp, IP, duration for complete events). Requires API key.
list_monitorsList all monitors with real-time computed status.No findings
Why it is in this group
- The name "list_monitors" says "list": a word for reading.
Description, as the server wrote it List all monitors with real-time computed status. Requires API key.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.lazy-mac.com/.well-known/oauth-protected-resource/cron-monitor/mcp
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.lazy-mac.com/cron-monitor/mcp: tools/list returned 6 tools to an anonymous client, including ping_monitor (irreversible), create_monitor (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http cron-monitor https://api.lazy-mac.com/cron-monitor/mcpclaude mcp add --transport http cron-monitor https://api.lazy-mac.com/cron-monitor/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__cron-monitor__get_monitor_status",
"mcp__cron-monitor__get_dashboard",
"mcp__cron-monitor__list_monitors",
"mcp__cron-monitor__get_ping_history"
],
"ask": [
"mcp__cron-monitor__ping_monitor",
"mcp__cron-monitor__create_monitor"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cron-monitor. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.lazymac2x/cron-monitor/verify?hash=770cf9c286d0607b935203bc7fa0c664e672cfc19dad4a947d67e8e06fd26a91" | jq -e '.changed == false'Pinned hash 770cf9c286d0, from Nov 21, 2026, 16:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.lazymac2x/cron-monitor/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.lazymac2x/cron-monitor)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:38 UTC.
cron-monitor MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the cron-monitor MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the cron-monitor MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the cron-monitor MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: ping_monitor.
What tools does the cron-monitor MCP server have?
- 6 tools: 1 irreversible, 1 write, 4 read. ping_monitor, create_monitor, get_monitor_status, get_dashboard, list_monitors and get_ping_history.
Does the cron-monitor MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the cron-monitor MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the cron-monitor MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.