Skip to content

Task Scheduler MCP server

org.memoryapi/cronmemoryapi.orgstreamable-httpv1.0.0Scanned

Schedule and manage recurring or one-shot tasks

4 tools: 1 can delete or cancel things, 2 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Task Scheduler MCP server can do

The Task Scheduler MCP server is published by memoryapi.org, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: cancel_schedule) and create or change data (2 tools: schedule_task and check_schedule). 1 tool only reads.

1 tool can send data out of your system (schedule_task).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

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.

4 tools

Deletes or cancels 1Claude Code: deny
  • cancel_scheduleCancel an active cron schedule to stop all future executions immediately.No findings

    Why it is in this group

    • The name "cancel_schedule" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    Cancel an active cron schedule to stop all future executions immediately.
Changes things 2Claude Code: ask
  • check_scheduleCheck the status of a cron schedule — is it active, when does it next run, how many times has it executed?No findings

    Why it is in this group

    • The name "check_schedule" says "schedule": a word for a change.
    Description, as the server wrote it
    Check the status of a cron schedule — is it active, when does it next run, how many times has it executed?
  • schedule_taskRegister a persistent cron schedule that runs even when your agent session ends.Can send data outNo findings

    Why it is in this group

    • The name "schedule_task" says "schedule": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Register a persistent cron schedule that runs even when your agent session ends. Specify a URL to call, how often, and for how long.
Only reads 1Show 1 read-only tool
  • get_execution_historyView recent execution history for a schedule — status codes, response previews, and timing.No findings

    Why it is in this group

    • The name "get_execution_history" says "get": a word for reading.
    Description, as the server wrote it
    View recent execution history for a schedule — status codes, response previews, and timing.

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 private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:24 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
3
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://cron.memoryapi.org/.well-known/oauth-protected-resource
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 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://cron.memoryapi.org/mcp: tools/list returned 4 tools to an anonymous client, including cancel_schedule (destructive), schedule_task (write), check_schedule (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http cron https://cron.memoryapi.org/mcp
claude mcp add --transport http cron https://cron.memoryapi.org/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__cron__get_execution_history"
    ],
    "ask": [
      "mcp__cron__schedule_task",
      "mcp__cron__check_schedule"
    ],
    "deny": [
      "mcp__cron__cancel_schedule"
    ]
  }
}

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 cron. Review it before you use it.

Capability tags behind 1 rule
  • mcp__cron__schedule_task outbound

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/org.memoryapi/cron/verify?hash=78fd07a0699506fa4f1c50f251469f1b0222e1dc708865de8d2a288ffd371a9e" | jq -e '.changed == false'

Pinned hash 78fd07a06995, from Nov 21, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.memoryapi/cron/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.memoryapi/cron
[![Anlyon Radar](https://radar.anlyon.com/badge/org.memoryapi/cron.svg)](https://radar.anlyon.com/servers/org.memoryapi/cron)

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

Task Scheduler MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Task Scheduler MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 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 Task Scheduler MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_schedule.

Can the Task Scheduler 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 Task Scheduler MCP server have?

4 tools: 1 destructive, 2 write, 1 read. cancel_schedule, schedule_task, check_schedule and get_execution_history.

Does the Task Scheduler MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Task Scheduler MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): schedule_task.

Has the Task Scheduler MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.