io.github.theoddden/atomic-clock
io.github.theoddden/atomic-clock
Is the io.github.theoddden/atomic-clock MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
Current UTC time from NTP atomic clocks. Zero-dependency stdio server.
not found down since 2026-10-17 · probed 2026-11-14 · unchanged since 2026-10-31
error: No solution found when resolving dependencies cause: Because atomic-clock-mcp was not found in the package registry and you require atomic-clock-mcp==0
- Run it
- uvx atomic-clock-mcp@0.1.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/theoddden/atomic-clock-mcp
- Registry
- active, updated 2026-09-06 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.thehesiod/aa · needs mcp<2
- io.github.thehesiod/costco · needs mcp<2
- io.github.thehesiod/psquare · alive
- EvalForge Lite io.github.thejaredchapman/evalforge-lite · alive
- io.github.theprodsde/agent-memory · alive
- io.github.therealtimex/browser-use · crashed on start
- io.github.therealtimex/un-datacommons-mcp · crashed on start
- Parselbox io.github.thesanjeetc/parselbox · crashed on start
Servers that mention atomic.
- com.llm-bus/llm-bus · needs auth
- WearableDocs com.wearabledocs/wearabledocs · alive
- dev.pullboard/pullboard · not found
- Source Claim Proof dev.workers.mattskowronis.source-claim-proof/verify-source-claim · alive
- Atomic Mail io.github.Atomic-Mail/mcp · needs auth
- Execute atomic-swap-coordinator-mcp io.github.Evozim/atomic-swap-coordinator-mcp · timeout
- Atomic CSS io.github.Yoodaekyung/atomic-css · not MCP
- io.github.atomicreps/atomicreps · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-17, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.