# cron402 (npm · cron402-mcp)

Schedule webhook calls, pay per run in USDC on Base via x402. Ten tools, built for small models.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- npm · `cron402-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/userdefault13-cron402-mcp/cron402-mcp.md), [page](https://verifymcp.io/servers/userdefault13-cron402-mcp/cron402-mcp)

## Channel facts

- Registry: `npm`
- Package: `cron402-mcp`
- Version: `1.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 32 of 116 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 933 tokens (~93/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_cron" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the cron402 MCP server?

cron402 runs locally as an npm package, launched with npx -y cron402-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add userdefault13-cron402-mcp -- npx -y cron402-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "userdefault13-cron402-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cron402-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "userdefault13-cron402-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cron402-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add userdefault13-cron402-mcp -- npx -y cron402-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "userdefault13-cron402-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "cron402-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add userdefault13-cron402-mcp --command npx --arg -y --arg cron402-mcp
```

### Hermes

```yaml
mcp_servers:
  userdefault13-cron402-mcp:
    command: "npx"
    args: ["-y", "cron402-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "userdefault13-cron402-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "cron402-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add userdefault13-cron402-mcp -t stdio -c npx -a -y cron402-mcp
```

### Other

```json
{
  "mcpServers": {
    "userdefault13-cron402-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cron402-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-23 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 73, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-08 (score 69, +41)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Dependency health: unverified → 0.86
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Tool coverage: 93
- [functional] First check of Destructive annotations: 0
- [functional] First check of Schema quality: pass

### 2026-09-07 (score 28)

First indexed and scored.

## MCP tools (10)

### `cron402_guide` (~51 tokens)

READ THIS FIRST before using any other cron402 tool. Free, no payment. Returns the exact step-by-step procedure for scheduling a recurring webhook, what each tool costs, and the rules you must follow.

### `check_wallet` (~54 tokens)

Free. Check the cron402 payment wallet before spending: returns the address, network, USDC balance, ETH balance for gas, and how many runs it can afford. Call this before create_cron or topup_cron.

### `preview_schedule` (~161 tokens)

Free, no payment. Turn a schedule into a validated cron expression and show the next 5 run times in UTC. Accepts plain English like 'every 15 minutes' or 'every weekday at 9am', or a 5-field cron expression. ALWAYS call this before create_cron and show the user the result.

Input parameters:

- `schedule` (string, required): Plain English ('every 15 minutes', 'every day at 09:00', 'every monday at 5pm', 'weekly') or a 5-field cron expression ('*/15 * * * *').
- `timezone` (string): IANA timezone of any time-of-day in the schedule, e.g. 'America/New_York'. Omit if the user gave the time in UTC.

### `create_cron` (~241 tokens)

PAID: spends $0.008 USDC. Create a scheduled job that calls a webhook URL on a repeating schedule. Call this ONCE per request — calling it twice creates two jobs and charges twice. Run preview_schedule first. Returns a jobId you must report to the user. The job is created with 1 run credit, so it fires once and then stops unless you call topup_cron.

Input parameters:

- `body` (string): Request body sent on every fire (POST only).
- `headers` (object): Extra request headers, e.g. an authorization token for the target.
- `method` (string)
- `notifyUrl` (string): Optional. Receives a POST with the result after every fire.
- `schedule` (string, required): Plain English ('every 15 minutes', 'every weekday at 9am') or a 5-field cron expression. Validated locally before any payment is made.
- `timezone` (string): IANA timezone for a time-of-day in the schedule, e.g. 'Europe/Berlin'.
- `url` (string, required): Public HTTPS URL to call on every fire. localhost will never work.

### `topup_cron` (~111 tokens)

PAID: spends $0.008 per credit ($0.008 / $0.08 / $0.80). Add prepaid run credits to an existing job. Each credit pays for one fire. Also reactivates a job that ran out of credits. Call ONCE — repeating it charges again.

Input parameters:

- `jobId` (string, required): The job id returned by create_cron.
- `pack` (number, required): How many run credits to buy: 1, 10, or 100.

### `get_cron` (~65 tokens)

Free. Get one job's current status, remaining credits, next run time, and its last 20 executions with HTTP status codes and errors. Use this to answer 'is my cron working?'.

Input parameters:

- `jobId` (string, required): The job id returned by create_cron.

### `list_crons` (~49 tokens)

Free. List the cron jobs created from this machine with this wallet, with each one's live status and remaining credits. Use this when the user asks what is scheduled or you have lost a job id.

### `pause_cron` (~64 tokens)

Free. Stop a job from firing without deleting it. Credits are kept. Signs an EIP-712 authorization with the configured wallet — only the wallet that paid for the job can do this.

Input parameters:

- `jobId` (string, required): The job id returned by create_cron.

### `resume_cron` (~70 tokens)

Free. Start a paused job firing again. The job needs at least 1 credit — if it is 'exhausted', call topup_cron instead. Signs an EIP-712 authorization with the configured wallet.

Input parameters:

- `jobId` (string, required): The job id returned by create_cron.

### `delete_cron` (~67 tokens)

Free but PERMANENT and irreversible: deletes a job forever and does not refund unused credits. Confirm with the user before calling. If they only want it to stop for now, use pause_cron instead.

Input parameters:

- `jobId` (string, required): The job id returned by create_cron.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/userdefault13-cron402-mcp/cron402-mcp#diagnostics

## Score history

- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 75
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 73
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 69
- 2026-09-07: 28

## Common questions

### What is the cron402 MCP server?

cron402 is an MCP server listed in the public MCP registry as io.github.userdefault13/cron402-mcp. Schedule webhook calls, pay per run in USDC on Base via x402. Ten tools, built for small models. This page covers its npm package (cron402-mcp).

### Is the cron402 MCP server safe to use?

cron402 scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the cron402 MCP server expose?

cron402 exposes 10 tools: cron402_guide, check_wallet, preview_schedule, create_cron, topup_cron, and 5 more. Their descriptions and schemas cost roughly 933 tokens of context every time the server is loaded.

### Is the cron402 MCP server still maintained?

cron402 is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the cron402 MCP server under?

cron402 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/cron402-mcp
- Socket report: https://socket.dev/npm/package/cron402-mcp
- Repository: https://github.com/userdefault13/ai-cron-site
- Website: https://agentcron.site/
- Changelog RSS feed: https://verifymcp.io/servers/userdefault13-cron402-mcp/cron402-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/userdefault13-cron402-mcp/cron402-mcp.json
- HTML version of this page: https://verifymcp.io/servers/userdefault13-cron402-mcp/cron402-mcp