A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
402cron is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Paid cron for AI agents: we call your https URL on schedule, signed. No account, paid with x402.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http 402cron-mcp https://402cron.com/mcp
# 2 — ask your agent for something these tools do
# get_pricing, get_docs, get_service_status and 13 more
402cron costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http 402cron-mcp https://402cron.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
One section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit section to get the whole document.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | string | no | Which section to return. Omit for all of 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.
No parameter schema on file.
Your tasks and their state. Needs your management token as an Authorization header on this connection.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Filter by state: live (default), all, or one exact state such as active or paused_by_client. |
| limit | integer | no | How many to return. |
| after | string | no | Cursor from a previous page. |
A single task: schedule, destination, state, next run, and how many failures in a row it carries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Task id (UUID), as returned by create_task or list_tasks. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Your name for the task. Unique among your live tasks; creating with an existing name updates it. |
| cron | string | yes | 5 fields, UTC only, one minute at the finest. Operators: * a-b a,b */n a-b/n. Names: SUN-SAT (day), JAN-DEC (month). Macros: @yearly @annually @monthly @weekly @daily @midnight @hourly. Day-of-week is |
| url | string | yes | The https:// destination. It must already be registered and verified — see register_destination. |
| method | string | no | HTTP method of the delivery. Default POST. GET and HEAD carry no body. |
| timeoutMs | integer | no | How long we wait for your server, 250-2000 ms. Answer 202 and do the work behind it. |
| headers | object | no | Headers we send with the delivery. Stored ENCRYPTED at rest — put credentials here, never in the body. |
| body | no | The body we send. Stored in the clear, so it must not carry credentials. A non-string is serialized as JSON. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Task id (UUID), as returned by create_task or list_tasks. |
| name | string | no | Your name for the task. Unique among your live tasks; creating with an existing name updates it. |
| cron | string | no | 5 fields, UTC only, one minute at the finest. Operators: * a-b a,b */n a-b/n. Names: SUN-SAT (day), JAN-DEC (month). Macros: @yearly @annually @monthly @weekly @daily @midnight @hourly. Day-of-week is |
| url | string | no | The https:// destination. It must already be registered and verified — see register_destination. |
| method | string | no | HTTP method of the delivery. Default POST. GET and HEAD carry no body. |
| timeoutMs | integer | no | How long we wait for your server, 250-2000 ms. Answer 202 and do the work behind it. |
| headers | object | no | Headers we send with the delivery. Stored ENCRYPTED at rest — put credentials here, never in the body. |
| body | no | The body we send. Stored in the clear, so it must not carry credentials. A non-string is serialized as JSON. |
Stop firing until you resume. Nothing is charged while a task is paused.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Task id (UUID), as returned by create_task or list_tasks. |
Start firing again on the schedule. Refused if your balance is empty — buy deliveries first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Task id (UUID), as returned by create_task or list_tasks. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Task id (UUID), as returned by create_task or list_tasks. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Task id (UUID), as returned by create_task or list_tasks. |
Bring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Task id (UUID), as returned by create_task or list_tasks. |
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:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The https:// URL you control. |
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}/ver
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Destination id, as returned by register_destination. |
The URLs you have claimed and whether each is verified. The signing secrets are never shown again.
No parameter schema on file.
Remove a claimed URL. Refused while a task still points at it — delete the task first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Destination id, as returned by register_destination. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install 402cron or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish 402cron can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.