Schedules webhook calls and manages recurring tasks using USDC payments on the Base network.
Also known as userdefault13/ai-cron-site, cron402-mcp
- Stars
- 0
- Tools
- 10
- Downloads, 30 days
- —
- Latest version
- 1.1.1
- Last commit
- Oct 26, 2026
- License
- MIT
What is cron402 MCP?
cron402 schedules webhook calls and manages recurring tasks using USDC payments on the Base network. It exposes 10 tools, such as cron402_guide, check_wallet, preview_schedule.
Summary generated from the project's README
About cron402 MCP server
Scheduling webhook calls and managing recurring tasks using USDC payments on the Base network is what cron402 enables for developers. This server allows AI agents to automate webhooks by paying $0.008 USDC per run via the x402 protocol. It operates locally using a private key for authentication, meaning your wallet serves as your credential instead of traditional API keys or accounts.
Users can interact with the server through tools like create_cron, topup_cron, and preview_schedule. The system is designed to work with smaller models by supporting plain-English scheduling instructions such as every weekday at 9am. It includes safety features like free validation through preview_schedule to prevent accidental spending. Management tools like list_crons, pause_cron, and delete_cron allow for full control over active jobs, while the server can start in a read-only mode even without a private key provided.
What you can do with it
- 1Validate a new scheduleCheck if a natural language time expression is valid and see the upcoming execution times before paying.
- 2Automate recurring webhooksSet up a recurring webhook task using simple English instructions and pay for each execution with USDC.
- 3Manage existing cron jobsPause or delete previously created scheduled tasks using local cryptographic signatures.
- 4Monitor wallet fundsVerify the current USDC balance on the Base network to determine how many scheduled runs can be afforded.
Written from the project's README. Every use case is checked against a quote from it.
How to install cron402 MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall cron402 MCP in Claude Code
$ claude mcp add --env 'CRON402_PRIVATE_KEY=<YOUR_CRON402_PRIVATE_KEY>' cron402-mcp -- npx -y cron402-mcpInstall cron402 MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cron402-mcp": {
"command": "npx",
"args": [
"-y",
"cron402-mcp"
],
"env": {
"CRON402_PRIVATE_KEY": "<YOUR_CRON402_PRIVATE_KEY>"
}
}
}
}Install cron402 MCP in VS Code
.vscode/mcp.json
{
"servers": {
"cron402-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cron402-mcp"
],
"env": {
"CRON402_PRIVATE_KEY": "<YOUR_CRON402_PRIVATE_KEY>"
}
}
}
}Install cron402 MCP in VS Code CLI
$ code --add-mcp '{"name":"cron402-mcp","type":"stdio","command":"npx","args":["-y","cron402-mcp"],"env":{"CRON402_PRIVATE_KEY":"<YOUR_CRON402_PRIVATE_KEY>"}}'Install cron402 MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"cron402-mcp": {
"command": "npx",
"args": [
"-y",
"cron402-mcp"
],
"env": {
"CRON402_PRIVATE_KEY": "<YOUR_CRON402_PRIVATE_KEY>"
}
}
}
}Install cron402 MCP in Codex
$ codex mcp add cron402-mcp --env 'CRON402_PRIVATE_KEY=<YOUR_CRON402_PRIVATE_KEY>' -- npx -y cron402-mcpInstall cron402 MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.cron402-mcp] command = "npx" args = ["-y", "cron402-mcp"] [mcp_servers.cron402-mcp.env] CRON402_PRIVATE_KEY = "<YOUR_CRON402_PRIVATE_KEY>"
Install cron402 MCP in Gemini CLI
$ gemini mcp add -s user -e 'CRON402_PRIVATE_KEY=<YOUR_CRON402_PRIVATE_KEY>' cron402-mcp npx -- -y cron402-mcpInstall cron402 MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cron402-mcp": {
"command": "npx",
"args": [
"-y",
"cron402-mcp"
],
"env": {
"CRON402_PRIVATE_KEY": "<YOUR_CRON402_PRIVATE_KEY>"
}
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for cron402-mcp 1.1.1 in an isolated container with no network and no keys. It answered and listed 10 tools.
cron402 MCP tools 10
Read from the server with tools/listcron402_guideREAD 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_walletFree. 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_scheduleFree, 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.
create_cronPAID: 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.
topup_cronPAID: 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.
get_cronFree. 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_cronsFree. 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_cronFree. 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.
resume_cronFree. 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.
delete_cronFree 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.
Configuration
CRON402_PRIVATE_KEYSecretAgent wallet private key (0x…). Fund with USDC on Base mainnet or Sepolia. Without it the server starts read-only: the free tools still work.
CRON402_API_URLcron402 API base URL. Defaults to the production Worker.
CRON402_NETWORKCAIP-2 network id. Default eip155:8453 (Base mainnet); use eip155:84532 for Sepolia.
CRON402_STATE_DIRDirectory where created job ids are remembered so list_crons can recover them. Defaults to ~/.cron402.
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableuserdefault13/ai-cron-site is public and reachablegithub.com/userdefault13/ai-cron-site ↗Pass
- Package names this repository as its sourcecron402-mcp names userdefault13/ai-cron-site as sourcenpmjs.com/package/cron402-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-26github.com/userdefault13/ai-cron-site ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from cron402-mcpPass
- No critical advisory in the package or its dependencies119 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model10 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubcron402-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
export CRON402_PRIVATE_KEY=0x... # fund with USDC on Base
npx -y cron402-mcp
Optional env vars:
| Variable | Default | Description |
|---|---|---|
CRON402_PRIVATE_KEY |
(required for paid tools) | Agent wallet private key. Without it the server still starts and the free tools work. |
CRON402_NETWORK |
eip155:8453 |
CAIP-2 id; use eip155:84532 for Base Sepolia |
CRON402_API_URL |
production Worker | Override API base URL |
CRON402_STATE_DIR |
~/.cron402 |
Where created job ids are remembered for list_crons |
MCP client config
Cursor / Claude Desktop:
{
"mcpServers": {
"cron402": {
"command": "npx",
"args": ["-y", "cron402-mcp"],
"env": {
"CRON402_PRIVATE_KEY": "0x..."
}
}
}
}
OpenCode (opencode.json):
{
"mcp": {
"cron402": {
"type": "local",
"command": ["npx", "-y", "cron402-mcp"],
"environment": {
"CRON402_PRIVATE_KEY": "0x..."
},
"enabled": true
}
}
}
Tools
| Tool | Cost | Description |
|---|---|---|
cron402_guide |
free | The whole procedure, prices and rules — the tool a model should read first |
check_wallet |
free | Address, network, USDC/ETH balance, and how many runs it can afford |
preview_schedule |
free | Validate a schedule and list the next 5 run times in UTC |
create_cron |
$0.008 | Create a scheduled webhook job (includes 1 run credit) |
topup_cron |
$0.008–$0.80 | Add 1, 10, or 100 prepaid run credits |
get_cron |
free | Job status, credits, last 20 executions |
list_crons |
free | Jobs created from this machine, with live status |
pause_cron |
free | Pause a job (EIP-712 signed) |
resume_cron |
free | Resume a paused job (requires credits) |
delete_cron |
free | Permanently delete a job (EIP-712 signed) |
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:
mkdir -p .claude/skills/cron402
curl -sL https://raw.githubusercontent.com/userdefault13/ai-cron-site/main/skills/cron402/SKILL.md \
-o .claude/skills/cron402/SKILL.md
Links
License
MIT
cron402 MCP questions
How do I add cron402 MCP to Claude Code?
Run claude mcp add --env 'CRON402_PRIVATE_KEY=<YOUR_CRON402_PRIVATE_KEY>' cron402-mcp -- npx -y cron402-mcp in your terminal. Add --scope user to make it available in every project.
How do I add cron402 MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does cron402 MCP provide?
It exposes 10 tools, including cron402_guide, check_wallet, preview_schedule, create_cron, topup_cron.
Do I need an API key to use this server?
No, you do not need accounts or API keys; your crypto wallet serves as your credential.
Can I test a schedule before paying for it?
Yes, you can use the preview_schedule tool to validate a schedule and see the next five run times for free.
What happens if I don't provide a private key?
The server will still start and allow you to use free tools, but paid tools will not work.