MCP.Market

cron402 MCP server

by userdefault13·io.github.userdefault13/cron402-mcp·v1.1.1
No reviews yet

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

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars45 downloads/wk

Reviews

Write one

Nobody has reviewed cron402 yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

cron402 tools (10, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_wallet

    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.

  • create_cronwrite action

    PAID: spends $… 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.

  • cron402_guide

    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.

  • delete_cronwrite action

    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.

  • get_cron

    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?'.

  • list_crons

    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

    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.

  • preview_schedule

    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.

  • resume_cron

    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.

  • topup_cron

    PAID: spends $… per credit ($… / $… / $…). 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.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 38 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How cron402 compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,243 servers
Tools
10
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
45
more than 35% of 12,306 servers with a package

What its tools let an agent do: 8 read · 1 create · 1 delete

Install cron402 in Claude Code, Cursor or VS Code

Runs npx -y cron402-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add cron402-mcp -- npx -y cron402-mcp
Add to Cursor

What the publisher says

From the cron402 repository's README, as published. We do not edit it. Read it on GitHub

cron402

x402-native cron-as-a-service for AI agents. Agents schedule webhook calls and pay per run in USDC on Base via the x402 protocol — no accounts, no API keys. The wallet is the credential.

  • Price: $0.008 flat per run
  • Network: Base mainnet (eip155:8453) — validated end-to-end on Sepolia first (settlement tx 0x01f7bed4…)
  • Wallets: built for Coinbase Agentic Wallets / any x402 client

Architecture

┌────────────────────────────┐        ┌─────────────────────────────────────────┐
│  apps/web — SvelteKit      │        │  apps/api — Cloudflare Worker (Hono)    │
│  deployed to Vercel        │──────▶ │                                         │
│  - landing page            │        │  x402 paywall (@x402/hono v2)           │
│  - agent integration docs  │        │  ├─ POST /v1/crons            $0.008    │
│                            │        │  ├─ POST /v1/crons/topup/1|10|100       │
│                            │        │  ├─ GET  /v1/crons/:id        (free)    │
│                            │        │  ├─ POST /v1/crons/:id/pause|resume     │
│                            │        │  └─ DELETE /v1/crons/:id   (EIP-712)    │
└────────────────────────────┘        │                                         │
                                      │  CronJobDO (Durable Object per job)     │
                                      │  alarm() → dispatch webhook             │
                                      │  D1: jobs, executions, payments         │
                                      └─────────────────────────────────────────┘
                                                │ se

How scheduling works

  • Every job gets its own Durable Object (CronJobDO). A cron-parser-computed next-run time is set as the DO's alarm() — exact to the minute for arbitrary cron expressions.
  • Each fire: dispatch the target webhook (10s timeout) → up to 3 attempts with backoff → log the execution to D1 (kept: last 100 runs / 30 days per job) → consume 1 credit.
  • Auto-pause rules: 3 consecutive failures → paused; zero credits → exhausted.
  • A global Worker Cron Trigger ( *) sweeps for missed alarms as a safety net.
  • Top-ups reactivate paused/exhausted jobs automatically.

How payments work

Paid endpoints are gated by @x402/hono v2 middleware:

  1. Agent calls the endpoint with no auth.
  2. Server responds 402 Payment Required with instructions (price, network, payTo).
  3. Agent signs an EIP-3009 USDC transfer from its wallet and retries.
  4. The facilitator verifies + settles; settlement receipts land in D1.

Because the payer isn't online when an alarm fires, billing is prepaid run credits: creation includes 1 credit; packs of 1 / 10 / 100 cost $0.008 / $0.08 / $0.80. Credits never expire and top-ups are permissionless (anyone can fund any job).

Management actions (pause/resume/delete) require an EIP-712 signature over ManageJob { action, jobId, timestamp } from the payer key (±5 min validity).

Repository layout

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

cron402: common questions

Is cron402 MCP server safe?
Mostly: it is graded B (78/100). Read the cron402 safety report
How do I install cron402?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does cron402 need an API key?
Yes. The registry entry asks for CRON402_PRIVATE_KEY.
Is cron402 maintained?
The last commit was 58 days ago (2026-09-08). The latest release is v1.1.1.
How does cron402 compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,243 servers); tools 10 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.