# Perfect Clock (remote · perfectclock.cc)

Find meeting times across time zones and compare working hours.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `perfectclock.cc`: 79/100 (this document), [markdown](https://verifymcp.io/servers/cc-perfectclock-perfect-clock/perfectclock.md), [page](https://verifymcp.io/servers/cc-perfectclock-perfect-clock/perfectclock)

## Channel facts

- Endpoint: `https://perfectclock.cc/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 649 tokens (~162/item across 4 items; 2 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 77% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Perfect Clock MCP server?

Perfect Clock is a hosted endpoint at https://perfectclock.cc/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.

### Claude

```bash
claude mcp add --transport http cc-perfectclock-perfect-clock 'https://perfectclock.cc/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cc-perfectclock-perfect-clock": {
      "url": "https://perfectclock.cc/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cc-perfectclock-perfect-clock": {
      "type": "http",
      "url": "https://perfectclock.cc/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cc-perfectclock-perfect-clock]
url = "https://perfectclock.cc/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cc-perfectclock-perfect-clock": {
      "type": "remote",
      "url": "https://perfectclock.cc/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cc-perfectclock-perfect-clock --url 'https://perfectclock.cc/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cc-perfectclock-perfect-clock:
    url: "https://perfectclock.cc/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cc-perfectclock-perfect-clock": {
      "Transport": "http",
      "Url": "https://perfectclock.cc/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cc-perfectclock-perfect-clock -t streamable-http -u 'https://perfectclock.cc/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cc-perfectclock-perfect-clock": {
      "type": "http",
      "url": "https://perfectclock.cc/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 79, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 78, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_meeting_windows” rewrote its description, which is the text the model reads
- [security] Tool “plan_meeting_schedule” rewrote its description, which is the text the model reads

### 2026-11-04 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 73)

First indexed and scored.

## MCP tools (2)

### `plan_meeting_schedule` (~211 tokens)

Plan a meeting schedule

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.

Input parameters:

- `durationMinutes` (integer)
- `maxOccurrences` (integer): How many upcoming meetings to list.
- `participants` (array, required): People or places the meeting must suit, each with their own time zone.
- `rule` (object, required): Recurrence of the meeting.
- `time` (string, required): Local start time in `tz`.
- `title` (string, required): Meeting title.
- `tz` (string, required): Time zone the meeting time is fixed in (usually the organizer's).

### `find_meeting_windows` (~188 tokens)

Find meeting windows

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.

Input parameters:

- `days` (integer)
- `durationMinutes` (integer)
- `from` (string): First day in `tz`; default today.
- `participants` (array, required): People or places the meeting must suit, each with their own time zone.
- `title` (string): Meeting title, if the user gave one.
- `tz` (string, required): Time zone whose calendar days are scanned (usually the organizer's).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cc-perfectclock-perfect-clock/perfectclock#diagnostics

## Score history

- 2026-11-06: 79
- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73

## Common questions

### What is the Perfect Clock MCP server?

Perfect Clock is an MCP server listed in the public MCP registry as cc.perfectclock/perfect-clock. Find meeting times across time zones and compare working hours. This page covers its hosted endpoint (https://perfectclock.cc/mcp).

### Is the Perfect Clock MCP server safe to use?

Perfect Clock scores 79 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 Perfect Clock MCP server expose?

Perfect Clock exposes 2 tools: plan_meeting_schedule, find_meeting_windows. Their descriptions and schemas cost roughly 399 tokens of context every time the server is loaded.

### Does the Perfect Clock MCP server require authentication?

No. We connected to Perfect Clock without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Perfect Clock MCP server still maintained?

Perfect Clock is still listed as active in the MCP registry. We last reached this channel on 6 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 Perfect Clock MCP server?

VerifyMCP ran 14 checks on Perfect Clock, 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.

## Links

- Remote endpoint: https://perfectclock.cc/mcp
- Website: https://perfectclock.cc/
- Changelog RSS feed: https://verifymcp.io/servers/cc-perfectclock-perfect-clock/perfectclock.xml
- Changelog JSON feed: https://verifymcp.io/servers/cc-perfectclock-perfect-clock/perfectclock/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cc-perfectclock-perfect-clock/perfectclock.json
- HTML version of this page: https://verifymcp.io/servers/cc-perfectclock-perfect-clock/perfectclock