Cronofy MCP by usefulapi
io.usefulapi/cronofyusefulapi.iostreamable-httpv1.40.4Scanned
MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.
8 tools: 2 can delete or cancel things and 6 only read.
- Reads private data · 6
- Reads text others write · 2
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
2 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 Cronofy MCP by usefulapi can do
The Cronofy MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (2 tools: cronofy_upsert_event and cronofy_delete_event). 6 tools only read.
6 tools read private data (cronofy_get_account, cronofy_get_userinfo, cronofy_list_calendars and 3 more); 2 tools bring in text other people can write (cronofy_get_account and cronofy_get_userinfo).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
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.
8 tools
Deletes or cancels 2Claude Code: deny
cronofy_delete_eventDeletes an event (by your event_id) from a real connected calendar.No findings
Why it is in this group
- The name "cronofy_delete_event" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Deletes an event (by your event_id) from a real connected calendar. Destructive. API: DELETE /v1/calendars/{calendar_id}/events.
Annotations the server declares
- title: Delete event
- destructiveHint: true
cronofy_upsert_eventCreates or updates an event on a REAL connected calendar (upsert by event_id).No findings
Why it is in this group
- The name "cronofy_upsert_event" says "upsert": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Create or update event
- destructiveHint: true
Only reads 6Show 6 read-only tools
cronofy_get_accountGet the authenticated Cronofy account's details (id, email, name, default tzid, locale).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "cronofy_get_account" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Get the authenticated Cronofy account's details (id, email, name, default tzid, locale). API: GET /v1/account.
Annotations the server declares
- title: Get account
- readOnlyHint: true
cronofy_get_free_busyRead free/busy information across the account's calendars over a time window.Reads private dataNo findings
Why it is in this group
- The name "cronofy_get_free_busy" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "calendar": it reads calendars.
- private-dataThe input names a calendar (input.calendar_ids), and the tool reads: it reads calendars.
Description, as the server wrote it Read free/busy information across the account's calendars over a time window. Returns { pages, free_busy }. API: GET /v1/free_busy.
Annotations the server declares
- title: Get free/busy
- readOnlyHint: true
cronofy_get_userinfoGet the OpenID-style profile of the authenticated user (sub, email, Cronofy profile info).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "cronofy_get_userinfo" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Get the OpenID-style profile of the authenticated user (sub, email, Cronofy profile info). API: GET /v1/userinfo.
Annotations the server declares
- title: Get userinfo
- readOnlyHint: true
cronofy_list_calendarsList all calendars the authenticated account can see (id, name, profile, readonly, primary).Reads private dataNo findings
Why it is in this group
- The name "cronofy_list_calendars" says "list": a word for reading.
What it can reach
- private-dataThe name "cronofy_list_calendars" says "list" and "calendar": it reads calendars.
- private-dataThe description's first sentence says "list" and "calendar": it reads calendars.
Description, as the server wrote it List all calendars the authenticated account can see (id, name, profile, readonly, primary). API: GET /v1/calendars.
Annotations the server declares
- title: List calendars
- readOnlyHint: true
cronofy_list_profilesList the connected calendar accounts/profiles (e.g.Reads private dataNo findings
Why it is in this group
- The name "cronofy_list_profiles" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "calendar": it reads calendars.
Description, as the server wrote it List the connected calendar accounts/profiles (e.g. Google, Office 365) linked to this Cronofy account. API: GET /v1/profiles.
Annotations the server declares
- title: List profiles
- readOnlyHint: true
cronofy_read_eventsRead events across the account's calendars over a time window.Reads private dataNo findings
Why it is in this group
- The name "cronofy_read_events" says "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "calendar": it reads calendars.
- private-dataThe input names a calendar (input.calendar_ids), and the tool reads: it reads calendars.
Description, as the server wrote it Read events across the account's calendars over a time window. Returns { pages, events }. API: GET /v1/events.
Annotations the server declares
- title: Read events
- readOnlyHint: true
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 outbound.
- Reads private data6
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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.
Looked at Nov 20, 2026, 19:34 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://cronofy.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://cronofy.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
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.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://cronofy.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://cronofy.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http cronofy https://cronofy.usefulapi.io/mcpclaude mcp add --transport http cronofy https://cronofy.usefulapi.io/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__cronofy__cronofy_get_account",
"mcp__cronofy__cronofy_get_userinfo",
"mcp__cronofy__cronofy_list_calendars",
"mcp__cronofy__cronofy_list_profiles",
"mcp__cronofy__cronofy_read_events",
"mcp__cronofy__cronofy_get_free_busy"
],
"ask": [],
"deny": [
"mcp__cronofy__cronofy_upsert_event",
"mcp__cronofy__cronofy_delete_event"
]
}
}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 cronofy. Review it before you use it.
Capability tags behind 6 rules
- mcp__cronofy__cronofy_get_account private-data, untrusted-input
- mcp__cronofy__cronofy_get_userinfo private-data, untrusted-input
- mcp__cronofy__cronofy_list_calendars private-data
- mcp__cronofy__cronofy_list_profiles private-data
- mcp__cronofy__cronofy_read_events private-data
- mcp__cronofy__cronofy_get_free_busy private-data
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/io.usefulapi/cronofy/verify?hash=2535de7cdcf55286ee11de6c626f64eaec74f6e0b0df90e7ac9d01c4fd92aea4" | jq -e '.changed == false'Pinned hash 2535de7cdcf5, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/cronofy/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/cronofy)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Cronofy MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Cronofy MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 8 tools, 2 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 Cronofy MCP by usefulapi delete data?
- Yes. 2 tools can delete, cancel or revoke something: cronofy_upsert_event and cronofy_delete_event.
Can the Cronofy MCP by usefulapi 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 Cronofy MCP by usefulapi have?
- 8 tools: 2 destructive, 6 read. cronofy_upsert_event, cronofy_delete_event, cronofy_get_account, cronofy_get_userinfo, cronofy_list_calendars, cronofy_list_profiles, cronofy_read_events and cronofy_get_free_busy.
Does the Cronofy MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Cronofy MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Cronofy MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.