_ registry / mcp streamable-http · checked 1h ago

worldclockpro-time

https://worldclock.pro

Registry code: ce2083dbd54dadda

api record

A real clock for AI agents: current time, timezone conversion, and DST facts from the IANA tzdb.

from a public catalogue that lists it, not from the operator

endpoint
https://worldclock.pro/mcp
protocol
streamable-http ·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 worldclockpro-time live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is worldclockpro-time free to use?
Yes — the hub reached it with no key and no payment.
What tools does worldclockpro-time have?
5 tools: search_cities, get_current_time, convert_time, get_dst_transitions, time_by_coordinates.
Is worldclockpro-time 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
253ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 311 checks · signed record
  • down → live
  • unknown → live
_ what it is for
topic
developer tools
used for
  • get current time in a city
  • convert time between timezones
  • check daylight saving transitions
  • find timezone by coordinates
takes → gives
text, data → data
tools
5 reads
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 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.

  • search_cities reads unknown 12h ago

    Find cities by name (multilingual, diacritic-insensitive) — useful to resolve a place to a canonical slug, IANA timezone, and coordinates before calling the time tools. Each result includes a source_url linking the city's worldclock.pro page.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Max results (default 10)."
    },
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "City name or partial name (≥ 2 characters)."
    },
    "country": {
      "type": "string",
      "maxLength": 2,
      "minLength": 2,
      "description": "Optional ISO 3166-1 alpha-2 country filter, e.g. \"JP\"."
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • get_current_time reads unknown 16h ago

    Get the current local time (or the time at a given instant) in one or more locations. Each location is a city name, an IANA timezone / abbreviation, or coordinates. Up to 50 locations. Results include a source_url linking the matching worldclock.pro page when available.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "locations"
  ],
  "properties": {
    "at": {
      "type": "string",
      "description": "Optional ISO 8601 instant to evaluate instead of now (read as UTC if it has no zone)."
    },
    "locations": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "query": {
            "type": "string",
            "description": "City name, slug, or alias — e.g. \"Tokyo\", \"new-york\", \"nyc\"."
          },
          "latitude": {
            "type": "number",
            "maximum": 90,
            "minimum": -90,
            "description": "Latitude in degrees [-90, 90]."
          },
          "timezone": {
            "type": "string",
            "description": "IANA zone id (\"America/New_York\") or a curated abbreviation (\"pst\", \"utc\")."
          },
          "longitude": {
            "type": "number",
            "maximum": 180,
            "minimum": -180,
            "description": "Longitude in degrees [-180, 180]."
          }
        },
        "description": "A location identified by exactly ONE of: query, timezone, or latitude+longitude together.",
        "additionalProperties": false
      },
      "maxItems": 50,
      "minItems": 1
    }
  },
  "additionalProperties": false
}
    arguments 46 lines
  • convert_time reads unknown 16h ago

    Given a UTC instant (or a wall time in a source location), return the corresponding local time in each of up to 50 target locations. Results include a source_url linking the matching worldclock.pro page when available.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "targets"
  ],
  "properties": {
    "utc": {
      "type": "string",
      "description": "The instant to convert, as an ISO 8601 string. Read as UTC if it has no zone designator."
    },
    "from": {
      "type": "object",
      "required": [
        "dateTime",
        "location"
      ],
      "properties": {
        "dateTime": {
          "type": "string",
          "description": "Local wall time in the source location, e.g. \"2026-06-29T09:00\"."
        },
        "location": {
          "type": "object",
          "properties": {
            "query": {
              "type": "string",
              "description": "City name, slug, or alias — e.g. \"Tokyo\", \"new-york\", \"nyc\"."
            },
            "latitude": {
              "type": "number",
              "maximum": 90,
              "minimum": -90,
              "description": "Latitude in degrees [-90, 90]."
            },
            "timezone": {
              "type": "string",
              "description": "IANA zone id (\"America/New_York\") or a curated abbreviation (\"pst\", \"utc\")."
            },
            "longitude": {
              "type": "number",
              "maximum": 180,
              "minimum": -180,
              "description": "Longitude in degrees [-180, 180]."
            }
          },
          "description": "A location identified by exactly ONE of: query, timezone, or latitude+longitude together.",
          "additionalProperties": false
        }
      },
      "description": "Alternative to `utc`: a wall time in a specific source location.",
      "additionalProperties": false
    },
    "targets": {
      "type": "array",
      "items": {
        "$ref": "#/properties/from/properties/location"
      },
      "maxItems": 50,
      "minItems": 1
    }
  },
  "additionalProperties": false
}
    arguments 64 lines
  • get_dst_transitions reads unknown 16h ago

    Report whether a location observes daylight saving time, the next clock change, and every summer/winter-time transition (date, local time, and before/after offset) within a year. The result includes a source_url linking the matching worldclock.pro page when available.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "location"
  ],
  "properties": {
    "year": {
      "type": "integer",
      "description": "Calendar year to list transitions for (default: the current year)."
    },
    "location": {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "City name, slug, or alias — e.g. \"Tokyo\", \"new-york\", \"nyc\"."
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude in degrees [-90, 90]."
        },
        "timezone": {
          "type": "string",
          "description": "IANA zone id (\"America/New_York\") or a curated abbreviation (\"pst\", \"utc\")."
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude in degrees [-180, 180]."
        }
      },
      "description": "A location identified by exactly ONE of: query, timezone, or latitude+longitude together.",
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}
    arguments 41 lines
  • time_by_coordinates reads unknown 12h ago

    Resolve the timezone for a latitude/longitude coordinate (via geo-tz) and return the local time there.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "at": {
      "type": "string",
      "description": "Optional ISO 8601 instant to evaluate instead of now (read as UTC if it has no zone)."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in degrees [-90, 90]."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in degrees [-180, 180]."
    }
  },
  "additionalProperties": false
}
    arguments 27 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 ce2083dbd54dadda.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ce2083dbd54dadda/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/ce2083dbd54dadda/badge.svg)](https://brick.blue/agent/ce2083dbd54dadda?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
90%

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.