Skip to content

Perfect Clock MCP server

cc.perfectclock/perfect-clockperfectclock.ccstreamable-httpv1.0.0Scanned

Find meeting times across time zones and compare working hours.

2 tools: 2 change things.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

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

The Perfect Clock MCP server is published by perfectclock.cc, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: plan_meeting_schedule and find_meeting_windows), but cannot delete data. None of its tools only reads.

1 tool reads private data (find_meeting_windows).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

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

Last scanned Nov 9, 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.

2 tools

Changes things 2Claude Code: ask
  • find_meeting_windowsFinds 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 weeke…Reads private data1 finding

    Why it is in this group

    • The name "find_meeting_windows" says "find": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe name "find_meeting_windows" says "find" and "meeting": it reads calendars.

    Findings

    • Warn

      The server marks "find_meeting_windows" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "find_meeting_windows" says "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find meeting windows
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • plan_meeting_schedulePlans a one-off or recurring meeting with people in other time zones when its time is known (e.g.No findings

    Why it is in this group

    • The name "plan_meeting_schedule" says "schedule": a word for a change.
    Description, as the server wrote 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.

    Annotations the server declares

    • title: Plan a meeting schedule
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
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.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:23 UTC, unchanged since Oct 26, 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
2
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
  • WarnThe whole server

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

    Matched text

    https://perfectclock.cc/mcp: tools/list returned 2 tools to an anonymous client, including plan_meeting_schedule (write), find_meeting_windows (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "find_meeting_windows" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "find_meeting_windows" says "find": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

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

claude mcp add --transport http perfect-clock https://perfectclock.cc/mcp
claude mcp add --transport http perfect-clock https://perfectclock.cc/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": [],
    "ask": [
      "mcp__perfect-clock__plan_meeting_schedule",
      "mcp__perfect-clock__find_meeting_windows"
    ],
    "deny": []
  }
}

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

Capability tags behind 1 rule
  • mcp__perfect-clock__find_meeting_windows private-data

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/cc.perfectclock/perfect-clock/verify?hash=4815dfa1a311adb280e43908bcc51b252af735d940c479fa03c917c05b70275e" | jq -e '.changed == false'

Pinned hash 4815dfa1a311, from Nov 9, 2026, 06:18 UTC.

Watch

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

https://radar.anlyon.com/servers/cc.perfectclock/perfect-clock/changes.xml

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

Badge

Anlyon Radar badge for cc.perfectclock/perfect-clock
[![Anlyon Radar](https://radar.anlyon.com/badge/cc.perfectclock/perfect-clock.svg)](https://radar.anlyon.com/servers/cc.perfectclock/perfect-clock)

Source: MCP Registry. Synced Oct 25, 2026, 19:17 UTC.

Perfect Clock MCP server: questions and answers

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

Is the Perfect Clock MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Perfect Clock MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

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

2 tools: 2 write. plan_meeting_schedule and find_meeting_windows.

Does the Perfect Clock MCP server need sign-in or OAuth?

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

Does the Perfect Clock MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Perfect Clock MCP server changed its tools?

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