Tempi
REMOTE · MEETTEMPI.COM
Find open times and book, reschedule or cancel meetings on anyone's Tempi link. No account needed.
Available components
Last scanned (18 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_booking_as_invitee). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2901 tokens (~223/item across 13 items; 12 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Nov 26 0
- Tool “answer_booking” rewrote its description, which is the text the model reads security
- “create_booking” reworded the description of “answers” cosmetic
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_booking” rewrote its description, which is the text the model reads security
- Schema quality: 2549 → 2880 ▼ functional
- Schema quality: excellent → good functional
- New tool “answer_booking” functional
- “create_booking” added an optional parameter “answers” cosmetic
- 11 Nov 26 0
- Stability: 0.97 → pass security
- Schema quality: good → excellent functional
- “share_booking_as_invitee” reworded the description of “style” cosmetic
- 10 Nov 26 0
- Schema quality: excellent → good functional
- Stability: pass → 0.97 functional
- “share_booking_as_invitee” reworded the description of “style” cosmetic
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 7 Nov 26 0
- Schema quality: 243 → 210 ▲ functional
- New tool “get_shared_booking” functional
- New tool “share_booking_as_invitee” functional
- New tool “stop_sharing_booking_as_invitee” functional
- 6 Nov 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://meettempi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=meettempi.com | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1cfc72b09b88c69e0e7f9cd5543aeb25 |
| SANs: meettempi.com, staging.meettempi.com, *.staging.meettempi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of meettempi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| meettempi.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://meettempi.com/mcp | Verified | 200 | |
| http (plaintext) | http://meettempi.com/mcp | HTTPS enforced | 301 | https://meettempi.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
answer_booking Answer a booking's questions (invitee) ~133
Saves the invitee's answers to questions the host asks (`questions` on the booking, those not yet in `answers`). Questions are answered when booking, in create_booking's `answers`. This is for an answer the invitee wants to add or change afterwards: don't ask them again after booking. A new answer to a question replaces the old one. Returns the booking.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | array | yes | the answers, as [{ id, value }] |
| id | string | yes | the booking id from create_booking, or its manageUrl |
| token | string | yes | the token from create_booking, or the manageUrl |
No output schema declared.
No examples provided.
cancel_booking_as_invitee Cancel a booking (invitee) ~167
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).
| Name | Type | Req | Description |
|---|---|---|---|
| following | boolean | – | for a series: also cancel every later meeting |
| id | string | yes | the booking id from create_booking, or its manageUrl |
| reason | string | – | why the invitee cancels, sent to the host |
| token | string | yes | the token from create_booking, or the manageUrl |
No output schema declared.
No examples provided.
check_series Check a repeating series before booking it ~316
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | – | yes | how many meetings, first included (2 up to the event type's repeatMax) |
| every | – | yes | weeks between meetings: 1, 2 or 4 |
| handle | string | yes | a handle, the first part of a booking link ("acme" in meettempi.com/acme/demo), or the whole link |
| slug | string | yes | an event type slug from get_public_profile ("demo" in meettempi.com/acme/demo), or the whole link |
| start | string | yes | one of the `slots` values from get_available_slots, as given (ISO in UTC) |
| timezone | string | – | the invitee's time zone, an IANA id like America/New_York or an abbreviation like EST: each meeting's `when` is in it |
No output schema declared.
No examples provided.
create_booking Book a meeting ~784
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. For a video call, `meetingUrlStatus` says where the link stands: `ready` (in `meetingUrl`), `pending` (the host's calendar is making it: call get_booking with the `manageUrl` in a few seconds, and tell the person the link is on its way and in their email), `on_confirmation`, `host_sends` or `none`. `videoService` names the service (Google Meet, Microsoft Teams) even before the link is there.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | array | – | answers to the event type's `questions` (get_public_profile), as [{ id, value }]. Every question with `required` true needs one, or the booking is refused (422 answers_required, which lists them): as… |
| cover | string | – | leave it out: the id of the painting the booking page showed, when the event type shows a different one each booking (cover "hand", "light" or "still"), so the booking keeps it. Anything else is igno… |
| string | yes | the invitee's email address, which gets the confirmation and its calendar file | |
| handle | string | yes | a handle, the first part of a booking link ("acme" in meettempi.com/acme/demo), or the whole link |
| name | string | yes | the invitee's full name |
| notes | string | – | anything the invitee wants the host to know |
| phone | string | – | the invitee's phone number with its country code, like +1 415 555 0134: required when the event type is a phone call (whereKind phone on get_public_profile), where the host calls them |
| repeat | object | – | book a series instead: `count` meetings, `every` 1, 2 or 4 weeks at the host's clock time, when the event type's repeatMax allows. All or nothing: check_series first. The result's `series.meetings` g… |
| slug | string | yes | an event type slug from get_public_profile ("demo" in meettempi.com/acme/demo), or the whole link |
| start | string | yes | one of the `slots` values from get_available_slots, as given (ISO in UTC) |
| timezone | string | yes | the invitee's time zone, an IANA id like America/New_York or an abbreviation like EST: their emails and reminders show times in it |
No output schema declared.
No examples provided.
get_available_slots Find open times ~405
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| bookingId | string | – | the booking id from create_booking, or its manageUrl |
| date | string | – | one day to look at, as YYYY-MM-DD in `timezone` |
| from | string | – | start of the range, ISO with an offset |
| handle | string | yes | a handle, the first part of a booking link ("acme" in meettempi.com/acme/demo), or the whole link |
| slug | string | yes | an event type slug from get_public_profile ("demo" in meettempi.com/acme/demo), or the whole link |
| timezone | string | yes | the invitee's time zone, an IANA id like America/New_York or an abbreviation like EST: days, dates and times are in it |
| to | string | – | end of the range, ISO with an offset |
| token | string | – | the token from create_booking, or the manageUrl |
No output schema declared.
No examples provided.
get_booking View a booking (invitee) ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the booking id from create_booking, or its manageUrl |
| token | string | yes | the token from create_booking, or the manageUrl |
No output schema declared.
No examples provided.
get_public_profile List a person's or team's event types ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | a handle, the first part of a booking link ("acme" in meettempi.com/acme/demo), or the whole link |
No output schema declared.
No examples provided.
get_shared_booking View a shared invitation ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | the invitation’s address (".../i/<token>") or its token |
No output schema declared.
No examples provided.
join_waitlist Join the private beta waitlist ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | an email address | |
| name | string | – | the person’s name (at most 100 characters) |
| note | string | – | anything the admins should know, e.g. what you want to use Tempi for |
| ref | string | – | a short source tag of lowercase letters, digits, - or _, like "embed" |
No output schema declared.
No examples provided.
reschedule_booking_as_invitee Reschedule a booking (invitee) ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the booking id from create_booking, or its manageUrl |
| start | string | yes | one of the `slots` values from get_available_slots, as given (ISO in UTC) |
| token | string | yes | the token from create_booking, or the manageUrl |
No output schema declared.
No examples provided.
share_booking_as_invitee Share a booking as an invitation (invitee) ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the booking id from create_booking, or its manageUrl |
| includeLink | boolean | – | true: the invitation shows the meeting link, so anyone with it can join the call. Off by default. |
| style | string | – | how the invitation looks: light (the default), poster (dark, the name large, in the event type's color) or glow (its painting as light). Older names still work and give the nearest of the three |
| token | string | yes | the token from create_booking, or the manageUrl |
No output schema declared.
No examples provided.
stop_sharing_booking_as_invitee Stop sharing a booking (invitee) ~66
Ends a booking’s invitation: its link stops working. Sharing again gives a new link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the booking id from create_booking, or its manageUrl |
| token | string | yes | the token from create_booking, or the manageUrl |
No output schema declared.
No examples provided.
How do I install the Tempi MCP server?
Tempi is a hosted endpoint at https://meettempi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · meettempi.com
claude mcp add --transport http com-meettempi-tempi 'https://meettempi.com/mcp'
What is the Tempi MCP server?
Tempi is an MCP server listed in the public MCP registry as com.meettempi/tempi. Find open times and book, reschedule or cancel meetings on anyone's Tempi link. No account needed. This page covers its hosted endpoint (https://meettempi.com/mcp).
Is the Tempi MCP server safe to use?
Tempi scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tempi MCP server expose?
Tempi exposes 12 tools: get_public_profile, get_available_slots, check_series, create_booking, get_booking, and 7 more. Their descriptions and schemas cost roughly 2,705 tokens of context every time the server is loaded.
Does the Tempi MCP server require authentication?
No. We connected to Tempi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tempi MCP server still maintained?
Tempi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Tempi MCP server?
VerifyMCP ran 14 checks on Tempi, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.