io.usefulapi/cronofy
REMOTE · CRONOFY.USEFULAPI.IO · SCANNED AUG 3
MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.
Available components
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. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · cronofy.usefulapi.io
claude mcp add --transport http io-usefulapi-cronofy https://cronofy.usefulapi.io/mcp
[mcp_servers.io-usefulapi-cronofy] url = "https://cronofy.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-cronofy": {
"type": "remote",
"url": "https://cronofy.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-cronofy --url https://cronofy.usefulapi.io/mcp --transport streamable-http
mcp_servers:
io-usefulapi-cronofy:
url: "https://cronofy.usefulapi.io/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- 2 Aug 26 +55
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- 1 Aug 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 +57
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://cronofy.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 17 Jul 2026 | 15 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | d4f73e614565762f0ef6a17a23cbd2b5 |
| SANs: usefulapi.io, cronofy.usefulapi.io, *.cronofy.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of cronofy.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 429 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cronofy.usefulapi.io/mcp | HTTP error | 429 | |
| http (plaintext) | http://cronofy.usefulapi.io/mcp | Inconclusive | 429 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
cronofy_delete_event Delete event ~79
Deletes an event (by your event_id) from a real connected calendar. Destructive. API: DELETE /v1/calendars/{calendar_id}/events.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | yes | Calendar id the event lives on. |
| event_id | string | yes | YOUR event_id for the event to delete (sent in the JSON body). |
No output schema declared.
No examples provided.
cronofy_get_account Get account ~39
Get the authenticated Cronofy account's details (id, email, name, default tzid, locale). API: GET /v1/account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cronofy_get_free_busy Get free/busy ~156
Read free/busy information across the account's calendars over a time window. Returns { pages, free_busy }. API: GET /v1/free_busy.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | REQUIRED time zone id for the response, e.g. "Etc/UTC". |
No output schema declared.
No examples provided.
cronofy_get_userinfo Get userinfo ~40
Get the OpenID-style profile of the authenticated user (sub, email, Cronofy profile info). API: GET /v1/userinfo.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cronofy_list_calendars List calendars ~41
List all calendars the authenticated account can see (id, name, profile, readonly, primary). API: GET /v1/calendars.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cronofy_list_profiles List profiles ~43
List the connected calendar accounts/profiles (e.g. Google, Office 365) linked to this Cronofy account. API: GET /v1/profiles.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cronofy_read_events Read events ~210
Read events across the account's calendars over a time window. Returns { pages, events }. API: GET /v1/events.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | REQUIRED time zone id for the response, e.g. "Etc/UTC" or "America/New_York". |
No output schema declared.
No examples provided.
cronofy_upsert_event Create or update event ~202
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.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | yes | Target calendar id (from cronofy_list_calendars). |
| description | string | — | Event description/body. |
| end | string | yes | Event end — ISO 8601 datetime or a date (yyyy-mm-dd) string. |
| event_id | string | yes | 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 | yes | Event start — ISO 8601 datetime or a date (yyyy-mm-dd) string. |
| summary | string | yes | Event title/summary. |
| tzid | string | — | Time zone id for the start/end, e.g. "America/New_York". |
No output schema declared.
No examples provided.