Skip to content

Teamup Calendar MCP by usefulapi

io.usefulapi/teamup-calendarusefulapi.iostreamable-httpv1.27.7Scanned

Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events.

15 tools: 4 can delete or cancel things, 2 change things and 9 only read.

Tools: 4 delete, 0 irreversible, 2 write, 9 read.
  • Reads private data · 7
  • Reads text others write · 15
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

6 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 Teamup Calendar MCP by usefulapi can do

The Teamup Calendar MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (4 tools: teamup_update_event, teamup_delete_event, teamup_undo_event_action and teamup_update_subcalendar) and create or change data (2 tools: teamup_create_event and teamup_create_subcalendar). 9 tools only read.

7 tools read private data (teamup_get_calendar, teamup_list_subcalendars, teamup_get_subcalendar and 4 more); 15 tools bring in text other people can write (teamup_get_calendar, teamup_list_subcalendars, teamup_get_subcalendar and 12 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.27.7.

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.

15 tools

Deletes or cancels 4Claude Code: deny
  • teamup_delete_eventWRITE, DESTRUCTIVE: delete an event, or for a recurring event the chosen occurrences.Reads text others writeNo findings

    Why it is in this group

    • The name "teamup_delete_event" says "delete": a word for removing or ending something.
    • 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
    WRITE, DESTRUCTIVE: delete an event, or for a recurring event the chosen occurrences. Needs modify permission. Not retried. The reply holds an undo_id; teamup_undo_event_action restores the event within one hour, after that the deletion is permanent. For one occurrence use the occurrence id (123-rid-<unix start>) and redit single (the default); redit all deletes the whole series. DELETE /{calendarKey}/events/{id}.

    Annotations the server declares

    • title: Delete event
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • teamup_undo_event_actionWRITE: undo a recent event creation, update or deletion with the undo_id from that call.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "write": 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.
    Description, as the server wrote it
    WRITE: undo a recent event creation, update or deletion with the undo_id from that call. Works for one hour only and is refused if someone else changed the event since. PUT /{calendarKey}/events/undo/{undo_id}.

    Annotations the server declares

    • title: Undo event change
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • teamup_update_eventWRITE: change fields of an event; fields you leave out keep their value (the event is read first and sent back with its version, so a concurrent edit is refused instead of overwrit…Reads text others writeNo findings

    Why it is in this group

    • The name "teamup_update_event" says "update": 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.
    Description, as the server wrote it
    WRITE: change fields of an event; fields you leave out keep their value (the event is read first and sent back with its version, so a concurrent edit is refused instead of overwritten; an event without a version is not changed). Needs modify permission. For a recurring event pass redit; use the occurrence id (123-rid-<unix start>) with single or future. Attachments are not touched. The reply holds the event and an undo_id for one hour (teamup_undo_event_action). PUT /{calendarKey}/events/{id}.

    Annotations the server declares

    • title: Update event
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • teamup_update_subcalendarWRITE: change a sub-calendar's name, color, overlap rule or active state; fields you leave out keep their value.Reads text others writeNo findings

    Why it is in this group

    • The name "teamup_update_subcalendar" says "update": 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.
    Description, as the server wrote it
    WRITE: change a sub-calendar's name, color, overlap rule or active state; fields you leave out keep their value. Needs admin permission. Making a sub-calendar inactive hides it from users without admin rights. PATCH /{calendarKey}/subcalendars/{id}.

    Annotations the server declares

    • title: Update sub-calendar
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 2Claude Code: ask
  • teamup_create_eventWRITE: create an event.Reads text others writeNo findings

    Why it is in this group

    • The name "teamup_create_event" 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.
    Description, as the server wrote it
    WRITE: create an event. Needs a calendar key with add or modify permission. Give at least subcalendar_ids, start and end. Not idempotent: a repeated call creates a second event. The reply holds the new event and an undo_id; teamup_undo_event_action removes the event again within one hour. POST /{calendarKey}/events.

    Annotations the server declares

    • title: Create event
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • teamup_create_subcalendarWRITE: create a sub-calendar.Reads text others writeNo findings

    Why it is in this group

    • The name "teamup_create_subcalendar" 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.
    Description, as the server wrote it
    WRITE: create a sub-calendar. Needs a calendar key with admin permission, and the plan may limit how many exist. Not idempotent: a repeated call creates a second one. POST /{calendarKey}/subcalendars.

    Annotations the server declares

    • title: Create sub-calendar
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 9Show 9 read-only tools
  • teamup_get_calendarThe calendar this connection points at: title, timezone and date settings, custom event fields, sub-calendars, the permission of the calendar key in use and the plan's features.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "teamup_get_calendar" says "get": a word for reading.

    What it can reach

    • private-dataThe name "teamup_get_calendar" says "get" and "calendar": it reads calendars.
    • private-dataThe description's first sentence says "calendar": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The calendar this connection points at: title, timezone and date settings, custom event fields, sub-calendars, the permission of the calendar key in use and the plan's features. Call this first to learn the sub-calendar ids and the timezone. The calendar key itself is never returned. GET /{calendarKey}/configuration.

    Annotations the server declares

    • title: Get calendar
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • teamup_get_eventOne event by id: title, times, sub-calendars, location, who, notes (markdown), recurrence rule, custom fields, signups, comments, attachments (metadata), version, change history an…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "teamup_get_event" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "calendar": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    One event by id: title, times, sub-calendars, location, who, notes (markdown), recurrence rule, custom fields, signups, comments, attachments (metadata), version, change history and reminders. Use the occurrence id (123-rid-<unix start>) for one occurrence of a recurring event. GET /{calendarKey}/events/{id}.

    Annotations the server declares

    • title: Get event
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • teamup_get_subcalendarOne sub-calendar by id: name, color, overlap rule, active state and which links may use it.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "teamup_get_subcalendar" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "calendar": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    One sub-calendar by id: name, color, overlap rule, active state and which links may use it. GET /{calendarKey}/subcalendars/{id}.

    Annotations the server declares

    • title: Get sub-calendar
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • teamup_list_access_keysList the calendar's access keys (sharing links and user accesses) with name, role, active state and per-sub-calendar permission.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "teamup_list_access_keys" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "calendar": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the calendar's access keys (sharing links and user accesses) with name, role, active state and per-sub-calendar permission. Needs a key with admin permission. The secret key values are never returned (they are secrets); use the id and name to tell links apart. GET /{calendarKey}/keys.

    Annotations the server declares

    • title: List access keys
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • teamup_list_changed_eventsEvents created, changed or deleted since a Unix timestamp (at most 30 days back), for syncing.Reads text others writeNo findings

    Why it is in this group

    • The name "teamup_list_changed_events" says "list": a word for reading.

    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
    Events created, changed or deleted since a Unix timestamp (at most 30 days back), for syncing. A recurring event comes back once, as its series, not as occurrences. Deleted events carry delete_dt. Pass the reply's timestamp as since_timestamp next time so nothing is missed. GET /{calendarKey}/events?modifiedSince=.

    Annotations the server declares

    • title: List changed events
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • teamup_list_event_signupsThe people signed up for an event (name, email, id).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "teamup_list_event_signups" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    The people signed up for an event (name, email, id). Signups must be enabled on the event. GET /{calendarKey}/events/{id}/signups.

    Annotations the server declares

    • title: List event signups
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • teamup_list_eventsList the events in a date range, optionally only on some sub-calendars.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "teamup_list_events" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "calendar": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the events in a date range, optionally only on some sub-calendars. Recurring events are expanded: every occurrence in the range is returned with its own id (series id + -rid- + start). Notes come as markdown. Times use the calendar's timezone unless tz is set. GET /{calendarKey}/events.

    Annotations the server declares

    • title: List events
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • teamup_list_subcalendarsList the sub-calendars (the colored lanes that events belong to, such as people, rooms or resources).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "teamup_list_subcalendars" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "calendar": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the sub-calendars (the colored lanes that events belong to, such as people, rooms or resources). A key with admin permission also sees inactive ones. GET /{calendarKey}/subcalendars.

    Annotations the server declares

    • title: List sub-calendars
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • teamup_search_eventsSearch events by keyword (2-100 characters) within a date range (default: today only, so always pass the range you mean).Reads text others writeNo findings

    Why it is in this group

    • The name "teamup_search_events" says "search": a word for reading.

    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
    Search events by keyword (2-100 characters) within a date range (default: today only, so always pass the range you mean). Recurring events are expanded. Paged with limit and offset. GET /{calendarKey}/events?query=.

    Annotations the server declares

    • title: Search events
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: 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.

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.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 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

  1. 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: 6 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://teamup-calendar.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://teamup-calendar.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.

  1. 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: 6 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://teamup-calendar.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://teamup-calendar.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

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

claude mcp add --transport http teamup-calendar https://teamup-calendar.usefulapi.io/mcp
claude mcp add --transport http teamup-calendar https://teamup-calendar.usefulapi.io/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__teamup-calendar__teamup_get_calendar",
      "mcp__teamup-calendar__teamup_list_subcalendars",
      "mcp__teamup-calendar__teamup_get_subcalendar",
      "mcp__teamup-calendar__teamup_list_access_keys",
      "mcp__teamup-calendar__teamup_list_events",
      "mcp__teamup-calendar__teamup_search_events",
      "mcp__teamup-calendar__teamup_get_event",
      "mcp__teamup-calendar__teamup_list_changed_events",
      "mcp__teamup-calendar__teamup_list_event_signups"
    ],
    "ask": [
      "mcp__teamup-calendar__teamup_create_event",
      "mcp__teamup-calendar__teamup_create_subcalendar"
    ],
    "deny": [
      "mcp__teamup-calendar__teamup_update_event",
      "mcp__teamup-calendar__teamup_delete_event",
      "mcp__teamup-calendar__teamup_undo_event_action",
      "mcp__teamup-calendar__teamup_update_subcalendar"
    ]
  }
}

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 teamup-calendar. Review it before you use it.

