← MCP

Time MCP ServerTime MCP Server

Model Context Protocol

本地Local 只读Read-only verified lifecycle: active 核验Checked 2026-10-23

只做两件事：查当前时间、换时区。不读写项目文件；仍应核对所用 server 的实现与权限。

Does two things only: report the current time and convert time zones. No files, no network — the lowest-risk category of server.

适合与不适合When to use it, when not to

场景	是否适合
日程安排需要准确时间	✅
跨时区协作	✅
避免模型编造时间	✅
做定时任务 / 调度	❌ 它只查询时间，不调度

最后一条是常见误解——名字叫 time，容易以为能做定时。实际它只回答「现在几点」和「A 时区的 X 点是 B 时区几点」。

Scenarios where an agent needs the current date and time to reason about scheduling, logs or freshness.

Not a fit for anything beyond time — it is one tool with one narrow purpose.

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-20

出品属地Origin: 国外出品foreign-made　国外主体（网信办公示名单未见对应备案主体）。foreign entity (no matching filing entity in the CAC registry).
国内使用Direct access: 大陆可直连direct OK　官网仓库在 GitHub，大陆直连波动（同日实测 200/000 混合）；npm / PyPI 安装源实测稳定可达。Hosted on GitHub — direct reachability from mainland fluctuates (200/000 mixed on the same day); npm / PyPI install routes measured stable.
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-20 检索 13 批附件，https://www.cac.gov.cn/2024-04/02/c_1713729983803145.htm）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (13 batch attachments searched 2026-10-20, https://www.cac.gov.cn/2024-04/02/c_1713729983803145.htm); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

11 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 本身不调用模型，是被客户端调用的接口实现。使用 IANA 时区名，支持系统时区自动检测。
It calls no model itself; it is an interface implementation called by clients. It uses IANA timezone names and supports automatic system-timezone detection.
运行位置Where it runs: 本地 Python 进程，通过 stdio 通信。

依赖 Python MCP SDK 1.x（要求 mcp=1.29.0,2），SDK 2.0 重命名了该 server 使用的 API。

2026-08-30 修复了容器 bind mount 在 Docker / Podman / SELinux 下的安全与兼容问题。

推荐用 uvx 直接运行，无需预安装。
A local Python process communicating over stdio.

It depends on the Python MCP SDK 1.x (requires mcp=1.29.0,2); SDK 2.0 renamed the APIs this server uses.

A 2026-08-30 fix addressed security and compatibility issues of container bind mounts under Docker / Podman / SELinux.

Running directly with uvx, no pre-install needed, is recommended.
本地文件Local files: 无任何文件访问能力。不涉及文件读写。
No file-access capability whatsoever. No file reads or writes involved.
关机后的任务Tasks after shutdown: 不支持。单次时间查询为同步操作，随客户端进程结束。
Not supported. A single time query is a synchronous operation, ending with the client process.
工具与扩展Tools & extensions: 提供 2 个工具：get_current_time（按指定时区取当前时间）与 convert_time（时区间转换）。输出为结构化时间数据，可直接消费。
It provides 2 tools: get_current_time (current time in a given timezone) and convert_time (conversion between timezones). Output is structured time data, ready for direct consumption.
上下文与记忆Context & memory: 无状态。每次调用独立，不保留历史。
Stateless. Each call is independent; no history is kept.
权限与限制Permissions & limits: 无实质权限风险：不访问文件、不访问网络、不写任何状态。全部权限是「能查询当前时间和做时区换算」。
No substantive permission risk: no file access, no network access, writes no state. Its entire permission set is "being able to query the current time and convert timezones".
适合什么任务Best for: 给 Agent 提供可靠的时间与时区换算能力。适合需要避免模型猜时间的场景（如日程、跨时区协作）。
Gives an Agent reliable time and timezone-conversion capability. Suits scenarios where the model should not guess the time (scheduling, cross-timezone collaboration).
传输方式Transport: 支持 stdio，并提供容器部署方式（Docker / Podman）。

2026-08-30 修复 bind mount 安全与兼容问题（含 SELinux），与 fetch、git 属同一条修复 commit（#2205）。

官方 README（2026-10-08 全文核验）只给本地进程接入（uvx / pip / Docker），没有远程传输的官方启动方式。
Supports stdio, and offers container deployment (Docker / Podman).

