
cron402
io.github.userdefault13Published by GitHub account userdefault13v1.1.1Updated Oct 24, 2026
Schedule webhook calls, pay per run in USDC on Base via x402. Ten tools, built for small models.
Overview
Lets an assistant schedule recurring webhook calls, paying per run in USDC on Base through an agent wallet.
- What you can do
- Provides ten tools for creating and managing scheduled webhook jobs. Free tools cover a guide, wallet balance checks, schedule validation with the next five run times, job status, listing jobs created on this machine, and pausing, resuming or deleting jobs. Paid tools create a job or add prepaid run credits, handling x402 payment automatically. Schedules can be written in plain English or raw cron, and responses include a next_step hint.
- When to use it
- Use it when an assistant should set up recurring outbound webhook calls, such as periodic notifications or integrations, and pay per execution in USDC rather than through a subscription. It suits setups where a small model must drive scheduling safely, since schedules can be validated for free before any paid call.
- Requirements
- Runs locally over stdio via npx, so Node.js is needed. A funded agent wallet private key in CRON402_PRIVATE_KEY is required for paid tools; without it the server starts read-only and free tools still work. Optional variables: CRON402_NETWORK (default eip155:8453, Base mainnet), CRON402_API_URL, and CRON402_STATE_DIR (default ~/.cron402). Network access to the cron402 API is required.
Installation
In SourceWeft
- Open cron402 in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
cron402-mcp
MCP server for cron402 — schedule webhook calls and pay per run in USDC on Base via x402. No accounts, no API keys; your wallet is the credential.
Built so that small models can drive it safely: schedules can be written in plain
English, every schedule can be validated for free before a paid call, and every
response carries an explicit next_step telling the model what to do next.
Price: $0.008 USDC per run · Network: Base mainnet (eip155:8453)
Quick start
Optional env vars:
MCP client config
Cursor / Claude Desktop:
OpenCode (opencode.json):
Tools
Paid tools handle x402 payment automatically. Management tools sign locally with your key.
Designed for weak models
- Plain-English schedules.
"every 15 minutes","every weekday at 9am","every monday at 5pm","weekly"and raw cron all work. Ambiguous or impossible phrases ("every 2 weeks","at teatime") fail loudly with a fix, rather than silently scheduling the wrong thing. - Timezones. Pass
timezone: "America/New_York"and the time-of-day is converted to the UTC cron the API stores, with a DST caveat in the response. - Free dry run.
preview_scheduleshows the next 5 fire times before a cent is spent, andcreate_cronre-validates locally so a bad schedule never costs money. - Money guardrails. Paid tools say
PAIDin their descriptions, name the exact amount, and every response tells the model not to call them twice. - Actionable errors. Insufficient funds, unreachable API, an unowned job or a
localhosttarget each come back as{ ok: false, error, next_step }. - Job memory. Created job ids are written to
~/.cron402/jobs.jsonsolist_cronscan recover them — the API has no list endpoint. - Starts without a key. A missing
CRON402_PRIVATE_KEYdegrades to read-only instead of failing to boot, so the model can explain what is missing.
Agent skill
A drop-in skill teaching an agent this whole workflow lives at
skills/cron402/SKILL.md:
Links
License
MIT
Source: packages/mcp/README.md at commit 9c23532
Tools
0Version history
1- v1.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
