Is the 402cron MCP server down?

mcp-registry/com.402cron/402cron

healthy
Last checked 2026-10-25 10:32 UTC · handshake 217ms

As of 2026-10-25 10:32 UTC, the 402cron MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,758
outages (90d)
0
tools
16

Paid cron for AI agents: we call your https URL on schedule, signed. No account, paid with x402.

Install 402cron MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http 402cron-mcp-server https://402cron.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "402cron-mcp-server": {
      "type": "http",
      "url": "https://402cron.com/mcp"
    }
  }
}

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

Agent-readiness: A (93/100)

A (93/100): 0 error(s), 1 warning(s) across 16 tool(s); ~2,734 tokens of tool definitions.
Scores higher than 76% of 15,683 MCP servers Glimind has audited.
Its tool list costs an agent ~2,734 tokens per session — more than 50% of servers.
77 → 92 since 2026-10-17
no tool-poisoning patterns
Schemas84
Descriptions100
Safety hints100
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: create_task, update_task

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: 2 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%2Fcom.402cron%2F402cron/fixes

create_task 1 change
{
  "name": "create_task",
  "description": "Register a schedule against a destination you have already verified. Idempotent on \"name\": the same name updates the existing task instead of creating a second one. Creating costs nothing; each delivery ATTEMPT costs one credit.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name",
      "cron",
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "The https:// destination. It must already be registered and verified — see register_destination."
      },
      "body": {
        "description": "The body we send. Stored in the clear, so it must not carry credentials. A non-string is serialized as JSON.",
        "type": "string"
      },
      "cron": {
        "type": "string",
        "description": "5 fields, UTC only, one minute at the finest. Operators: * a-b a,b */n a-b/n. Names: SUN-SAT (day), JAN-DEC (month). Macros: @yearly @annually @monthly @weekly @daily @midnight @hourly. Day-of-week is 0-6 with 0 = Sunday; 7 also means Sunday. Write days as names (MON-FRI). Numbers differ between schedulers: Quartz, AWS EventBridge and Cloudflare number Sunday as 1, we and croniter as 0. Translated for you: \"?\". \"?\" as a whole day-of-month or day-of-week field becomes \"*\". A NUMERIC day-of-week next to \"?\" is refused, because \"?\" means the expression was written where Sunday is 1. Refused: Quartz L, Quartz W, Quartz #, six fields (seconds), seven fields (year), @reboot, @every, CRON_TZ= prefixes, time zones of any kind — each with a code saying what to send instead."
      },
      "name": {
        "type": "string",
        "description": "Your name for the task. Unique among your live tasks; creating with an existing name updates it."
      },
      "method": {
        "type": "string",
        "description": "HTTP method of the delivery. Default POST. GET and HEAD carry no body."
      },
      "headers": {
        "type": "object",
        "description": "Headers we send with the delivery. Stored ENCRYPTED at rest — put credentials here, never in the body."
      },
      "timeoutMs": {
        "type": "integer",
        "description": "How long we wait for your server, 250-2000 ms. Answer 202 and do the work behind it."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Create or update a scheduled task",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": true
  },
  "title": "Create or update a scheduled task"
}
update_task 1 change
{
  "name": "update_task",
  "description": "Change the schedule, destination, method, timeout, headers or body of an existing task. Omit a field to leave it unchanged — sending null is refused, because \"unchanged\" and \"cleared\" must not look the same. State is NOT editable here: use pause_task and resume_task.",
  "inputSchema": {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "Task id (UUID), as returned by create_task or list_tasks."
      },
      "url": {
        "type": "string",
        "description": "The https:// destination. It must already be registered and verified — see register_destination."
      },
      "body": {
        "description": "The body we send. Stored in the clear, so it must not carry credentials. A non-string is serialized as JSON.",
        "type": "string"
      },
      "cron": {
        "type": "string",
        "description": "5 fields, UTC only, one minute at the finest. Operators: * a-b a,b */n a-b/n. Names: SUN-SAT (day), JAN-DEC (month). Macros: @yearly @annually @monthly @weekly @daily @midnight @hourly. Day-of-week is 0-6 with 0 = Sunday; 7 also means Sunday. Write days as names (MON-FRI). Numbers differ between schedulers: Quartz, AWS EventBridge and Cloudflare number Sunday as 1, we and croniter as 0. Translated for you: \"?\". \"?\" as a whole day-of-month or day-of-week field becomes \"*\". A NUMERIC day-of-week next to \"?\" is refused, because \"?\" means the expression was written where Sunday is 1. Refused: Quartz L, Quartz W, Quartz #, six fields (seconds), seven fields (year), @reboot, @every, CRON_TZ= prefixes, time zones of any kind — each with a code saying what to send instead."
      },
      "name": {
        "type": "string",
        "description": "Your name for the task. Unique among your live tasks; creating with an existing name updates it."
      },
      "method": {
        "type": "string",
        "description": "HTTP method of the delivery. Default POST. GET and HEAD carry no body."
      },
      "headers": {
        "type": "object",
        "description": "Headers we send with the delivery. Stored ENCRYPTED at rest — put credentials here, never in the body."
      },
      "timeoutMs": {
        "type": "integer",
        "description": "How long we wait for your server, 250-2000 ms. Answer 202 and do the work behind it."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Edit a task",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": true
  },
  "title": "Edit a task"
}

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/com.402cron/402cron"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.402cron/402cron"}) 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%2Fcom.402cron%2F402cron.svg)](https://glimind.com/server/mcp-registry%2Fcom.402cron%2F402cron?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.402cron%2F402cron?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.402cron%2F402cron.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.402cron%2F402cron.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.402cron%2F402cron?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:9529dd0eb53d1d29…, first seen 2026-10-23, included at leaf 49906 of 65,487. Version history · verify what your client received.

Tools (16)

Compare: most reliable productivity servers · most reliable web servers · most reliable data servers · most reliable knowledge servers · most reliable finance 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 402cron MCP server down right now?

As of 2026-10-25 10:32 UTC, the 402cron MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does 402cron MCP server provide?

402cron MCP server advertises 16 tools, including create_task, delete_destination, delete_task, get_docs, get_pricing.

How do I install 402cron MCP server?

Point your MCP client at this streamable-http endpoint: https://402cron.com/mcp

Is the 402cron MCP server safe to connect to an AI agent?

Glimind scanned all 16 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 402cron 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