McpStamp Calendar MCP server
io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflictstheluckystrikestreamable-httpv0.23.0Scanned
Read .ics calendar exports: events in a window, free slots, double bookings, new .ics files.
12 tools: 1 can delete or cancel things, 2 do something that can't be undone, 5 change things and 4 only read.
- Reads private data · 3
- Reads text others write · 1
- Can send data out · 4
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 2 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the McpStamp Calendar MCP server can do
The McpStamp Calendar MCP server is published by the GitHub account theluckystrike. It has 12 tools. It can delete or cancel things (1 tool: ics_forget), do things that cannot be undone, such as sending, paying or publishing (free_busy and event_export) and create or change data (5 tools: license_activate, ics_import, conflicts, next_event and 1 more). 4 tools only read.
3 tools read private data (calendars_list, events_list and conflicts); 1 tool brings in text other people can write (license_status); 4 tools can send data out of your system (ics_import, free_busy, conflicts and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.23.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.
12 tools
Deletes or cancels 1Claude Code: deny
ics_forgetRemove one imported calendar by name and delete this server's local copy of its .ics, freeing a slot.1 finding
Why it is in this group
- The description's first verb is "remove": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "ics_forget" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "remove": a word for removing or ending something.
Description, as the server wrote it Remove one imported calendar by name and delete this server's local copy of its .ics, freeing a slot. Your own calendar and the source file are untouched. ics_import replaces a name in place.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Can't be undone 2Claude Code: ask
event_exportCall this tool to write chosen events to a new .ics file you can send or import elsewhere.Can send data out1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "event_export" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
Description, as the server wrote it Call this tool to write chosen events to a new .ics file you can send or import elsewhere. Pass either ids (from events_list) or a from/to window. Times are written in UTC so the file lands correctly in any client.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
free_busyMerged busy blocks and the free gaps inside your working hours over a day range.Can send data outNo findings
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Merged busy blocks and the free gaps inside your working hours over a day range. Events marked free do not count; whole-day events block the day. Free: 31 days. Use conflicts for overlapping pairs.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 5Claude Code: ask
conflictsFind double bookings: every PAIR of timed events that overlap, with the minutes they collide, across all calendars unless you name one.Reads private dataCan send data out1 finding
Why it is in this group
- The description's first verb is "find": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe description's first sentence says "find" and "calendar": it reads calendars.
- private-dataThe input names a calendar (input.calendar), and the tool reads: it reads calendars.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "conflicts" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "find": a word for reading.
Description, as the server wrote it Find double bookings: every PAIR of timed events that overlap, with the minutes they collide, across all calendars unless you name one. Whole-day events are reported apart. Free: 31 days. free_busy shows gaps.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
event_to_time_entryTake one event and return the exact arguments for the time-tracker's entry_add, so a meeting that already happened becomes billable time without retyping it.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Take one event and return the exact arguments for the time-tracker's entry_add, so a meeting that already happened becomes billable time without retyping it. Writes nothing: pass the JSON straight to entry_add.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
ics_importCall this tool to read a calendar export and keep it under a name.Can send data outNo findings
Why it is in this group
- The name "ics_import" says "import": 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 Call this tool to read a calendar export and keep it under a name. Give path (.ics file), text (contents), or url (public .ics/webcal feed; Pro). Google, Apple, Outlook exports read. Re-importing a name replaces it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
next_eventThe first event not yet started, within the next 366 days, across every imported calendar or one you name.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it The first event not yet started, within the next 366 days, across every imported calendar or one you name. Returns title, times in your zone, how long until it starts, location, attendees and its id.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 4Show 4 read-only tools
calendars_listList imported calendars: name, event-definition count, size, source, import time and free-tier use of the 2 slots.Reads private dataNo findings
Why it is in this group
- The name "calendars_list" says "list": a word for reading.
What it can reach
- private-dataThe name "calendars_list" 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 imported calendars: name, event-definition count, size, source, import time and free-tier use of the 2 slots. It also names stored .ics files with no calendar row. With none it prints the export steps.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
events_listEvery event between two dates, recurring expanded to occurrences, sorted by start.Reads private dataNo findings
Why it is in this group
- The name "events_list" says "list": a word for reading.
What it can reach
- private-dataThe input names a calendar (input.calendar), and the tool reads: it reads calendars.
Description, as the server wrote it Every event between two dates, recurring expanded to occurrences, sorted by start. Times shown in your zone (profile's, else this machine's) unless zone passed. Each id works for event_export or event_to_time_entry.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
events_searchFind events whose title, description, location or attendees contain a phrase.No findings
Why it is in this group
- The name "events_search" says "search": a word for reading.
Description, as the server wrote it Find events whose title, description, location or attendees contain a phrase. Searches every imported calendar. Without from/to it looks a year back and a year forward on Pro, and the free window either side of today.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
license_statusReport this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL.Reads text others writeNo findings
Why it is in this group
- The name "license_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.
12 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out4
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__calendar-ics-reader-events-freebusy-conflicts__license_status"
]
}
}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:29 UTC, unchanged since Nov 6, 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
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/calendar
- Authorization servers
- https://mcp.zovo.one
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 destructive, 2 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.zovo.one/mcp/calendar: tools/list returned 12 tools to an anonymous client, including ics_forget (destructive), free_busy (irreversible), event_export (irreversible), license_activate (write), ics_import (write) and 3 more
Posture changes
- Nov 6, 2026
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/calendar
Findings
Matches of fixed checks, with the text they matched.
- Warnconflicts
The server marks "conflicts" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "find": a word for reading.
- Warnevent_export
The server marks "event_export" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
- Warnics_forget
The server marks "ics_forget" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "remove": a word for removing or ending something.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/calendar.View diff
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/calendar
Install
Pinned to version 0.23.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http calendar-ics-reader-events-freebusy-conflicts https://mcp.zovo.one/mcp/calendarclaude mcp add --transport http calendar-ics-reader-events-freebusy-conflicts https://mcp.zovo.one/mcp/calendarRun 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__calendar-ics-reader-events-freebusy-conflicts__license_status",
"mcp__calendar-ics-reader-events-freebusy-conflicts__calendars_list",
"mcp__calendar-ics-reader-events-freebusy-conflicts__events_list",
"mcp__calendar-ics-reader-events-freebusy-conflicts__events_search"
],
"ask": [
"mcp__calendar-ics-reader-events-freebusy-conflicts__license_activate",
"mcp__calendar-ics-reader-events-freebusy-conflicts__ics_import",
"mcp__calendar-ics-reader-events-freebusy-conflicts__free_busy",
"mcp__calendar-ics-reader-events-freebusy-conflicts__conflicts",
"mcp__calendar-ics-reader-events-freebusy-conflicts__next_event",
"mcp__calendar-ics-reader-events-freebusy-conflicts__event_export",
"mcp__calendar-ics-reader-events-freebusy-conflicts__event_to_time_entry"
],
"deny": [
"mcp__calendar-ics-reader-events-freebusy-conflicts__ics_forget"
]
}
}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 calendar-ics-reader-events-freebusy-conflicts. Review it before you use it.
Capability tags behind 7 rules
- mcp__calendar-ics-reader-events-freebusy-conflicts__license_status untrusted-input
- mcp__calendar-ics-reader-events-freebusy-conflicts__ics_import outbound
- mcp__calendar-ics-reader-events-freebusy-conflicts__calendars_list private-data
- mcp__calendar-ics-reader-events-freebusy-conflicts__events_list private-data
- mcp__calendar-ics-reader-events-freebusy-conflicts__free_busy outbound
- mcp__calendar-ics-reader-events-freebusy-conflicts__conflicts private-data, outbound
- mcp__calendar-ics-reader-events-freebusy-conflicts__event_export 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/io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts/verify?hash=66bd5d3e2bfed4789eb088f2e05d8697bddae6d7850cc00298edbf91c73c2f2b" | jq -e '.changed == false'Pinned hash 66bd5d3e2bfe, from Nov 15, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts)Source: MCP Registry · repository. Synced Nov 2, 2026, 03:18 UTC.
McpStamp Calendar MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the McpStamp Calendar MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 8 of which can change, send or delete something, and 3 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 McpStamp Calendar MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: ics_forget.
Can the McpStamp Calendar MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: free_busy and event_export.
What tools does the McpStamp Calendar MCP server have?
- 12 tools: 1 destructive, 2 irreversible, 5 write, 4 read. ics_forget, free_busy, event_export, license_activate, ics_import, conflicts, next_event, event_to_time_entry and 4 more.
Does the McpStamp Calendar MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the McpStamp Calendar MCP server send data to outside services?
- 4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ics_import, free_busy, conflicts and event_export.
Has the McpStamp Calendar MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.