Skip to content

Tempi MCP server

com.meettempi/tempimeettempi.comstreamable-httpv1.0.0Scanned

Find open times and book, reschedule or cancel meetings on anyone's Tempi link. No account needed.

11 tools: 1 can delete or cancel things, 6 change things and 4 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • 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 Tempi MCP server can do

The Tempi MCP server is published by meettempi.com, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (1 tool: cancel_booking_as_invitee) and create or change data (6 tools: check_series, create_booking, reschedule_booking_as_invitee, share_booking_as_invitee and 2 more). 4 tools only read.

1 tool reads private data (get_available_slots); 2 tools bring in text other people can write (get_public_profile and get_booking); 1 tool can send data out of your system (create_booking). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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

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

Last scanned Nov 13, 2026, version 1.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.

11 tools

Deletes or cancels 1Claude Code: deny
  • cancel_booking_as_inviteeCancels a booking by its id and token.No findings

    Why it is in this group

    • The name "cancel_booking_as_invitee" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Cancels a booking by its id and token. The event is removed from the host's calendar. Paid bookings cancelled before `refundableUntil` are refunded in full. Later cancellations get no refund. The event type sets the rules, which get_booking shows: no changes after `changeableUntil` (409 change_too_late), no cancelling when `canCancel` is false (409 cancel_not_allowed, reschedule instead).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
Changes things 6Claude Code: ask
  • check_seriesFor event types with `repeatMax` (from get_public_profile): lists each meeting of a series that starts at `start` (one of the slots) and repeats `every` 1, 2 or 4 weeks at the host…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    For event types with `repeatMax` (from get_public_profile): lists each meeting of a series that starts at `start` (one of the slots) and repeats `every` 1, 2 or 4 weeks at the host's clock time, and whether each is free. Pass the invitee's `timezone` to get each meeting's `when` in it: where clocks change on other dates than the host's, some meetings move for the invitee, and `message` says which. Book it with create_booking and `repeat` when `bookable` is true. A series is booked whole or not at all, and round robin gives every meeting to the same host.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • create_bookingBooks `start`, which must be one of the `slots` from get_available_slots.Can send data outNo findings

    Why it is in this group

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

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Books `start`, which must be one of the `slots` from get_available_slots. Free events are confirmed at once, unless the event type has `requiresApproval`: then it's a request (status=pending_approval) that holds the time until a host approves or declines it, and the invitee hears either way by email. Nobody answering by its start (`holdExpiresAt`) lets it lapse. Tell the human it isn't confirmed yet. Paid events return status=pending_payment and a `paymentUrl`. Give it to the human to pay before `holdExpiresAt`, or the slot is released. Once confirmed, the event is added to the host's calendar if they connected one, and the invitee gets a confirmation email with a calendar file (.ics). Keep `manageUrl` and `token`: they are the only way to view, reschedule or cancel later. 409 slot_unavailable says why the time can't be booked and lists the `nearest` open times. The result's `when` is the start in the invitee's time zone, to tell them.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • join_waitlistRequests access to host on Tempi (create event types, share a booking page).No findings

    Why it is in this group

    • The description's first verb is "request": a word for a change.
    Description, as the server wrote it
    Requests access to host on Tempi (create event types, share a booking page). Not needed to book meetings, since booking pages are public. Returns the status: pending, approved (sign in to the Tempi web app), rejected, or open (no waitlist, sign in directly). Joining again with the same email returns the current status.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • reschedule_booking_as_inviteeMoves a confirmed booking to `start` with the same hosts.No findings

    Why it is in this group

    • The name "reschedule_booking_as_invitee" says "reschedule": a word for a change.
    Description, as the server wrote it
    Moves a confirmed booking to `start` with the same hosts. Get valid times from get_available_slots with this `bookingId` and `token`. The calendar event is updated and its provider notifies attendees. Payment carries over. Not possible after `changeableUntil` (409 change_too_late). A request (status=pending_approval) can’t be moved: cancel it and request another time.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • share_booking_as_inviteeTurns a confirmed booking into an invitation page anyone with its `url` can open: what, when (in the reader’s time zone) and with whom.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
    Turns a confirmed booking into an invitation page anyone with its `url` can open: what, when (in the reader’s time zone) and with whom. It never shows the invitee’s email, phone or notes, and shows the meeting link only with `includeLink`. Calling it again changes the style or the link and keeps the same `url`. stop_sharing_booking_as_invitee ends it.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • stop_sharing_booking_as_inviteeEnds a booking’s invitation: its link stops working.No findings

    Why it is in this group

    • The name "stop_sharing_booking_as_invitee" says "stop": a word for a change.
    Description, as the server wrote it
    Ends a booking’s invitation: its link stops working. Sharing again gives a new link.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • get_available_slotsReturns the start times that can be booked, with the hosts' calendars, buffers and limits already applied.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "return" and "calendar": it reads calendars.
    Description, as the server wrote it
    Returns the start times that can be booked, with the hosts' calendars, buffers and limits already applied. Pass the invitee's `timezone` and either `date` (YYYY-MM-DD in `timezone`) or `from` and `to` (ISO, at most 62 days apart). With neither, it covers the next 7 days. `days` groups the slots by date in `timezone`, and `times` gives each slot as a local time to show people. People can book up to `bookableUntil`. When the range has no open times, `next` is the next one. When `timezone` was an abbreviation that names more than one zone (CST, IST, BST), `timezoneNote` says which one was used: check it with the person. For new times for an existing booking, also pass its `bookingId` and `token`. Next: call create_booking (or reschedule_booking_as_invitee) with one of the `slots` values as `start`.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_bookingReturns a booking by its id and token (from create_booking), or its manageUrl passed as both, with `changeableUntil`, `refundableUntil` and `canCancel`.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Returns a booking by its id and token (from create_booking), or its manageUrl passed as both, with `changeableUntil`, `refundableUntil` and `canCancel`. For a series, `series` lists every meeting with its own manageUrl.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_public_profileTakes a handle, the first path segment of a booking link (https://host/acme/demo → "acme"), or the link itself.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Takes a handle, the first path segment of a booking link (https://host/acme/demo → "acme"), or the link itself. Returns the person or team and their bookable event types, with duration, price, and hosts with their time zones (`hostTimezones`, so you can say what time a slot is for them). A handle from before a rename also works. Next: call get_available_slots with one of the event type slugs.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_shared_bookingReturns the invitation behind a shared booking’s link ("…/i/<token>"): what, when, with whom, its status (upcoming, cancelled or past), its style, and where to book the same host.No findings

    Why it is in this group

    • The name "get_shared_booking" says "get": a word for reading.
    Description, as the server wrote it
    Returns the invitation behind a shared booking’s link ("…/i/<token>"): what, when, with whom, its status (upcoming, cancelled or past), its style, and where to book the same host. 404 once its sharer stopped sharing it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • 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.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
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 out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__tempi__create_booking"
    ]
  }
}

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 20, 2026, 18:42 UTC, unchanged since Nov 20, 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
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

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

    Matched text

    https://meettempi.com/mcp: tools/list returned 12 tools to an anonymous client, including cancel_booking_as_invitee (destructive), check_series (write), create_booking (write), answer_booking (write), reschedule_booking_as_invitee (write) and 3 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 7 to 8
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 5 to 7

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. Tools that change things, listed without credentials: 7 -> 8.View diff
    • Tools that change things, listed without credentials: 7 to 8
  2. Tools3 added.+3 addedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 7.View diff
    • Tools that change things, listed without credentials: 5 to 7

