io.github.theoddden/atomic-clock
PYPI · ATOMIC-CLOCK-MCP
Current UTC time from NTP atomic clocks. Zero-dependency stdio server.
Available components
Last scanned (2 months ago)
Scores higher than 0% of PyPI servers
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: even once the server responds again it stays dead until it is manually reinstated.
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. How we score → Why this is hard to score →
Supply Chain Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: we could not find this package in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency0
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: the registry has no such package, so there's no artefact to verify. See how to fix → View diagnostics → Fail
- License check failed: the registry has no such package, so no license can be read. See how to fix → Fail
- Maintenance check failed: the registry has no such package, so there's no release history to read. See how to fix → Fail
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 33 tokens (~33/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
Checks we ran (11)
- Malware scan
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: we could not find this package in its registry.
- Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
- Dependency health in Supply Chain SecurityDependency health could not be checked: we could not find this package in its registry.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Sept 26 −10
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Sept 26 −9
- Security disclosure: fail → unverified ▼ functional
- 11 Sept 26 −10
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Sept 26 −9
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Sept 26 −10
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Sept 26 0
- Known CVEs: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- The code this package runs automatically changed: its declared build backend security
- Dependency health: pass → unverified ▼ functional
- 7 Sept 26 0
- Malware scan: unverified → pass ▲ security
- 6 Sept 26 48
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 13 Sept 2026 · Analysed pypi/atomic-clock-mcp@0.1.1
Provenance Package not found
The registry answered that no such package exists, so no provenance could be looked up.
| Result | Package not found |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_atomic_time ~33
Get current UTC time from an atomic clock via NTP
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | NTP server to query |
No output schema declared.
No examples provided.
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.
pypi · atomic-clock-mcp
claude mcp add theoddden-atomic-clock -- uvx atomic-clock-mcp
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.
What did VerifyMCP test on the io.github.theoddden/atomic-clock MCP server?
VerifyMCP ran 11 checks on io.github.theoddden/atomic-clock, covering Malware scan, Source repository, Provenance, License and 7 more. 5 items could not be completed, a gap on our side rather than a finding about io.github.theoddden/atomic-clock: Known CVEs, Install scripts, Dependency health, Security disclosure and 1 more. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.