402cron MCP server
com.402cron/402cron402cron.comstreamable-httpv1.0.2Scanned
Paid cron for AI agents: we call your https URL on schedule, signed. No account, paid with x402.
16 tools: 8 can delete or cancel things, 2 change things and 6 only read.
- Reads private data · 1
- Reads text others write · 5
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
8 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the 402cron MCP server can do
The 402cron MCP server is published by 402cron.com, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (8 tools: create_task, update_task, pause_task, resume_task and 4 more) and create or change data (2 tools: restore_task and verify_destination). 6 tools only read.
1 tool reads private data (get_docs); 5 tools bring in text other people can write (create_task, update_task, resume_task and 2 more).
The fixed checks matched 4 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Deletes or cancels 8Claude Code: deny
create_taskRegister a schedule against a destination you have already verified.Reads text others write2 findings
Why it is in this group
- The name "create_task" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.headers.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.headers.description: "...elivery. Stored ENCRYPTED at rest — put credentials here, never in the body."
- Info
The input schema at properties.body.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.body.description: "...ored in the clear, so it must not carry credentials. A non-string is serialized as JSON."
Description, as the server wrote it Register a schedule against a destination you have already verified. Idempotent on "name": the same name updates the existing task instead of creating a second one. Creating costs nothing; each delivery ATTEMPT costs one credit.
Annotations the server declares
- title: Create or update a scheduled task
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
delete_destinationRemove a claimed URL.No findings
Why it is in this group
- The name "delete_destination" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Remove a claimed URL. Refused while a task still points at it — delete the task first.
Annotations the server declares
- title: Delete a destination
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
delete_taskMove the task to the recycle bin.No findings
Why it is in this group
- The name "delete_task" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Move the task to the recycle bin. It stops firing immediately and can be restored for 30 days with restore_task; after that it is unrecoverable. Credits already spent are not refunded.
Annotations the server declares
- title: Delete a task
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
pause_taskStop firing until you resume.No findings
Why it is in this group
- The description's first verb is "stop": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Stop firing until you resume. Nothing is charged while a task is paused.
Annotations the server declares
- title: Pause a task
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
register_destinationClaim an https:// URL you control.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Claim an https:// URL you control. We answer with a challenge and a SIGNING SECRET that is shown ONCE and never again — store it before you do anything else; it is what lets you verify that a delivery really came from us. The permission covers that path and everything beneath it, nothing above. Verification is one request from us to the exact URL you registered: POST, headers X-402cron-Challenge: <value> and X-402cron-Event: verify, JSON body {"challenge":"<value>"}. Reply within 5 seconds, without a redirect, with a body that is the bare value or {"challenge":"<value>"}; we read the first 512 bytes and do not check the HTTP status (2xx is fine). Then call POST /api/destinations/{id}/verify within 15 minutes of registering. A fixed-response webhook cannot pass: you need an endpoint you can program. Registering a URL that is still pending issues a new challenge and a new signing secret every time — the old secret immediately stops verifying deliveries; a verified URL is left untouched unless you add ?rotate=1. The daily verification allowance (10 per destination, 40 per client, UTC day) does not reset on re-registration.
Annotations the server declares
- title: Register a destination URL
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
resume_taskStart firing again on the schedule.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "start": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Start firing again on the schedule. Refused if your balance is empty — buy deliveries first.
Annotations the server declares
- title: Resume a paused task
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
run_task_nowDeliver immediately, outside the schedule.Reads text others writeNo findings
Why it is in this group
- The name "run_task_now" says "run": a word for a change.
- The description's first verb is "deliver": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Deliver immediately, outside the schedule. THIS COSTS ONE CREDIT per attempt, exactly like a scheduled firing, and a timeout or unreachable host is retried up to three times — so one call can cost up to three credits. Use it to test a destination.
Annotations the server declares
- title: Fire a task once, right now
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
update_taskChange the schedule, destination, method, timeout, headers or body of an existing task.Reads text others write2 findings
Why it is in this group
- The name "update_task" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.headers.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.headers.description: "...elivery. Stored ENCRYPTED at rest — put credentials here, never in the body."
- Info
The input schema at properties.body.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.body.description: "...ored in the clear, so it must not carry credentials. A non-string is serialized as JSON."
Description, as the server wrote it Change the schedule, destination, method, timeout, headers or body of an existing task. Omit a field to leave it unchanged — sending null is refused, because "unchanged" and "cleared" must not look the same. State is NOT editable here: use pause_task and resume_task.
Annotations the server declares
- title: Edit a task
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Changes things 2Claude Code: ask
restore_taskBring a task back from the recycle bin within 30 days.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Bring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.
Annotations the server declares
- title: Restore a deleted task
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_destinationVerification is one request from us to the exact URL you registered: POST, headers X-402cron-Challenge: <value> and X-402cron-Event: verify, JSON body {"challenge":"<value>"}.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Verification is one request from us to the exact URL you registered: POST, headers X-402cron-Challenge: <value> and X-402cron-Event: verify, JSON body {"challenge":"<value>"}. Reply within 5 seconds, without a redirect, with a body that is the bare value or {"challenge":"<value>"}; we read the first 512 bytes and do not check the HTTP status (2xx is fine). Then call POST /api/destinations/{id}/verify within 15 minutes of registering. A fixed-response webhook cannot pass: you need an endpoint you can program. Registering a URL that is still pending issues a new challenge and a new signing secret every time — the old secret immediately stops verifying deliveries; a verified URL is left untouched unless you add ?rotate=1. The daily verification allowance (10 per destination, 40 per client, UTC day) does not reset on re-registration. Until this passes, no task may point at the destination.
Annotations the server declares
- title: Verify a registered destination
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 6Show 6 read-only tools
get_docsOne section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits.Reads private dataNo findings
Why it is in this group
- The name "get_docs" says "get": a word for reading.
What it can reach
- private-dataThe name "get_docs" says "get" and "doc": it reads documents.
Description, as the server wrote it One section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit `section` to get the whole document.
Annotations the server declares
- title: Machine documentation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_pricingWhat a delivery costs, which packs exist, and the exact x402 payment requirements for each.No findings
Why it is in this group
- The name "get_pricing" says "get": a word for reading.
Description, as the server wrote it What a delivery costs, which packs exist, and the exact x402 payment requirements for each. Balance is counted in DELIVERIES, not money, and packs never expire. Call this before buying.
Annotations the server declares
- title: Pricing and payment requirements
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_service_statusWhether the service is currently selling, on which network, and if not — why not.No findings
Why it is in this group
- The name "get_service_status" says "get": a word for reading.
Description, as the server wrote it Whether the service is currently selling, on which network, and if not — why not. This is configuration, not liveness: the full health endpoint is at /health.
Annotations the server declares
- title: Is the service selling right now
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_taskA single task: schedule, destination, state, next run, and how many failures in a row it carries.No findings
Why it is in this group
- The name "get_task" says "get": a word for reading.
Description, as the server wrote it A single task: schedule, destination, state, next run, and how many failures in a row it carries.
Annotations the server declares
- title: One task with its full state
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_destinationsThe URLs you have claimed and whether each is verified.No findings
Why it is in this group
- The name "list_destinations" says "list": a word for reading.
Description, as the server wrote it The URLs you have claimed and whether each is verified. The signing secrets are never shown again.
Annotations the server declares
- title: List your destinations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_tasksYour tasks and their state.No findings
Why it is in this group
- The name "list_tasks" says "list": a word for reading.
Description, as the server wrote it Your tasks and their state. Needs your management token as an Authorization header on this connection.
Annotations the server declares
- title: List your scheduled tasks
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:33 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 10
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 10 tools that change things (8 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://402cron.com/mcp: tools/list returned 16 tools to an anonymous client, including create_task (destructive), update_task (destructive), pause_task (destructive), resume_task (destructive), run_task_now (destructive) and 5 more
Findings
Matches of fixed checks, with the text they matched.
- Infocreate_task
The input schema at properties.headers.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.headers.description: "...elivery. Stored ENCRYPTED at rest — put credentials here, never in the body."
- Infocreate_task
The input schema at properties.body.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.body.description: "...ored in the clear, so it must not carry credentials. A non-string is serialized as JSON."
- Infoupdate_task
The input schema at properties.headers.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.headers.description: "...elivery. Stored ENCRYPTED at rest — put credentials here, never in the body."
- Infoupdate_task
The input schema at properties.body.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.body.description: "...ored in the clear, so it must not carry credentials. A non-string is serialized as JSON."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools16 changed.~16 changedView diff
- Changed:create_taskDeletes or cancelsannotations
- Changed:delete_destinationDeletes or cancelsannotations
- Changed:delete_taskDeletes or cancelsannotations
- Changed:get_docsOnly readsannotations
- Changed:get_pricingOnly readsannotations
- Changed:get_service_statusOnly readsannotations
- Changed:get_taskOnly readsannotations
- Changed:list_destinationsOnly readsannotations
- Changed:list_tasksOnly readsannotations
- Changed:pause_taskDeletes or cancelsannotations
- Changed:register_destinationDeletes or cancelsannotations
- Changed:restore_taskChanges thingsannotations
- Changed:resume_taskDeletes or cancelsannotations
- Changed:run_task_nowDeletes or cancelsannotations
- Changed:update_taskDeletes or cancelsannotations
- Changed:verify_destinationChanges thingsannotations
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http 402cron https://402cron.com/mcpclaude mcp add --transport http 402cron https://402cron.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__402cron__get_pricing",
"mcp__402cron__get_docs",
"mcp__402cron__get_service_status",
"mcp__402cron__list_tasks",
"mcp__402cron__get_task",
"mcp__402cron__list_destinations"
],
"ask": [
"mcp__402cron__restore_task",
"mcp__402cron__verify_destination"
],
"deny": [
"mcp__402cron__create_task",
"mcp__402cron__update_task",
"mcp__402cron__pause_task",
"mcp__402cron__resume_task",
"mcp__402cron__run_task_now",
"mcp__402cron__delete_task",
"mcp__402cron__register_destination",
"mcp__402cron__delete_destination"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as 402cron. Review it before you use it.
Capability tags behind 6 rules
- mcp__402cron__get_docs private-data
- mcp__402cron__create_task untrusted-input
- mcp__402cron__update_task untrusted-input
- mcp__402cron__resume_task untrusted-input
- mcp__402cron__run_task_now untrusted-input
- mcp__402cron__verify_destination untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.402cron/402cron/verify?hash=efd30cf0c7148f0a5b292efd2c66a5ee7a72ba120b8b75f035399a34d6d46e2f" | jq -e '.changed == false'Pinned hash efd30cf0c714, from Nov 17, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.402cron/402cron/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.402cron/402cron)Source: MCP Registry · repository. Synced Nov 17, 2026, 23:17 UTC.
402cron MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the 402cron MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 10 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the 402cron MCP server delete data?
- Yes. 8 tools can delete, cancel or revoke something: create_task, update_task, pause_task, resume_task, run_task_now, delete_task and 2 more.
Can the 402cron MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the 402cron MCP server have?
- 16 tools: 8 destructive, 2 write, 6 read. create_task, update_task, pause_task, resume_task, run_task_now, delete_task, register_destination, delete_destination and 8 more.
Does the 402cron MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the 402cron MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the 402cron MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.