Perfect Clock is an MCP server published by cc.perfectclock, hosted at perfectclock.cc. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 2 tools, including plan_meeting_schedule, find_meeting_windows.
Find meeting times across time zones and compare working hours.
775 connections through 4 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Plans a one-off or recurring meeting with people in other time zones when its time is known (e.g. "every other Tuesday at 10:00 Berlin time with Anna in Tbilisi"). Expands it into concrete dates and shows each one in every participant's local time, with working-hours checks, public holidays and daylight-saving shifts. Saves the schedule for 30 days and returns a private perfectclock.cc/s/... link that opens it in Perfect Clock; each call saves a new schedule with its own link.
| Parameter | Type | Description |
|---|---|---|
| tz * | string | Time zone the meeting time is fixed in (usually the organizer's). |
| rule * | object | Recurrence of the meeting. |
| time * | string | Local start time in `tz`. |
| title |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| string |
| Meeting title. |
| participants * | array | People or places the meeting must suit, each with their own time zone. |
| maxOccurrences | integer | How many upcoming meetings to list. |
| durationMinutes | integer |
{
"name": "plan_meeting_schedule",
"title": "Plan a meeting schedule",
"description": "Plans a one-off or recurring meeting with people in other time zones when its time is known (e.g. \"every other Tuesday at 10:00 Berlin time with Anna in Tbilisi\"). Expands it into concrete dates and shows each one in every participant's local time, with working-hours checks, public holidays and daylight-saving shifts. Saves the schedule for 30 days and returns a private perfectclock.cc/s/... link that opens it in Perfect Clock; each call saves a new schedule with its own link.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"title",
"tz",
"time",
"rule",
"participants"
],
"properties": {
"tz": {
"type": "string",
"description": "Time zone the meeting time is fixed in (usually the organizer's)."
},
"rule": {
"type": "object",
"required": [
"freq"
],
"properties": {
"freq": {
"enum": [
"once",
"daily",
"weekly",
"monthly"
],
"type": "string"
},
"byDay": {
"type": "array",
"items": {
"enum": [
"MO",
"TU",
"WE",
"TH",
"FR",
"SA",
"SU"
],
"type": "string"
},
"description": "Weekdays for weekly rules; for monthly with setPos, the weekday."
},
"count": {
"type": "integer",
"maximum": 500,
"minimum": 1
},
"start": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First possible date in `tz`; default today."
},
"until": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"setPos": {
"type": "integer",
"maximum": 4,
"minimum": -1,
"description": "Monthly \"Nth weekday\": 1-4, or -1 for the last."
},
"interval": {
"type": "integer",
"maximum": 12,
"minimum": 1,
"description": "Every N days/weeks/months; default 1."
}
},
"description": "Recurrence of the meeting."
},
"time": {
"type": "string",
"pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
"description": "Local start time in `tz`."
},
"title": {
"type": "string",
"maxLength": 120,
"description": "Meeting title."
},
"participants": {
"type": "array",
"items": {
"type": "object",
"required": [
"label",
"tz"
],
"properties": {
"tz": {
"type": "string",
"description": "IANA time zone of this participant, e.g. Asia/Tbilisi."
},
"label": {
"type": "string",
"maxLength": 60,
"description": "How the participant or place is called in the conversation, e.g. \"Anna\" or \"Tokyo office\"."
},
"workHours": {
"type": "array",
"items": {
"type": "string",
"pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
},
"maxItems": 2,
"minItems": 2,
"description": "Local working hours [start, end]; default [\"09:00\",\"17:00\"]."
}
}
},
"maxItems": 10,
"minItems": 1,
"description": "People or places the meeting must suit, each with their own time zone."
},
"maxOccurrences": {
"type": "integer",
"default": 8,
"maximum": 20,
"minimum": 1,
"description": "How many upcoming meetings to list."
},
"durationMinutes": {
"type": "integer",
"default": 60,
"maximum": 720,
"minimum": 5
}
}
},
"annotations": {
"title": "Plan a meeting schedule",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}Finds when people in other time zones can meet, when the time is not decided yet: the windows on each day when all participants are within their working hours, accounting for weekends, public holidays and daylight-saving changes, and one suggested start time that fits the most days. Saves that suggested time on those days for 30 days and returns a private perfectclock.cc/s/... link that opens it in Perfect Clock; each call saves a new schedule with its own link.
| Parameter | Type | Description |
|---|---|---|
| tz * | string | Time zone whose calendar days are scanned (usually the organizer's). |
| days | integer | |
| from | string | First day in `tz`; default today. |
| title | string | Meeting title, if the user gave one. |
| participants * | array | People or places the meeting must suit, each with their own time zone. |
| durationMinutes | integer |
{
"name": "find_meeting_windows",
"title": "Find meeting windows",
"description": "Finds when people in other time zones can meet, when the time is not decided yet: the windows on each day when all participants are within their working hours, accounting for weekends, public holidays and daylight-saving changes, and one suggested start time that fits the most days. Saves that suggested time on those days for 30 days and returns a private perfectclock.cc/s/... link that opens it in Perfect Clock; each call saves a new schedule with its own link.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"tz",
"participants"
],
"properties": {
"tz": {
"type": "string",
"description": "Time zone whose calendar days are scanned (usually the organizer's)."
},
"days": {
"type": "integer",
"default": 5,
"maximum": 14,
"minimum": 1
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First day in `tz`; default today."
},
"title": {
"type": "string",
"maxLength": 120,
"description": "Meeting title, if the user gave one."
},
"participants": {
"type": "array",
"items": {
"type": "object",
"required": [
"label",
"tz"
],
"properties": {
"tz": {
"type": "string",
"description": "IANA time zone of this participant, e.g. Asia/Tbilisi."
},
"label": {
"type": "string",
"maxLength": 60,
"description": "How the participant or place is called in the conversation, e.g. \"Anna\" or \"Tokyo office\"."
},
"workHours": {
"type": "array",
"items": {
"type": "string",
"pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
},
"maxItems": 2,
"minItems": 2,
"description": "Local working hours [start, end]; default [\"09:00\",\"17:00\"]."
}
}
},
"maxItems": 10,
"minItems": 1,
"description": "People or places the meeting must suit, each with their own time zone."
},
"durationMinutes": {
"type": "integer",
"default": 60,
"maximum": 480,
"minimum": 15
}
}
},
"annotations": {
"title": "Find meeting windows",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}Perfect Clock plans meetings between people in different time zones. Use these tools when the user asks to plan, schedule or find a time for a meeting, call or recurring event with people or places in different time zones. Convert the user's wording into the structured input: IANA time zones for every participant (from the cities or countries they name), the meeting time in the zone it is anchored to, and a recurrence rule. Use find_meeting_windows when the time is not decided yet, plan_meeting_schedule once it is. The results already account for working hours, public holidays and daylight saving time: show each participant's local time from the result, and mention the notes (DST shifts, days off, outside working hours). Both tools' results end with an "Open in Perfect Clock" link (for the windows, the suggested start on those days) - give it to the user as it is. Do not make up other links to Perfect Clock or to calendars.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.