# io.github.theoddden/atomic-clock (pypi · atomic-clock-mcp)

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

- Trust score: 0/100 (low)
- Change this week: −48
- Registry status: active
- Liveness: dead
- Owner verified: no
- Last scored: 2026-09-13

> **Dead**: every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically.

## Components

- pypi · `atomic-clock-mcp`: 0/100 (this document), [markdown](https://verifymcp.io/servers/theoddden-atomic-clock/atomic-clock-mcp.md), [page](https://verifymcp.io/servers/theoddden-atomic-clock/atomic-clock-mcp)

## Channel facts

- Registry: `pypi`
- Package: `atomic-clock-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-13.

- **Supply Chain Security**: 50/100
  - No malware found by supply-chain analysis.
  - Known CVEs could not be checked: we could not find this package in its registry.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we could not find this package in its registry.
- **Provenance & Transparency**: 0/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: the registry has no such package, so there's no artefact to verify.
  - License check failed: the registry has no such package, so no license can be read.
  - Maintenance check failed: the registry has no such package, so there's no release history to read.
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 33 tokens (~33/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.theoddden/atomic-clock MCP server?

io.github.theoddden/atomic-clock runs locally as a PyPI package, launched with uvx atomic-clock-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add theoddden-atomic-clock -- uvx atomic-clock-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "theoddden-atomic-clock": {
      "command": "uvx",
      "args": [
        "atomic-clock-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theoddden-atomic-clock": {
      "command": "uvx",
      "args": [
        "atomic-clock-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add theoddden-atomic-clock -- uvx atomic-clock-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theoddden-atomic-clock": {
      "type": "local",
      "command": [
        "uvx",
        "atomic-clock-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theoddden-atomic-clock --command uvx --arg atomic-clock-mcp
```

### Hermes

```yaml
mcp_servers:
  theoddden-atomic-clock:
    command: "uvx"
    args: ["atomic-clock-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "theoddden-atomic-clock": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "atomic-clock-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add theoddden-atomic-clock -t stdio -c uvx -a atomic-clock-mcp
```

### Other

```json
{
  "mcpServers": {
    "theoddden-atomic-clock": {
      "command": "uvx",
      "args": [
        "atomic-clock-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-13 (score 0, −10)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-12 (score 10, −9)

- [functional regression] Security disclosure: fail → unverified

### 2026-09-11 (score 19, −10)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-10 (score 29, −9)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-09 (score 38, −10)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-08 (score 48, 0)

- [security regression] Known CVEs: pass → unverified
- [security regression] Install scripts: pass → unverified
- [security] The scripts that run when this package is installed changed: build_backend
- [functional regression] Dependency health: pass → unverified

### 2026-09-07 (score 48, 0)

- [security improvement] Malware scan: unverified → pass

### 2026-09-06 (score 48)

First indexed and scored.

## MCP tools (1)

### `get_atomic_time` (~33 tokens)

Get current UTC time from an atomic clock via NTP

Input parameters:

- `server` (string): NTP server to query

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/theoddden-atomic-clock/atomic-clock-mcp#diagnostics

## Score history

- 2026-09-13: 0
- 2026-09-12: 10
- 2026-09-11: 19
- 2026-09-10: 29
- 2026-09-09: 38
- 2026-09-08: 48
- 2026-09-07: 48
- 2026-09-06: 48

## Common questions

### What is the io.github.theoddden/atomic-clock MCP server?

io.github.theoddden/atomic-clock is an MCP server listed in the public MCP registry as io.github.theoddden/atomic-clock. Current UTC time from NTP atomic clocks. Zero-dependency stdio server. This page covers its PyPI package (atomic-clock-mcp).

### Is the io.github.theoddden/atomic-clock MCP server safe to use?

io.github.theoddden/atomic-clock scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.theoddden/atomic-clock MCP server expose?

io.github.theoddden/atomic-clock exposes 1 tool: get_atomic_time. Their descriptions and schemas cost roughly 33 tokens of context every time the server is loaded.

### Is the io.github.theoddden/atomic-clock MCP server still maintained?

io.github.theoddden/atomic-clock has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 6 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/atomic-clock-mcp/
- Socket report: https://socket.dev/pypi/package/atomic-clock-mcp
- Changelog RSS feed: https://verifymcp.io/servers/theoddden-atomic-clock/atomic-clock-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theoddden-atomic-clock/atomic-clock-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theoddden-atomic-clock/atomic-clock-mcp