Atomic Clock MCP server
Current UTC time from NTP atomic clocks. Zero-dependency stdio server.
D43/100grade D
Adoption
Not measured yet
Usage numbers are collected on the next scan
Reviews
Write oneNobody has reviewed Atomic Clock yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Atomic Clock tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
1 high
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancerepository not readable: repo not found3/15
- Maintainer identityno repository or website to verify2/10
Findings (1)
- highPackage atomic-clock-mcp not found on pypi
code.package-missing
Overall 43/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add atomic-clock -- uvx atomic-clock-mcp
Atomic Clock: common questions
- Is Atomic Clock MCP server safe?
- Not recommended: it is graded D (43/100). Read the Atomic Clock safety report
- How do I install Atomic Clock?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Atomic Clock need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Atomic Clock maintained?
- The latest release is v0.1.1.