Install

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

claude mcp add --transport http tempi https://meettempi.com/mcp
claude mcp add --transport http tempi https://meettempi.com/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__tempi__get_public_profile",
      "mcp__tempi__get_available_slots",
      "mcp__tempi__get_booking",
      "mcp__tempi__get_shared_booking"
    ],
    "ask": [
      "mcp__tempi__check_series",
      "mcp__tempi__create_booking",
      "mcp__tempi__reschedule_booking_as_invitee",
      "mcp__tempi__share_booking_as_invitee",
      "mcp__tempi__stop_sharing_booking_as_invitee",
      "mcp__tempi__join_waitlist"
    ],
    "deny": [
      "mcp__tempi__cancel_booking_as_invitee"
    ]
  }
}

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

Capability tags behind 4 rules
  • mcp__tempi__get_public_profile untrusted-input
  • mcp__tempi__get_available_slots private-data
  • mcp__tempi__create_booking outbound
  • mcp__tempi__get_booking 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/com.meettempi/tempi/verify?hash=a751211923720008d91cdd104321dcf8a1207283c86c991c831796e5cbb43a07" | jq -e '.changed == false'

Pinned hash a75121192372, from Nov 13, 2026, 18:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.meettempi/tempi/changes.xml

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

Badge

Anlyon Radar badge for com.meettempi/tempi
[![Anlyon Radar](https://radar.anlyon.com/badge/com.meettempi/tempi.svg)](https://radar.anlyon.com/servers/com.meettempi/tempi)

Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.

Tempi MCP server: questions and answers

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

Is the Tempi MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 7 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 Tempi MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_booking_as_invitee.

Can the Tempi 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 Tempi MCP server have?

11 tools: 1 destructive, 6 write, 4 read. cancel_booking_as_invitee, check_series, create_booking, reschedule_booking_as_invitee, share_booking_as_invitee, stop_sharing_booking_as_invitee, join_waitlist, get_public_profile and 3 more.

Does the Tempi MCP server need sign-in or OAuth?

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

Does the Tempi MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_booking.

Has the Tempi MCP server changed its tools?

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