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

NUGET · TIMEMCPSERVER · SCANNED SEP 20

Get the current UTC time in RFC 3339 format.

Available components

nuget · TimeMcpServer 77
0 this week 77 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency18
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 Management87
  • Stability observed for 26 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 NuGet package, launched with dnx TimeMcpServer@1.1.1 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

nuget · TimeMcpServer

# add to Claude Code
claude mcp add domdomegg-time-mcp-nuget -- dnx TimeMcpServer@1.1.1 --yes
// .cursor/mcp.json
{
  "mcpServers": {
    "domdomegg-time-mcp-nuget": {
      "command": "dnx",
      "args": [
        "TimeMcpServer@1.1.1",
        "--yes"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "domdomegg-time-mcp-nuget": {
      "command": "dnx",
      "args": [
        "TimeMcpServer@1.1.1",
        "--yes"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add domdomegg-time-mcp-nuget -- dnx TimeMcpServer@1.1.1 --yes
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "domdomegg-time-mcp-nuget": {
      "type": "local",
      "command": [
        "dnx",
        "TimeMcpServer@1.1.1",
        "--yes"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  domdomegg-time-mcp-nuget:
    command: "dnx"
    args: ["TimeMcpServer@1.1.1", "--yes"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "domdomegg-time-mcp-nuget": {
      "Transport": "stdio",
      "Command": "dnx",
      "Arguments": [
        "TimeMcpServer@1.1.1",
        "--yes"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "domdomegg-time-mcp-nuget": {
      "command": "dnx",
      "args": [
        "TimeMcpServer@1.1.1",
        "--yes"
      ]
    }
  }
}
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.

  • 20 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.

  • 18 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

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

  • 13 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.

  • 11 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 20 Sept 2026 · Analysed nuget/TimeMcpServer@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 nuget
Reason Signature present, unreadable

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
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-nuget. Get the current UTC time in RFC 3339 format. This page covers its NuGet package (TimeMcpServer).

Is the Time MCP Server server safe to use?

Time MCP Server scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Time MCP Server server under?

Time MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.