_ registry / mcp http-sse · checked 2h ago

perfect-clock

https://perfectclock.cc

Registry code: 5e51e1a4f0bf3c5e

api record

Perfect Clock plans meetings between people in different time zones.

Whenever the user wants to schedule, plan or find a time for a meeting, call, sync or recurring event with people or places in different time zones, call these tools first - before answering, and instead of working out times, daylight saving or holidays yourself.

endpoint
https://perfectclock.cc/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is perfect-clock live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is perfect-clock free to use?
Not measured yet.
What tools does perfect-clock have?
2 tools: plan_meeting_schedule, find_meeting_windows.
Is perfect-clock safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
969ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • plan_meeting_schedule unknown never probed

    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.

    mcp-tool

    {
  "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
    }
  }
}
    arguments 134 lines
  • find_meeting_windows unknown never probed

    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.

    mcp-tool

    {
  "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
    }
  }
}
    arguments 70 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5e51e1a4f0bf3c5e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5e51e1a4f0bf3c5e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5e51e1a4f0bf3c5e/badge.svg)](https://brick.blue/agent/5e51e1a4f0bf3c5e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.