Is the Lazymac2x Cron Parser MCP server down?

mcp-registry/io.github.lazymac2x/cron-parser · v2.0.0

As of 2026-10-20 17:12 UTC, the Lazymac2x Cron Parser 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-parser

claude mcp add --transport http lazymac2x-cron-parser-mcp-server https://api.lazy-mac.com/cron-parser/mcp

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

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

Agent-readiness: C (74/100)

What to fix (5)

Auto-fix: 3 corrected tool definitions

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-parser/fixes

{
  "name": "explain_cron",
  "description": "Explain a cron expression in human-readable form and show parsed fields. Supports @presets like @daily, @weekly.",
  "inputSchema": {
    "type": "object",
    "required": [
      "expression"
    ],
    "properties": {
      "expression": {
        "type": "string",
        "description": "Cron expression (e.g. \"*/5 * * * *\" or \"@daily\")"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "next_runs",
  "description": "Get the next N scheduled run times for a cron expression. Uses standard Unix OR semantics for day fields.",
  "inputSchema": {
    "type": "object",
    "required": [
      "expression"
    ],
    "properties": {
      "from": {
        "type": "string",
        "description": "ISO 8601 start date (default: now)"
      },
      "count": {
        "type": "number",
        "description": "Number of next runs to return (1-20, default 5)"
      },
      "expression": {
        "type": "string",
        "description": "Cron expression"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

{
  "name": "validate_cron",
  "description": "Check if a cron expression is valid. Returns {valid: bool, error?: string}.",
  "inputSchema": {
    "type": "object",
    "required": [
      "expression"
    ],
    "properties": {
      "expression": {
        "type": "string",
        "description": "Cron expression to validate"
      }
    }
  },
  "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-parser"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/cron-parser"}) 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 (~564 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

• generate_cron ~150 tokens
• next_runs ~124 tokens
• explain_cron ~91 tokens
• diff_cron ~85 tokens
• validate_cron ~74 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-parser.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fcron-parser?ref=badge)

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

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

Tools (6)

• common_crons
• diff_cron
• explain_cron
• generate_cron
• next_runs
• validate_cron

Compare: most reliable productivity servers · most reliable devops servers · most reliable knowledge servers · most reliable other servers · most reliable code 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 Parser MCP server down right now?

As of 2026-10-20 17:12 UTC, the Lazymac2x Cron Parser 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 Parser MCP server provide?

Lazymac2x Cron Parser MCP server advertises 6 tools, including common_crons, diff_cron, explain_cron, generate_cron, next_runs.

How do I install Lazymac2x Cron Parser MCP server?

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

Is the Lazymac2x Cron Parser 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 Parser 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.