Atomic Clock

io.github.theodddenPublished by GitHub account theodddenv0.1.1Updated Oct 24, 2026

Current UTC time from NTP atomic clocks. Zero-dependency stdio server.

VerifiedSTDIODesktop only

Overview

AI-generated overview

A local stdio MCP server that gives an assistant the current UTC time sourced from NTP atomic clocks.

What you can do
Provides the current UTC time, taken from NTP atomic clock sources, so the assistant can answer time questions with an authoritative reference rather than its own estimate. It is a zero-dependency stdio server, so it exposes this single capability without extra libraries. No individual tools are listed in the manifest.
When to use it
Useful when an assistant needs an accurate current UTC timestamp, for example to anchor logs, schedules, or time-sensitive answers to a trusted clock source.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package atomic-clock-mcp over stdio. Desktop only; no web execution. No authentication, environment variables, or headers are declared. Network access is implied by fetching time from NTP sources.
Before you install
The server contacts external NTP time sources, so its queries leave the machine. No credentials or write actions are declared. It reports UTC only, so local time zones must be handled by the assistant.

Installation

In SourceWeft

  1. Open Atomic Clock in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.