Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Time MCP Server

PYPI · TIME-MCP-PYPI · SCANNED SEP 13

Get the current UTC time in RFC 3339 format.

Available components

0 this week 53 Trust /100
Trust breakdown (7 categories)

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 Security33
  • Malware scan not yet available for this package.Unverified
  • CVE check failed: a known high-severity CVE affects mcp 1.13.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency5
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 25 tokens (~25/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 Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Time MCP Server server?

Time MCP Server runs locally as a PyPI package, launched with uvx time-mcp-pypi. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · time-mcp-pypi

# add to Claude Code
claude mcp add domdomegg-time-mcp-pypi -- uvx time-mcp-pypi
// .cursor/mcp.json
{
  "mcpServers": {
    "domdomegg-time-mcp-pypi": {
      "command": "uvx",
      "args": [
        "time-mcp-pypi"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "domdomegg-time-mcp-pypi": {
      "command": "uvx",
      "args": [
        "time-mcp-pypi"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add domdomegg-time-mcp-pypi -- uvx time-mcp-pypi
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "domdomegg-time-mcp-pypi": {
      "type": "local",
      "command": [
        "uvx",
        "time-mcp-pypi"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add domdomegg-time-mcp-pypi --command uvx --arg time-mcp-pypi
# ~/.hermes/config.yaml
mcp_servers:
  domdomegg-time-mcp-pypi:
    command: "uvx"
    args: ["time-mcp-pypi"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "domdomegg-time-mcp-pypi": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "time-mcp-pypi"
      ]
    }
  }
}
# add to Vellum
assistant mcp add domdomegg-time-mcp-pypi -t stdio -c uvx -a time-mcp-pypi
// mcp.json
{
  "mcpServers": {
    "domdomegg-time-mcp-pypi": {
      "command": "uvx",
      "args": [
        "time-mcp-pypi"
      ]
    }
  }
}
Changelog

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.

  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 11 Sept 26 +1
    • Stability: 0.97 → pass security
  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 4 Sept 26 +1
    • Stability: 0.97 → pass security
  • 2 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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/time-mcp-pypi@1.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 6 findings
ID CVE Severity Vector Fix available
GHSA-9h52-p55h-vw2f CVE-2025-66416 high yes
GHSA-jpw9-pfvf-9f58 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
GHSA-vj7q-gjh5-988w CVE-2026-59950 high yes
PYSEC-2026-1617 CVE-2025-66416 none yes
PYSEC-2026-3482 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
PYSEC-2026-3483 CVE-2026-59950 none yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~25 tokens

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 →

Tool Tokens
get_current_utc_time ~25

Gets the current UTC date and time in RFC 3339 format

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Time MCP Server server?

Time MCP Server is listed in the public MCP registry as io.github.domdomegg/time-mcp-pypi. Get the current UTC time in RFC 3339 format. This page covers its PyPI package (time-mcp-pypi).

Is the Time MCP Server server safe to use?

Time MCP Server scores 53 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 13 September 2026. 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 Time MCP Server server expose?

Time MCP Server exposes 1 tool: get_current_utc_time. Their descriptions and schemas cost roughly 25 tokens of context every time the server is loaded.

Is the Time MCP Server server still maintained?

Time MCP Server is still listed as active in the MCP registry. We last reached this channel on 13 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.