Is the Lazymac2x Cron Collision Detector MCP server down?

mcp-registry/io.github.lazymac2x/cron-collision-detector · v1.0.0

As of 2026-10-20 03:05 UTC, the Lazymac2x Cron Collision Detector 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-collision-detector

claude mcp add --transport http lazymac2x-cron-collision-detector-mcp-se https://api.lazy-mac.com/cron-collision-detector/mcp

{
  "mcpServers": {
    "lazymac2x-cron-collision-detector-mcp-se": {
      "type": "http",
      "url": "https://api.lazy-mac.com/cron-collision-detector/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (73/100)

What to fix (4)

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lazymac2x%2Fcron-collision-detector/fixes

{
  "name": "analyze_cron_collisions",
  "description": "Detect collision and spike windows across multiple cron schedules over a time horizon.",
  "inputSchema": {
    "type": "object",
    "required": [
      "jobs"
    ],
    "properties": {
      "jobs": {
        "type": "array",
        "items": {
          "type": "object"
        },
        "description": "Array of { id, expression }"
      },
      "bucket_seconds": {
        "type": "number",
        "description": "Collision bucket size in seconds (default 1)"
      },
      "horizon_minutes": {
        "type": "number",
        "description": "Look-ahead horizon in minutes (default 60)"
      },
      "collision_threshold": {
        "type": "number",
        "description": "Min concurrent jobs to count as collision (default 2)"
      }
    }
  },
  "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-collision-detector"],"email":"[email protected]"}'

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

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~249 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

• analyze_cron_collisions ~167 tokens
• next_firings ~82 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-collision-detector.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fcron-collision-detector?ref=badge)

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

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fcron-collision-detector.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fcron-collision-detector?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:5357256bdb9d7367…, first seen 2026-10-17, included at leaf 2896 of 30,375. Version history · verify what your client received.

Tools (2)

• analyze_cron_collisions
• next_firings

Compare: most reliable devops servers · most reliable other 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 Collision Detector MCP server down right now?

As of 2026-10-20 03:05 UTC, the Lazymac2x Cron Collision Detector 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 Collision Detector MCP server provide?

Lazymac2x Cron Collision Detector MCP server advertises 2 tools, including analyze_cron_collisions, next_firings.

How do I install Lazymac2x Cron Collision Detector MCP server?

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

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

Glimind scanned all 2 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 Collision Detector 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.