The 2026-08-30 bind-mount security/compatibility fix (including SELinux) is the same commit (#2205) as for fetch and git.

The official README (full-text verification 2026-10-08) gives only local-process integration (uvx / pip / Docker); there is no official launch method for a remote transport.
认证机制Authentication: 无独立认证层，但本 server 无任何外部资源访问，认证与否不影响安全。
No separate authentication layer, but this server accesses no external resources; whether auth exists makes no security difference.
权限范围Permission scope: 无文件与网络访问，不读不写任何外部资源。与 sequential-thinking 同属权限风险最低的一类，可放心在敏感环境使用。
No file or network access; reads and writes no external resources. Together with sequential-thinking it is the lowest permission-risk class; safe in sensitive environments.

头号误解Top misconception

以为模型自己知道准确时间，需要它取系统时间而非猜Assuming the model already knows the exact time — it needs this to read the system clock rather than guess
以为能用它做定时任务，它只查询时间，不调度Assuming it can schedule tasks — it only reads the time, it does not schedule

未知项清单Known unknowns

是否支持 Streamable HTTP（仓库未声明）
容器形态下的认证配置
是否支持夏令时切换的边界情况处理

Whether Streamable HTTP is supported (not declared in the repo)
Authentication configuration in the container form
Whether edge cases of daylight-saving transitions are handled

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-23，内容更新日content updated on 2026-10-08。

类型Type	名称Name	链接Link
docs	MCP · Time ServerMCP · Time Server	https://github.com/modelcontextprotocol/servers/tree/main/src/time
changelog	MCP · Time 目录变更历史MCP · Time directory change history	https://github.com/modelcontextprotocol/servers/commits/main/src/time
changelog	MCP · Servers ReleasesMCP · Servers Releases	https://github.com/modelcontextprotocol/servers/releases
repo	MCP · Servers 仓库 README（生产环境免责声明）MCP · Servers repo README (production-use disclaimer)	https://github.com/modelcontextprotocol/servers

实测记录Measured runs

本档未在真实客户端逐项跑通；工具清单与权限来自官方 README。

This site has not completed measured runs. The test protocol is at protocols/mcp/_protocol.md.

变更记录说明Change-log notes

本对象无独立 changelog 页，变更记录在目录 commit 历史中：

日期	内容
2026-08-30	修复容器 bind mount 安全与兼容问题（与 fetch、git 同一条 commit #2205）
2026-08-18	文档补充 Python MCP 1.x 版本要求

注意：SDK 2.0 重命名了该 server 使用的 API，官方锁在 mcp>=1.29.0,<2。如果你的环境装了 SDK 2.x，这个 server 可能起不来。

This object has no standalone changelog page; change records are in the directory's commit history:

Date	Content
2026-08-30	Fix container bind-mount security and compatibility (same commit #2205 as fetch and git)
2026-08-18	Document the Python MCP 1.x version requirement

Note: SDK 2.0 renamed the APIs this server uses, and the official side pins mcp>=1.29.0,<2. If your environment has SDK 2.x installed, this server may fail to start.

工具清单Tool inventory

工具	参数	说明
`get_current_time`	`timezone`（IANA 名）	取指定时区的当前时间
`convert_time`	`source_timezone` `time`（HH:MM） `target_timezone`	时区换算

用 IANA 时区名（如 America/New_York），不是 UTC 偏移量。这也是它比「让模型自己算时区」可靠的地方——IANA 名带夏令时规则。

Tool	Parameters	Description
`get_current_time`	`timezone` (IANA name)	current time in the given timezone
`convert_time`	`source_timezone` `time` (HH:MM) `target_timezone`	timezone conversion

It uses IANA timezone names (e.g. America/New_York), not UTC offsets. That is also where it beats "letting the model do timezone math" — IANA names carry daylight-saving rules.

权限评价Permission assessment

MCP server 里权限风险最低的一类：

检查项	结果
读文件	❌ 无
写文件	❌ 无
访问网络	❌ 无
持久化状态	❌ 无
删除能力	❌ 无

全部权限就是「能问系统现在几点」。这类 server 值得单独指出—— 它说明 MCP 生态里也有零风险工具。

The lowest permission-risk class among MCP servers:

Check	Result
Read files	❌ none
Write files	❌ none
Network access	❌ none
Persisted state	❌ none
Delete capability	❌ none

Its entire permission set is "being able to ask the system what time it is". This class of server deserves calling out — it shows the MCP ecosystem also has zero-risk tools.

安装Installation

官方推荐 uvx 直接运行，无需预安装：

uvx mcp-server-time

也支持 pip install mcp-server-time。

The official recommendation is running directly with uvx, no pre-install needed:

uvx mcp-server-time

pip install mcp-server-time is also supported.