Skip to content

Smart Calendars AI MCP server

ai.smartcalendars/smart-calendars-aismartcalendars.aistreamable-httpv2.0.0Scanned

Create and update subscription calendars from ChatGPT, Claude, or Codex.

7 tools: 2 can delete or cancel things, 2 change things and 3 only read.

Tools: 2 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 4
  • Can send data out · 0
  • 5 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Smart Calendars AI MCP server can do

The Smart Calendars AI MCP server is published by smartcalendars.ai, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (2 tools: apply_feed_changes and deactivate_feed) and create or change data (2 tools: create_feed and reactivate_feed). 3 tools only read.

1 tool reads private data (list_feeds); 4 tools bring in text other people can write (create_feed, apply_feed_changes, deactivate_feed and 1 more).

The fixed checks matched 5 findings (credentials-mention and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 2.0.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.

7 tools

Deletes or cancels 2Claude Code: deny
  • apply_feed_changesSaves one revision to one existing calendar feed owned by the connected account for a user-approved schedule change.Reads text others write4 findings

    Why it is in this group

    • The name "apply_feed_changes" says "apply": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.operations.items.oneOf[0].properties.event.properties.description.description mentions "credentials".

      Matched text

      inputSchema.properties.operations.items.oneOf[0].properties.event.properties.description.description: "...blish with this calendar. Chat history, credentials, health records and unrelated personal..."

      What this check looks for
    • Info

      The input schema at properties.operations.items.oneOf[1].properties.set.properties.description.description mentions "credentials".

      Matched text

      inputSchema.properties.operations.items.oneOf[1].properties.set.properties.description.description: "...blish with this calendar. Chat history, credentials, health records and unrelated personal..."

      What this check looks for
    • Info

      The input schema at properties.operations.items.oneOf[3].properties.set.properties.description.description mentions "credentials".

      Matched text

      inputSchema.properties.operations.items.oneOf[3].properties.set.properties.description.description: "...blish with this calendar. Chat history, credentials, health records and unrelated personal..."

      What this check looks for
    • Info

      The description is 4,911 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...does not confirm a subscription; confirmation occurs in the user’s calendar app."

      What this check looks for
    Description, as the server wrote it
    Saves one revision to one existing calendar feed owned by the connected account for a user-approved schedule change. Accepts one fixed-schema change set with up to 250 event changes and/or a feed title or description change; all stored calendar changes commit together in one transaction, or none are saved. The schema declares every supported change: add creates an event; update changes selected fields or uses reset_fields to restore saved field baselines; delete marks an existing event canceled without permanently erasing it; restore reinstates that same event and may update selected fields; feed_patch changes only the calendar title or description. No dynamic operation discovery, fetched schemas, arbitrary commands or arbitrary endpoints are supported. dry_run=true validates and previews the proposed change set without saving calendar changes, advancing the revision or spending credits. The response contains the exact before/after changes and any billing quote. User approval of that exact preview is a prerequisite for saving with dry_run=false. Saving requires the returned preview_receipt and the identical feed_id, expected_revision, request_id, operations and feed_patch. The receipt binds that validated preview, not user consent. Changed proposals or expired previews require a new preview and approval; revision conflicts require current feed data and a new preview. Omitted events and fields remain unchanged. Cancellation assessment from a revised schedule requires the complete unfiltered event set; unrelated events and manual fields remain unchanged unless explicitly included in the approved changes. Uncertain event matches require user clarification. Updates address matched event IDs; a duplicate add is not an update. A recurring-series target is series_id with scope=occurrence, following or series; occurrence/following uses the original scheduled occurrence_date, including moved occurrences. reset_fields can include cancellation to restore source cancellation policy. Entire-series edits include history and all returned segments are part of the preview. Explicit null in set clears nullable fields; reset_fields restores saved baselines. expected_revision prevents overwriting concurrent changes. An uncertain save is retried with the identical request_id and payload, including the original preview_receipt, rather than a new operation. Included editing access has no credit charge or credit-consent prompt. A quoted one-credit editing window requires explicit user authorization of the deduction and resulting balance before confirm_credit_charge=true; that authorization may be added after preview. Preview approval or an automation default does not authorize credit spending. publication.status reports calendar-file preparation, not subscription access. distribution_ready reports subscription availability at the returned revision; availability may change afterward. Preview proposals are recoverable for up to one hour; expired drafts are removed automatically. Previewing temporarily stores only the exact proposed calendar fields, without writing calendar events or advancing their revision. Returned feed_id and request_id identify that exact proposal for recovery. Recovery accepts only feed_id, the original request_id, dry_run=true and recover_preview=true. Reconstructed changes, guessed identifiers and latest-preview selection are unsupported. Recovery returns the original unexpired preview and exact save_arguments without extending expiry, saving or spending credits. Saving a recovered preview requires fresh user approval of its exact changes and the returned save_arguments unchanged; confirm_credit_charge remains false without explicit authorization of the current quoted charge. Recovery is not consent. Recovery with saved=true reports an already completed save and requires no additional save. An unavailable or expired proposal requires current feed data, a new request_id, a new preview and user approval; a changed proposal is a new approval decision. Scope is limited to the connected account’s Smart Calendars AI feeds. No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh is provided. Structured schedule content is supplied explicitly by the caller. Result links: subscription_open_url is the exact HTTPS handoff to the default calendar app via webcal; subscription_options_url provides Apple/default, Google, Outlook and copy-link choices; subscription_url is the copyable HTTPS calendar-file fallback; manage_url opens the feed dashboard. URL hosts, paths and tokens identify the returned resource and are not interchangeable. A filtered_subscription has its own links for that selection; top-level links remain unfiltered. Subscription access requires distribution_ready=true. Opening a link does not confirm a subscription; confirmation occurs in the user’s calendar app.

    Annotations the server declares

    • title: Save a calendar revision
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • deactivate_feedDeactivates a feed for an explicit user request to interrupt its subscription access, without deleting events or resetting editing windows.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Deactivates a feed for an explicit user request to interrupt its subscription access, without deleting events or resetting editing windows. User approval of that access interruption is required. A counted active feed releases its allowance slot. publication.status reports calendar-file preparation, not subscription access. distribution_ready reports subscription availability at the returned revision; availability may change afterward. Scope is limited to the connected account’s Smart Calendars AI feeds. No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh is provided. Structured schedule content is supplied explicitly by the caller. Result links: subscription_open_url is the exact HTTPS handoff to the default calendar app via webcal; subscription_options_url provides Apple/default, Google, Outlook and copy-link choices; subscription_url is the copyable HTTPS calendar-file fallback; manage_url opens the feed dashboard. URL hosts, paths and tokens identify the returned resource and are not interchangeable. A filtered_subscription has its own links for that selection; top-level links remain unfiltered. Subscription access requires distribution_ready=true. Opening a link does not confirm a subscription; confirmation occurs in the user’s calendar app.

    Annotations the server declares

    • title: Deactivate a calendar
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 2Claude Code: ask
  • create_feedCreates a subscription calendar from user-reviewed structured events and optionally activates it.Reads text others write1 finding

    Why it is in this group

    • The name "create_feed" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.events.items.properties.event.properties.description.description mentions "credentials".

      Matched text

      inputSchema.properties.events.items.properties.event.properties.description.description: "...blish with this calendar. Chat history, credentials, health records and unrelated personal..."

      What this check looks for
    Description, as the server wrote it
    Creates a subscription calendar from user-reviewed structured events and optionally activates it. Intended for an explicit request to save a schedule. The caller supplies the events; source-document extraction and automatic monitoring are not performed. Existing account feed and creation allowances apply. Identical retries retain the original request_id and payload. publication.status reports calendar-file preparation, not subscription access. distribution_ready reports subscription availability at the returned revision; availability may change afterward. Scope is limited to the connected account’s Smart Calendars AI feeds. No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh is provided. Structured schedule content is supplied explicitly by the caller. Result links: subscription_open_url is the exact HTTPS handoff to the default calendar app via webcal; subscription_options_url provides Apple/default, Google, Outlook and copy-link choices; subscription_url is the copyable HTTPS calendar-file fallback; manage_url opens the feed dashboard. URL hosts, paths and tokens identify the returned resource and are not interchangeable. A filtered_subscription has its own links for that selection; top-level links remain unfiltered. Subscription access requires distribution_ready=true. Opening a link does not confirm a subscription; confirmation occurs in the user’s calendar app.

    Annotations the server declares

    • title: Create a subscription calendar
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • reactivate_feedReactivates an existing feed for an explicit user request to restore its subscription access, subject to existing account allowances.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Reactivates an existing feed for an explicit user request to restore its subscription access, subject to existing account allowances. Does not reset the original editing window or modify events. publication.status reports calendar-file preparation, not subscription access. distribution_ready reports subscription availability at the returned revision; availability may change afterward. Scope is limited to the connected account’s Smart Calendars AI feeds. No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh is provided. Structured schedule content is supplied explicitly by the caller. Result links: subscription_open_url is the exact HTTPS handoff to the default calendar app via webcal; subscription_options_url provides Apple/default, Google, Outlook and copy-link choices; subscription_url is the copyable HTTPS calendar-file fallback; manage_url opens the feed dashboard. URL hosts, paths and tokens identify the returned resource and are not interchangeable. A filtered_subscription has its own links for that selection; top-level links remain unfiltered. Subscription access requires distribution_ready=true. Opening a link does not confirm a subscription; confirmation occurs in the user’s calendar app.

    Annotations the server declares

    • title: Reactivate a calendar
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • get_feedReads events and the current revision of a selected feed for a requested schedule lookup or revision.No findings

    Why it is in this group

    • The name "get_feed" says "get": a word for reading.
    Description, as the server wrote it
    Reads events and the current revision of a selected feed for a requested schedule lookup or revision. include_facets=true provides known facet values for label selection. Facets describe the entire published active feed, independent of read filters or pagination. Nonempty filters also return filtered_subscription with canonical filters, matching_event_count and unmatched_filter_values. Its nested URLs address that selection; top-level subscription URLs remain unfiltered. Event IDs, external keys, dates, removal state and pagination narrow only the read, never the subscription. Filtering changes no events and creates no cloned feed. A complete unfiltered read is a prerequisite for assessing cancellations from a revised schedule; omission from a filtered or paginated result is not evidence of deletion. Scope is limited to the connected account’s Smart Calendars AI feeds. No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh is provided. Structured schedule content is supplied explicitly by the caller. Result links: subscription_open_url is the exact HTTPS handoff to the default calendar app via webcal; subscription_options_url provides Apple/default, Google, Outlook and copy-link choices; subscription_url is the copyable HTTPS calendar-file fallback; manage_url opens the feed dashboard. URL hosts, paths and tokens identify the returned resource and are not interchangeable. A filtered_subscription has its own links for that selection; top-level links remain unfiltered. Subscription access requires distribution_ready=true. Opening a link does not confirm a subscription; confirmation occurs in the user’s calendar app. Filter privacy: filters select events, not who can access them; anyone with the link can remove the filters and read the full published calendar.

    Annotations the server declares

    • title: Read calendar events
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_feed_statusReads a selected feed’s last update, current subscription availability (distribution_ready), editing access and configured monitoring status for a requested status check.No findings

    Why it is in this group

    • The name "get_feed_status" says "get": a word for reading.
    Description, as the server wrote it
    Reads a selected feed’s last update, current subscription availability (distribution_ready), editing access and configured monitoring status for a requested status check. This does not refresh, save or charge. Scope is limited to the connected account’s Smart Calendars AI feeds. No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh is provided. Structured schedule content is supplied explicitly by the caller. Result links: subscription_open_url is the exact HTTPS handoff to the default calendar app via webcal; subscription_options_url provides Apple/default, Google, Outlook and copy-link choices; subscription_url is the copyable HTTPS calendar-file fallback; manage_url opens the feed dashboard. URL hosts, paths and tokens identify the returned resource and are not interchangeable. A filtered_subscription has its own links for that selection; top-level links remain unfiltered. Subscription access requires distribution_ready=true. Opening a link does not confirm a subscription; confirmation occurs in the user’s calendar app.

    Annotations the server declares

    • title: Check calendar status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_feedsLists the connected account’s feeds, management links and shared active-feed allowance for a requested calendar lookup.Reads private dataNo findings

    Why it is in this group

    • The name "list_feeds" 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
    Lists the connected account’s feeds, management links and shared active-feed allowance for a requested calendar lookup. Only feeds marked counts_towards_active_limit use a slot; this page’s length is not the account’s usage. Reading changes no feeds or subscription access. Scope is limited to the connected account’s Smart Calendars AI feeds. No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh is provided. Structured schedule content is supplied explicitly by the caller. Result links: subscription_open_url is the exact HTTPS handoff to the default calendar app via webcal; subscription_options_url provides Apple/default, Google, Outlook and copy-link choices; subscription_url is the copyable HTTPS calendar-file fallback; manage_url opens the feed dashboard. URL hosts, paths and tokens identify the returned resource and are not interchangeable. A filtered_subscription has its own links for that selection; top-level links remain unfiltered. Subscription access requires distribution_ready=true. Opening a link does not confirm a subscription; confirmation occurs in the user’s calendar app.

    Annotations the server declares

    • title: List calendars
    • 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
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.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:23 UTC, unchanged since Oct 23, 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
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.smartcalendars.ai/.well-known/oauth-protected-resource/mcp
Authorization servers
https://auth.smartcalendars.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (2 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.smartcalendars.ai/mcp: tools/list returned 7 tools to an anonymous client, including apply_feed_changes (destructive), deactivate_feed (destructive), create_feed (write), reactivate_feed (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

5 info
  • The input schema at properties.events.items.properties.event.properties.description.description mentions "credentials".

    Matched text

    inputSchema.properties.events.items.properties.event.properties.description.description: "...blish with this calendar. Chat history, credentials, health records and unrelated personal..."

    What this check looks for
  • The input schema at properties.operations.items.oneOf[0].properties.event.properties.description.description mentions "credentials".

    Matched text

    inputSchema.properties.operations.items.oneOf[0].properties.event.properties.description.description: "...blish with this calendar. Chat history, credentials, health records and unrelated personal..."

    What this check looks for
  • The input schema at properties.operations.items.oneOf[1].properties.set.properties.description.description mentions "credentials".

    Matched text

    inputSchema.properties.operations.items.oneOf[1].properties.set.properties.description.description: "...blish with this calendar. Chat history, credentials, health records and unrelated personal..."

    What this check looks for
  • The input schema at properties.operations.items.oneOf[3].properties.set.properties.description.description mentions "credentials".

    Matched text

    inputSchema.properties.operations.items.oneOf[3].properties.set.properties.description.description: "...blish with this calendar. Chat history, credentials, health records and unrelated personal..."

    What this check looks for
  • The description is 4,911 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...does not confirm a subscription; confirmation occurs in the user’s calendar app."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools7 changed.~7 changedView diff
    • Changed:apply_feed_changesDeletes or cancelsdescriptioninputSchemaannotations
    • Changed:create_feedChanges thingstitledescriptioninputSchemaannotations
    • Changed:deactivate_feedDeletes or cancelstitledescriptioninputSchemaannotations
    • Changed:get_feedOnly readstitledescriptioninputSchemaannotations
    • Changed:get_feed_statusOnly readstitledescriptioninputSchemaannotations
    • Changed:list_feedsOnly readstitledescriptioninputSchemaannotations
    • Changed:reactivate_feedChanges thingstitledescriptioninputSchemaannotations

Install

Pinned to version 2.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http smart-calendars-ai https://api.smartcalendars.ai/mcp
claude mcp add --transport http smart-calendars-ai https://api.smartcalendars.ai/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__smart-calendars-ai__list_feeds",
      "mcp__smart-calendars-ai__get_feed",
      "mcp__smart-calendars-ai__get_feed_status"
    ],
    "ask": [
      "mcp__smart-calendars-ai__create_feed",
      "mcp__smart-calendars-ai__reactivate_feed"
    ],
    "deny": [
      "mcp__smart-calendars-ai__apply_feed_changes",
      "mcp__smart-calendars-ai__deactivate_feed"
    ]
  }
}

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 smart-calendars-ai. Review it before you use it.

