# io.usefulapi/cronofy (remote · cronofy.usefulapi.io)

MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.

- Trust score: 18/100 (low)
- Change this week: −51
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `cronofy.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-cronofy/cronofy.md), [page](https://verifymcp.io/servers/io-usefulapi-cronofy/cronofy)

## Channel facts

- Endpoint: `https://cronofy.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 429.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-cronofy https://cronofy.usefulapi.io/mcp
```

### Codex

```toml
[mcp_servers.io-usefulapi-cronofy]
url = "https://cronofy.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-cronofy": {
      "type": "remote",
      "url": "https://cronofy.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-cronofy --url https://cronofy.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-cronofy:
    url: "https://cronofy.usefulapi.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-cronofy": {
      "type": "http",
      "url": "https://cronofy.usefulapi.io/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-03 (score 18, −55)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified

### 2026-08-02 (score 73, +55)

- [security improvement] Authorization: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20

### 2026-08-01 (score 18, −54)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 72, +3)

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

### 2026-07-30 (score 69, −2)

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

### 2026-07-29 (score 71, +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-28 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 69, +57)

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

## MCP tools (8)

### `cronofy_get_account` (~39 tokens)

Get account

Get the authenticated Cronofy account's details (id, email, name, default tzid, locale). API: GET /v1/account.

### `cronofy_get_userinfo` (~40 tokens)

Get userinfo

Get the OpenID-style profile of the authenticated user (sub, email, Cronofy profile info). API: GET /v1/userinfo.

### `cronofy_list_calendars` (~41 tokens)

List calendars

List all calendars the authenticated account can see (id, name, profile, readonly, primary). API: GET /v1/calendars.

### `cronofy_list_profiles` (~43 tokens)

List profiles

List the connected calendar accounts/profiles (e.g. Google, Office 365) linked to this Cronofy account. API: GET /v1/profiles.

### `cronofy_read_events` (~210 tokens)

Read events

Read events across the account's calendars over a time window. Returns { pages, events }. API: GET /v1/events.

Input parameters:

- `calendar_ids` (array): Restrict to these calendar ids (sent as repeated calendar_ids[] params).
- `from` (string): Start of the window — date (yyyy-mm-dd) or ISO 8601 datetime.
- `include_deleted` (boolean): Include deleted events. Default false.
- `include_managed` (boolean): Include events created via the Cronofy API. Default false.
- `last_modified` (string): Only events modified since this ISO 8601 datetime.
- `only_managed` (boolean): Return only events created via the Cronofy API. Default false.
- `to` (string): End of the window — date (yyyy-mm-dd) or ISO 8601 datetime.
- `tzid` (string, required): REQUIRED time zone id for the response, e.g. "Etc/UTC" or "America/New_York".

### `cronofy_get_free_busy` (~156 tokens)

Get free/busy

Read free/busy information across the account's calendars over a time window. Returns { pages, free_busy }. API: GET /v1/free_busy.

Input parameters:

- `calendar_ids` (array): Restrict to these calendar ids (sent as repeated calendar_ids[] params).
- `from` (string): Start of the window — date (yyyy-mm-dd) or ISO 8601 datetime.
- `include_managed` (boolean): Include events created via the Cronofy API. Default false.
- `to` (string): End of the window — date (yyyy-mm-dd) or ISO 8601 datetime.
- `tzid` (string, required): REQUIRED time zone id for the response, e.g. "Etc/UTC".

### `cronofy_upsert_event` (~202 tokens)

Create or update event

Creates or updates an event on a REAL connected calendar (upsert by event_id). This writes to the user's actual calendar. API: POST /v1/calendars/{calendar_id}/events.

Input parameters:

- `calendar_id` (string, required): Target calendar id (from cronofy_list_calendars).
- `description` (string): Event description/body.
- `end` (string, required): Event end — ISO 8601 datetime or a date (yyyy-mm-dd) string.
- `event_id` (string, required): YOUR unique id for the event. Re-using it updates the same event.
- `location_description` (string): Free-text location (sent as location.description).
- `start` (string, required): Event start — ISO 8601 datetime or a date (yyyy-mm-dd) string.
- `summary` (string, required): Event title/summary.
- `tzid` (string): Time zone id for the start/end, e.g. "America/New_York".

### `cronofy_delete_event` (~79 tokens)

Delete event

Deletes an event (by your event_id) from a real connected calendar. Destructive. API: DELETE /v1/calendars/{calendar_id}/events.

Input parameters:

- `calendar_id` (string, required): Calendar id the event lives on.
- `event_id` (string, required): YOUR event_id for the event to delete (sent in the JSON body).

## Diagnostics

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

## Score history

- 2026-08-03: 18
- 2026-08-02: 73
- 2026-08-01: 18
- 2026-07-31: 72
- 2026-07-30: 69
- 2026-07-29: 71
- 2026-07-28: 70
- 2026-07-27: 69
- 2026-07-26: 12

## Links

- Remote endpoint: https://cronofy.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-cronofy/cronofy/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-cronofy/cronofy/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-cronofy/cronofy