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.

io.github.mcpcentral-io/mcp-time

REMOTE · MCP.TIME.MCPCENTRAL.IO · 2 COMPONENTS · SCANNED SEP 22

Time MCP server via HTTP

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

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

Install

How do I install the io.github.mcpcentral-io/mcp-time server?

io.github.mcpcentral-io/mcp-time is a hosted endpoint at https://mcp.time.mcpcentral.io/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.time.mcpcentral.io

# add to Claude Code
claude mcp add --transport http mcpcentral-io-mcp-time 'https://mcp.time.mcpcentral.io/'
// .cursor/mcp.json
{
  "mcpServers": {
    "mcpcentral-io-mcp-time": {
      "url": "https://mcp.time.mcpcentral.io/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mcpcentral-io-mcp-time": {
      "type": "http",
      "url": "https://mcp.time.mcpcentral.io/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.mcpcentral-io-mcp-time]
url = "https://mcp.time.mcpcentral.io/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mcpcentral-io-mcp-time": {
      "type": "remote",
      "url": "https://mcp.time.mcpcentral.io/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mcpcentral-io-mcp-time --url 'https://mcp.time.mcpcentral.io/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  mcpcentral-io-mcp-time:
    url: "https://mcp.time.mcpcentral.io/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mcpcentral-io-mcp-time": {
      "Transport": "http",
      "Url": "https://mcp.time.mcpcentral.io/"
    }
  }
}
# add to Vellum
assistant mcp add mcpcentral-io-mcp-time -t streamable-http -u 'https://mcp.time.mcpcentral.io/'
// mcp.json
{
  "mcpServers": {
    "mcpcentral-io-mcp-time": {
      "type": "http",
      "url": "https://mcp.time.mcpcentral.io/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • Endpoint reachability: reachable → behind authorisation security
    • Stability: 0.37 → unverified security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

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 22 Sept 2026 · Probed https://mcp.time.mcpcentral.io

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcpcentral.io CN=WE1,O=Google Trust Services,C=US 6 Aug 2026 4 Nov 2026 ECDSA 256 ECDSA-SHA256 2f34bde0d90972a3137bde247fb2eea0
SANs: mcpcentral.io, mcp.time.mcpcentral.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.time.mcpcentral.io. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
mcpcentral.io. present 2371 13 Verified
mcp.time.mcpcentral.io. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.time.mcpcentral.io Verified 200
http (plaintext) http://mcp.time.mcpcentral.io HTTPS enforced 301 https://mcp.time.mcpcentral.io/
MCP tools · 6 exposed · ~345 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
convert_time ~94

Converts a time from a source IANA timezone to a target IANA timezone.

NameTypeReqDescription
sourceTimezonestringyesSource IANA timezone name (e.g., "Asia/Shanghai")
targetTimezonestringyesTarget IANA timezone name (e.g., "Europe/London")
timestringyesThe time to convert (e.g., "2025-03-23 12:30:00")
NameTypeReqDescription
convertedTimestringyes
hourDifferencenumberyes

No examples provided.

current_time ~72

Returns the current time in UTC and a specified or guessed IANA timezone.

NameTypeReqDescription
formatstringFormat for the returned time string (default YYYY-MM-DD HH:mm:ss)
timezonestringIANA timezone name (e.g., "America/New_York"). Defaults to the server's guessed timezone
NameTypeReqDescription
localTimestringyes
timezonestringyes
utcTimestringyes

No examples provided.

days_in_month ~44

Returns the number of days in the month of a given date.

NameTypeReqDescription
datestringThe date to check (format: YYYY-MM-DD). Defaults to current date
NameTypeReqDescription
daysintegeryes

No examples provided.

get_timestamp ~45

Converts a date-time string to a Unix timestamp in milliseconds.

NameTypeReqDescription
timestringThe time to convert (format: YYYY-MM-DD HH:mm:ss). Defaults to current time
NameTypeReqDescription
timestampnumberyes

No examples provided.

get_week_year ~49

Returns the week number and ISO week number for a given date.

NameTypeReqDescription
datestringThe date to check (e.g., "2025-03-23"). Defaults to current date
NameTypeReqDescription
isoWeekintegeryes
weekintegeryes

No examples provided.

relative_time ~41

Calculates the relative time from now to a given date-time string.

NameTypeReqDescription
timestringyesThe time to compare (format: YYYY-MM-DD HH:mm:ss)
NameTypeReqDescription
relativeTimestringyes

No examples provided.

Common questions

What is the io.github.mcpcentral-io/mcp-time server?

io.github.mcpcentral-io/mcp-time is listed in the public MCP registry as io.github.mcpcentral-io/mcp-time. Time MCP server via HTTP. This page covers its hosted endpoint (https://mcp.time.mcpcentral.io).

Is the io.github.mcpcentral-io/mcp-time server safe to use?

io.github.mcpcentral-io/mcp-time scores 34 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.mcpcentral-io/mcp-time server expose?

io.github.mcpcentral-io/mcp-time exposes 6 tools: current_time, relative_time, days_in_month, get_timestamp, convert_time, get_week_year. Their descriptions and schemas cost roughly 345 tokens of context every time the server is loaded.

Does the io.github.mcpcentral-io/mcp-time server require authentication?

No. We connected to io.github.mcpcentral-io/mcp-time without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.mcpcentral-io/mcp-time server still maintained?

io.github.mcpcentral-io/mcp-time is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.