Capability tags behind 5 rules
  • mcp__smart-calendars-ai__create_feed untrusted-input
  • mcp__smart-calendars-ai__list_feeds private-data
  • mcp__smart-calendars-ai__apply_feed_changes untrusted-input
  • mcp__smart-calendars-ai__deactivate_feed untrusted-input
  • mcp__smart-calendars-ai__reactivate_feed untrusted-input

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/ai.smartcalendars/smart-calendars-ai/verify?hash=d07471f86fea6e549855264937f2f982ab3f907596fc1bd044d87c67c8078267" | jq -e '.changed == false'

Pinned hash d07471f86fea, from Nov 8, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.smartcalendars/smart-calendars-ai/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.smartcalendars/smart-calendars-ai
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.smartcalendars/smart-calendars-ai.svg)](https://radar.anlyon.com/servers/ai.smartcalendars/smart-calendars-ai)

Source: MCP Registry. Synced Oct 23, 2026, 13:17 UTC.

Smart Calendars AI MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Smart Calendars AI MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 5 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 Smart Calendars AI MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: apply_feed_changes and deactivate_feed.

Can the Smart Calendars AI MCP server 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 Smart Calendars AI MCP server have?

7 tools: 2 destructive, 2 write, 3 read. apply_feed_changes, deactivate_feed, create_feed, reactivate_feed, list_feeds, get_feed and get_feed_status.

Does the Smart Calendars AI MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Smart Calendars AI MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Smart Calendars AI MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.