# Task Scheduler (remote · cron.memoryapi.org)

Schedule and manage recurring or one-shot tasks

- Trust score: 63/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `cron.memoryapi.org`: 63/100 (this document), [markdown](https://verifymcp.io/servers/org-memoryapi-cron/cron.md), [page](https://verifymcp.io/servers/org-memoryapi-cron/cron)

## Channel facts

- Endpoint: `https://cron.memoryapi.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 287 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.org-memoryapi-cron]
url = "https://cron.memoryapi.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-memoryapi-cron": {
      "type": "remote",
      "url": "https://cron.memoryapi.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-memoryapi-cron --url https://cron.memoryapi.org/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-memoryapi-cron:
    url: "https://cron.memoryapi.org/mcp"
```

### Other

```json
{
  "mcpServers": {
    "org-memoryapi-cron": {
      "type": "http",
      "url": "https://cron.memoryapi.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (4)

### `schedule_task` (~130 tokens)

Register a persistent cron schedule that runs even when your agent session ends. Specify a URL to call, how often, and for how long.

Input parameters:

- `agent_id` (string, required): Your agent identifier
- `body` (string): Optional JSON body for POST requests
- `duration_days` (number): How many days to keep running (max 30, default 7)
- `interval_minutes` (number, required): How often to run (minimum 15 minutes)
- `method` (string): HTTP method: GET or POST (default: GET)
- `url` (string, required): HTTPS URL to call on each execution

### `check_schedule` (~60 tokens)

Check the status of a cron schedule — is it active, when does it next run, how many times has it executed?

Input parameters:

- `agent_id` (string): Alternatively list all schedules for this agent
- `schedule_id` (string): Schedule UUID from registration

### `cancel_schedule` (~45 tokens)

Cancel an active cron schedule to stop all future executions immediately.

Input parameters:

- `agent_id` (string): Agent ID for ownership verification
- `schedule_id` (string, required): Schedule UUID to cancel

### `get_execution_history` (~52 tokens)

View recent execution history for a schedule — status codes, response previews, and timing.

Input parameters:

- `limit` (number): Number of executions to return (max 50)
- `schedule_id` (string, required): Schedule UUID

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-memoryapi-cron/cron#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 63
- 2026-08-01: 62
- 2026-07-31: 62
- 2026-07-30: 62
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://cron.memoryapi.org/mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-memoryapi-cron/cron/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-memoryapi-cron/cron/changelog.json
- HTML version of this page: https://verifymcp.io/servers/org-memoryapi-cron/cron