Is the Idoazacalls Cron Explainer MCP server down?

mcp-registry/io.github.idoazacalls/cron-explainer · v0.1.2

Also listed as glama/idoazacalls/cron-explainer

healthy
Last checked 2026-10-24 01:01 UTC · handshake 78ms

As of 2026-10-24 01:01 UTC, the Idoazacalls Cron Explainer MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,478
outages (90d)
0
tools
1

Cron expression parser: explains any cron + returns next N fire times. Timezone-aware.

Install Idoazacalls Cron Explainer MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http idoazacalls-cron-explainer-mcp-server https://cron-explainer.cron-explainer-prod.workers.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "idoazacalls-cron-explainer-mcp-server": {
      "type": "http",
      "url": "https://cron-explainer.cron-explainer-prod.workers.dev/mcp"
    }
  }
}

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

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 1 tool(s); ~189 tokens of tool definitions.
Scores higher than 47% of 15,609 MCP servers Glimind has audited.
Its tool list costs an agent ~189 tokens per session — lighter than 99% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: explain_cron

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 1 corrected tool definition

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.idoazacalls%2Fcron-explainer/fixes

explain_cron 1 change
{
  "name": "explain_cron",
  "description": "Parse a POSIX/Vixie cron expression and return the next N fire times plus an English description. Timezone-aware (IANA). Best-effort accuracy. Billed at 1 EUR cent per successful call; non-2xx responses are refunded.",
  "inputSchema": {
    "type": "object",
    "required": [
      "cron"
    ],
    "properties": {
      "n": {
        "type": "integer",
        "default": 5,
        "maximum": 100,
        "minimum": 1,
        "description": "Number of upcoming fire times to return."
      },
      "tz": {
        "type": "string",
        "description": "IANA timezone (e.g. 'Europe/Lisbon'). Defaults to UTC."
      },
      "cron": {
        "type": "string",
        "minLength": 1,
        "description": "POSIX/Vixie cron expression (5 fields, e.g. '*/15 * * * *')."
      }
    },
    "additionalProperties": false
  },
  "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.idoazacalls/cron-explainer"],"email":"[email protected]"}'

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

Passed

Largest tool definitions

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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.idoazacalls%2Fcron-explainer.svg)](https://glimind.com/server/mcp-registry%2Fio.github.idoazacalls%2Fcron-explainer?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.idoazacalls%2Fcron-explainer?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.idoazacalls%2Fcron-explainer.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.idoazacalls%2Fcron-explainer.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.idoazacalls%2Fcron-explainer?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:39585f12796ca1e3…, first seen 2026-10-17, included at leaf 6260 of 55,650. Version history · verify what your client received.

Tools (1)

Compare: most reliable productivity servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Idoazacalls Cron Explainer MCP server down right now?

As of 2026-10-24 01:01 UTC, the Idoazacalls Cron Explainer MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Idoazacalls Cron Explainer MCP server provide?

Idoazacalls Cron Explainer MCP server advertises 1 tool, including explain_cron.

How do I install Idoazacalls Cron Explainer MCP server?

Point your MCP client at this streamable-http endpoint: https://cron-explainer.cron-explainer-prod.workers.dev/mcp

Is the Idoazacalls Cron Explainer MCP server safe to connect to an AI agent?

Glimind scanned all 1 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 Idoazacalls Cron Explainer 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.

Feedback
Help us improve