Capability tags behind 15 rules
  • mcp__teamup-calendar__teamup_get_calendar private-data, untrusted-input
  • mcp__teamup-calendar__teamup_list_subcalendars private-data, untrusted-input
  • mcp__teamup-calendar__teamup_get_subcalendar private-data, untrusted-input
  • mcp__teamup-calendar__teamup_list_access_keys private-data, untrusted-input
  • mcp__teamup-calendar__teamup_list_events private-data, untrusted-input
  • mcp__teamup-calendar__teamup_search_events untrusted-input
  • mcp__teamup-calendar__teamup_get_event private-data, untrusted-input
  • mcp__teamup-calendar__teamup_list_changed_events untrusted-input
  • mcp__teamup-calendar__teamup_list_event_signups private-data, untrusted-input
  • mcp__teamup-calendar__teamup_create_event untrusted-input
  • mcp__teamup-calendar__teamup_update_event untrusted-input
  • mcp__teamup-calendar__teamup_delete_event untrusted-input
  • mcp__teamup-calendar__teamup_undo_event_action untrusted-input
  • mcp__teamup-calendar__teamup_create_subcalendar untrusted-input
  • mcp__teamup-calendar__teamup_update_subcalendar 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/io.usefulapi/teamup-calendar/verify?hash=f34893bf1e62554b0ccc99d98b04fe0652678b3f5b263b0312f0c721326b1daf" | jq -e '.changed == false'

Pinned hash f34893bf1e62, 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/teamup-calendar/changes.xml

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

Badge

Anlyon Radar badge for io.usefulapi/teamup-calendar
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/teamup-calendar.svg)](https://radar.anlyon.com/servers/io.usefulapi/teamup-calendar)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

Teamup Calendar MCP by usefulapi: questions and answers

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

Is the Teamup Calendar MCP by usefulapi safe?

No scan can promise that. What its definitions show: 15 tools, 6 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 Teamup Calendar MCP by usefulapi delete data?

Yes. 4 tools can delete, cancel or revoke something: teamup_update_event, teamup_delete_event, teamup_undo_event_action and teamup_update_subcalendar.

Can the Teamup Calendar 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 Teamup Calendar MCP by usefulapi have?

15 tools: 4 destructive, 2 write, 9 read. teamup_update_event, teamup_delete_event, teamup_undo_event_action, teamup_update_subcalendar, teamup_create_event, teamup_create_subcalendar, teamup_get_calendar, teamup_list_subcalendars and 7 more.

Does the Teamup Calendar MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Teamup Calendar 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 Teamup Calendar MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.