cron402
NPM · CRON402-MCP · SCANNED SEP 24
Schedule webhook calls, pay per run in USDC on Base via x402. Ten tools, built for small models.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 116 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 933 tokens (~93/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
npm · cron402-mcp
claude mcp add userdefault13-cron402-mcp -- npx -y cron402-mcp
{
"mcpServers": {
"userdefault13-cron402-mcp": {
"command": "npx",
"args": [
"-y",
"cron402-mcp"
]
}
}
} {
"servers": {
"userdefault13-cron402-mcp": {
"command": "npx",
"args": [
"-y",
"cron402-mcp"
]
}
}
} codex mcp add userdefault13-cron402-mcp -- npx -y cron402-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"userdefault13-cron402-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"cron402-mcp"
],
"enabled": true
}
}
} openclaw mcp add userdefault13-cron402-mcp --command npx --arg -y --arg cron402-mcp
mcp_servers:
userdefault13-cron402-mcp:
command: "npx"
args: ["-y", "cron402-mcp"] {
"McpServers": {
"userdefault13-cron402-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"cron402-mcp"
]
}
}
} assistant mcp add userdefault13-cron402-mcp -t stdio -c npx -a -y cron402-mcp
{
"mcpServers": {
"userdefault13-cron402-mcp": {
"command": "npx",
"args": [
"-y",
"cron402-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +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.
- 21 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 15 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 8 Sept 26 +41
- Injection markers: unverified → pass ▲ security
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- Dependency health: unverified → 0.86 ▲ functional
- 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 functional
- 7 Sept 26 28
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/cron402-mcp@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 116 packages
| Packages resolved | 116 |
|---|---|
| Deprecated | 1 |
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_wallet ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_cron ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Public HTTPS URL to call on every fire. localhost will never work. |
No output schema declared.
No examples provided.
cron402_guide ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_cron ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The job id returned by create_cron. |
No output schema declared.
No examples provided.
get_cron ~65
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?'.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The job id returned by create_cron. |
No output schema declared.
No examples provided.
list_crons ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pause_cron ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The job id returned by create_cron. |
No output schema declared.
No examples provided.
preview_schedule ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| schedule | string | yes | 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. |
No output schema declared.
No examples provided.
resume_cron ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The job id returned by create_cron. |
No output schema declared.
No examples provided.
topup_cron ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The job id returned by create_cron. |
| pack | number | yes | How many run credits to buy: 1, 10, or 100. |
No output schema declared.
No examples provided.
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.