Is the Lazymac2x Cron Monitor MCP server down?

mcp-registry/io.github.lazymac2x/cron-monitor · v1.1.0

As of 2026-10-26 22:19 UTC, the Lazymac2x Cron Monitor MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

Cloudflare Workers MCP server: cron-monitor

Point your MCP client at this streamable-http endpoint: https://api.lazy-mac.com/cron-monitor/mcp

Agent-readiness: C (79/100)

What to fix (4)

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lazymac2x%2Fcron-monitor/fixes

{
  "name": "create_monitor",
  "description": "Register a new cron job monitor. Returns the monitor ID to use in ping URLs. Requires API key.",
  "inputSchema": {
    "type": "object",
    "required": [
      "api_key",
      "name",
      "expected_interval_seconds"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Human-readable monitor name"
      },
      "api_key": {
        "type": "string",
        "description": "API key (x-api-key header value)"
      },
      "notify_url": {
        "type": "string",
        "description": "Webhook URL for DOWN alerts (receives POST with JSON)"
      },
      "grace_period_seconds": {
        "type": "integer",
        "default": 0,
        "description": "Extra seconds allowed after interval before going DOWN"
      },
      "schedule_description": {
        "type": "string",
        "description": "Human-readable schedule (e.g. 'Every night at 3am UTC')"
      },
      "expected_interval_seconds": {
        "type": "integer",
        "description": "How often the job should run (seconds)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

{
  "name": "get_dashboard",
  "description": "Get an overview of all cron monitors — total count, counts per status (up/down/grace/new), and a summary list. Requires API key.",
  "inputSchema": {
    "type": "object",
    "required": [
      "api_key"
    ],
    "properties": {
      "api_key": {
        "type": "string",
        "description": "API key (x-api-key header value)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_monitor_status",
  "description": "Get the current status (up/down/grace/new) of a specific cron monitor along with last ping time and total ping count.",
  "inputSchema": {
    "type": "object",
    "required": [
      "monitor_id"
    ],
    "properties": {
      "monitor_id": {
        "type": "string",
        "description": "Monitor ID to check"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.lazymac2x/cron-monitor"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/cron-monitor"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~720 tokens).
• Tool names are unique and portable across clients.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• create_monitor ~230 tokens
• ping_monitor ~140 tokens
• get_ping_history ~106 tokens
• get_dashboard ~88 tokens
• get_monitor_status ~85 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fcron-monitor.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fcron-monitor?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fcron-monitor?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fcron-monitor.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fcron-monitor.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fcron-monitor?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:460a15425181ac2c…, first seen 2026-10-17, included at leaf 11858 of 75,794. Version history · verify what your client received.

Tools (6)

• create_monitor
• get_dashboard
• get_monitor_status
• get_ping_history
• list_monitors
• ping_monitor

Compare: most reliable devops servers · most reliable data servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Lazymac2x Cron Monitor MCP server down right now?

As of 2026-10-26 22:19 UTC, the Lazymac2x Cron Monitor MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Lazymac2x Cron Monitor MCP server provide?

Lazymac2x Cron Monitor MCP server advertises 6 tools, including create_monitor, get_dashboard, get_monitor_status, get_ping_history, list_monitors.

How do I install Lazymac2x Cron Monitor MCP server?

Point your MCP client at this streamable-http endpoint: https://api.lazy-mac.com/cron-monitor/mcp

Is the Lazymac2x Cron Monitor MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Lazymac2x Cron Monitor MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.