Chuk MCP Time

MCP运维云端

提供方 IBM

运维云端 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude DesktopClaude
查看接入方式

一个基于NTP共识和IANA tzdata的高精度时间服务,提供准确的时间信息和时区转换功能,适用于需要可信时间源、时区转换或分布式系统的应用场景。

一句话选型结论

按资料字段整理

Chuk MCP Time 属于运维云端类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude Desktop、Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 3 仓库热度,无公开仓库时显示未标注
工具数 7 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量7暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

高精度时间Python本地部署NTP共识时区转换时钟漂移检测分布式系统

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
uvx chuk-mcp-time

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Python,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 7 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 7 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Chuk MCP Time当前 7 stdio · 本地进程 本地部署 有 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方IBM上游标注的维护方 IBM
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

19.3 KB
来自项目仓库与上游目录的原文,未做删改

chuk-mcp-time

High-accuracy time + timezone MCP server using NTP consensus & IANA tzdata

A Model Context Protocol (MCP) server that provides extremely accurate time information by querying multiple NTP servers, removing outliers, and computing a consensus time independent of the system clock. Now includes comprehensive timezone support using IANA tzdata for accurate timezone conversions, DST handling, and timezone discovery. Perfect for applications requiring trusted time sources, timezone conversions, detecting clock drift, or working in distributed systems.

> This is a demonstration project provided as-is for learning and testing purposes.

Features

🎯 Multi-Source Consensus: Queries 4-7 NTP servers simultaneously and computes consensus time using median with outlier rejection

⚡ Async-First: Built on asyncio for maximum performance with concurrent NTP queries

⏱️ Latency Compensation: Automatically adjusts timestamps for query duration so returned time represents "now"

🔒 Type-Safe: 100% Pydantic models with full type hints and validation using enums

🌍 IANA Timezone Support: Complete timezone handling with DST, conversions, and discovery

🔍 Clock Drift Detection: Compare system clock against trusted NTP sources

⏰ Timezone Conversions: Convert between any IANA timezones with accurate DST handling

🗺️ Timezone Discovery: List and search 600+ IANA timezones to prevent hallucination

📊 Transparent: Returns all source data, consensus method, error estimates, and query duration

⚙️ Configurable: Environment-based configuration for NTP servers and consensus parameters

🚀 Deployment Examples: Docker support, GitHub Actions CI/CD, Fly.io deployment

🌐 Public Endpoint: Try instantly at https://time.chukai.io/mcp - no installation needed!

Quick Start

🌐 Use the Public HTTP Endpoint (No Installation)

Try it instantly with our hosted MCP server:

Endpoint: https://time.chukai.io/mcp

Configure in Claude Desktop or any MCP client to connect to the HTTP streamable endpoint. No installation required!

📦 Installation Options

Using uvx (recommended for local use)```bash

Run directly with uvx (auto-installs and runs)

uvx chuk-mcp-time

For STDIO mode (Claude Desktop, mcp-cli)

uvx chuk-mcp-time

For HTTP mode

uvx chuk-mcp-time http


#### Using pip```bash
pip install chuk-mcp-time

From source```bash

Clone the repository

git clone <repository-url>
cd chuk-mcp-time
make dev-install


## Demo

See the server in action with a comprehensive demo:```bash
# Run the demo script
uv run examples/demo.py

# Or with Python
python examples/demo.py

The demo shows:
- ✅ Querying 4 NTP servers with consensus
- ✅ System clock drift detection (detects ±millisecond accuracy)
- ✅ Timezone conversions (6 timezones from single consensus)
- ✅ Stability across 5 samples

Example output:```
📊 Results:
Consensus Time (UTC).................... 2025-11-28T10:04:59.916227+00:00
Sources Used............................ 4/4
Estimated Error......................... ±10.0 ms
Query Time.............................. 42.8 ms

🕐 Clock Comparison:
Delta................................... +2.4 ms
Status.................................. ✅ OK - System clock is accurate


See examples/README.md for detailed demo documentation.

## Usage with MCP Clients

### Option 1: Public HTTP Endpoint (Easiest)

Connect to our hosted server at `https://time.chukai.io/mcp`

**Claude Desktop Configuration:**

Add to your `claude_desktop_config.json`:```json
{
  &quot;mcpServers&quot;: {
    &quot;time&quot;: {
      &quot;url&quot;: &quot;https://time.chukai.io/mcp&quot;
    }
  }
}

✅ No installation required
✅ Always up to date
✅ High availability

Option 2: Local STDIO (Most Common)

Run locally using uvx for STDIO transport (works with Claude Desktop, mcp-cli, etc.):

Claude Desktop Configuration:```json
{
"mcpServers": {
"time": {
"command": "uvx",
"args": ["chuk-mcp-time"]
}
}
}


**Or run manually:**```bash
# Run with uvx
uvx chuk-mcp-time

# Or with Python
python -m chuk_mcp_time.server

Option 3: Local HTTP Server

Run your own HTTP server for testing/development:```bash

Start HTTP server

uvx chuk-mcp-time http

Or with Python

python -m chuk_mcp_time.server http

Server runs on http://localhost:8000


**Claude Desktop Configuration:**```json
{
  &quot;mcpServers&quot;: {
    &quot;time&quot;: {
      &quot;url&quot;: &quot;http://localhost:8000/mcp&quot;
    }
  }
}

Available Tools

1. get_time_utc

Get current UTC time with high accuracy using NTP consensus.

Parameters:
- mode (optional): &quot;fast&quot; (default, 4 servers) or &quot;accurate&quot; (7 servers)
- compensate_latency (optional): true (default) to adjust timestamp for query duration

Returns:```json
{
"iso8601_time": "2025-11-28T01:23:45.123456+00:00",
"epoch_ms": 1732756425123,
"sources_used": 4,
"total_sources": 4,
"consensus_method": "median_with_outlier_rejection",
"estimated_error_ms": 12.5,
"source_samples": [...],
"warnings": ["Applied +150.2ms latency compensation to timestamp"],
"system_time": "2025-11-28T01:23:49.456789+00:00",
"system_delta_ms": 4333.333,
"query_duration_ms": 150.2,
"latency_compensated": true
}


**Latency Compensation:**
By default, the timestamp is adjusted to account for the time spent querying NTP servers. This means the returned timestamp represents &quot;now&quot; (when the response is sent), not when the NTP queries started. This is especially important for slow networks or accurate mode.

### 2. `get_time_for_timezone`

Get current time for a specific timezone with high accuracy.

**Parameters:**
- `timezone_name`: IANA timezone name (e.g., `&quot;America/New_York&quot;`, `&quot;Europe/London&quot;`)
- `mode` (optional): `&quot;fast&quot;` or `&quot;accurate&quot;`
- `compensate_latency` (optional): `true` (default) to adjust timestamp for query duration

**Returns:**
Same as `get_time_utc` plus:```json
{
  &quot;timezone&quot;: &quot;America/New_York&quot;,
  &quot;local_time&quot;: &quot;2025-11-27T20:23:45.123456-05:00&quot;
}

3. get_local_time

Get current time for a specific IANA timezone with high accuracy.

Uses NTP consensus for accurate UTC time, then converts to the requested timezone using IANA tzdata. Provides authoritative local time independent of system clock.

Parameters:
- timezone: IANA timezone identifier (e.g., &quot;America/New_York&quot;, &quot;Europe/London&quot;, &quot;Asia/Tokyo&quot;)
- mode (optional): &quot;fast&quot; or &quot;accurate&quot;
- compensate_latency (optional): true (default) to adjust timestamp for query duration

Returns:```json
{
"local_datetime": "2025-11-27T20:23:45.123456-05:00",
"timezone": "America/New_York",
"utc_offset_seconds": -18000,
"is_dst": false,
"abbreviation": "EST",
"source_utc": "2025-11-28T01:23:45.123456+00:00",
"tzdata_version": "2024b",
"estimated_error_ms": 12.5
}


### 4. `convert_time`

Convert a datetime from one timezone to another using IANA rules.

Performs timezone conversion independent of system clock. Uses IANA tzdata to handle all DST transitions, historical changes, and political boundaries.

**Parameters:**
- `datetime_str`: ISO 8601 datetime string (naive, will be interpreted in from_timezone)
- `from_timezone`: Source IANA timezone identifier
- `to_timezone`: Target IANA timezone identifier

**Returns:**```json
{
  &quot;from_timezone&quot;: &quot;America/New_York&quot;,
  &quot;from_datetime&quot;: &quot;2025-06-15T14:30:00-04:00&quot;,
  &quot;from_utc_offset_seconds&quot;: -14400,
  &quot;to_timezone&quot;: &quot;Europe/London&quot;,
  &quot;to_datetime&quot;: &quot;2025-06-15T19:30:00+01:00&quot;,
  &quot;to_utc_offset_seconds&quot;: 3600,
  &quot;offset_difference_seconds&quot;: 18000,
  &quot;explanation&quot;: &quot;Europe/London is 5.0 hours ahead of America/New_York (UTC-4.0 → UTC+1.0)&quot;
}

5. list_timezones

List available IANA timezones with optional filtering.

Returns all valid IANA timezone identifiers. Helps discover correct timezone names and prevents hallucination of invalid timezones.

Parameters:
- country_code (optional): ISO 3166 country code filter (e.g., &quot;US&quot;, &quot;GB&quot;, &quot;FR&quot;)
- search (optional): Substring search filter (case-insensitive)

Returns:```json
{
"timezones": [
{
"id": "America/New_York",
"country_code": "US",
"comment": null,
"example_city": "New York"
},
{
"id": "Europe/London",
"country_code": "GB",
"comment": null,
"example_city": "London"
}
],
"total_count": 2,
"tzdata_version": "2024b"
}


**Example searches:**
- `search: &quot;New&quot;` → Returns all timezones with &quot;New&quot; in the name
- `search: &quot;Tokyo&quot;` → Returns Asia/Tokyo
- No filters → Returns all 600+ IANA timezones

### 6. `get_timezone_info`

Get detailed information about a timezone including upcoming transitions.

Provides comprehensive timezone metadata including current offset, DST status, and upcoming transitions (e.g., DST changes). Useful for planning and understanding timezone behavior.

**Parameters:**
- `timezone`: IANA timezone identifier
- `mode` (optional): `&quot;fast&quot;` or `&quot;accurate&quot;` (affects accuracy of current time)

**Returns:**```json
{
  &quot;timezone&quot;: &quot;America/New_York&quot;,
  &quot;country_code&quot;: null,
  &quot;comment&quot;: null,
  &quot;current_offset_seconds&quot;: -18000,
  &quot;current_is_dst&quot;: false,
  &quot;current_abbreviation&quot;: &quot;EST&quot;,
  &quot;transitions&quot;: [
    {
      &quot;from_datetime&quot;: &quot;2026-03-08T07:00:00+00:00&quot;,
      &quot;utc_offset_seconds&quot;: -14400,
      &quot;is_dst&quot;: true,
      &quot;abbreviation&quot;: &quot;EDT&quot;
    },
    {
      &quot;from_datetime&quot;: &quot;2026-11-01T06:00:00+00:00&quot;,
      &quot;utc_offset_seconds&quot;: -18000,
      &quot;is_dst&quot;: false,
      &quot;abbreviation&quot;: &quot;EST&quot;
    }
  ],
  &quot;tzdata_version&quot;: &quot;2024b&quot;
}

7. compare_system_clock

Compare system clock against trusted NTP sources to detect drift.

Parameters:
- mode (optional): &quot;fast&quot; or &quot;accurate&quot;

Returns:```json
{
"system_time": "2025-11-28T01:23:49.456789+00:00",
"trusted_time": "2025-11-28T01:23:45.123456+00:00",
"delta_ms": 4333.333,
"estimated_error_ms": 12.5,
"status": "error"
}


Status values:
- `&quot;ok&quot;`: Delta &lt; 100ms
- `&quot;drift&quot;`: Delta 100-1000ms
- `&quot;error&quot;`: Delta &gt; 1000ms

## Configuration

Configuration can be set via environment variables or `.env` file:```bash
# NTP Servers (comma-separated)
TIME_SERVER_NTP_SERVERS=time.cloudflare.com,time.google.com,time.apple.com

# NTP timeout in seconds (0.5 to 10.0)
TIME_SERVER_NTP_TIMEOUT=2.0

# Maximum outlier deviation in milliseconds (100.0 to 60000.0)
TIME_SERVER_MAX_OUTLIER_DEVIATION_MS=5000.0

# Minimum number of sources required (1 to 10)
TIME_SERVER_MIN_SOURCES=3

# Maximum disagreement before warning in milliseconds (10.0 to 5000.0)
TIME_SERVER_MAX_DISAGREEMENT_MS=250.0

# Number of servers to query in fast mode (2 to 10)
TIME_SERVER_FAST_MODE_SERVER_COUNT=4

See .env.example for complete configuration template.

How It Works

Consensus Algorithm

  1. Query Multiple Sources: Queries 4-7 NTP servers concurrently based on mode
  2. RTT Adjustment: Adjusts timestamps by adding half the round-trip time
  3. Outlier Removal: Iteratively removes outliers > 5 seconds from median
  4. Median Consensus: Computes median of remaining timestamps
  5. Error Estimation: Calculates IQR (interquartile range) as error estimate
  6. Latency Compensation: Adds query duration to timestamp so result represents "now"
  7. System Comparison: Compares consensus against system clock

Latency Compensation

The server tracks how long it takes to query NTP servers and compute consensus (typically 100-500ms). By default, this duration is added to the consensus timestamp, so the returned time represents when the response is sent, not when queries began.

Example:
- Query starts at T+0ms
- NTP consensus computed at T+150ms → timestamp = 12:00:00.000
- Latency compensation: 12:00:00.000 + 150ms = 12:00:00.150
- Response sent at T+150ms with timestamp 12:00:00.150

This ensures the timestamp is as accurate as possible when received by the caller. You can disable this with compensate_latency=false if you prefer the raw consensus timestamp.

Timezone Support

The server uses Python's zoneinfo module with IANA tzdata for authoritative timezone information:

  1. IANA tzdata Source: Uses official IANA Time Zone Database (maintained by IANA, curated by global experts)
  2. DST Handling: Automatic daylight saving time transitions using historical and future rules
  3. Political Boundaries: Handles all timezone changes, country boundaries, and historical adjustments
  4. Transition Detection: Identifies upcoming DST changes and offset modifications
  5. No System Clock Dependency: All timezone conversions use NTP consensus time, not system clock

Timezone Data Hierarchy:
- UTC Authority: NTP consensus (time.google.com, time.cloudflare.com, etc.)
- Political Time: IANA tzdata (official timezone database)
- Local Conversion: Python's zoneinfo module
- Result: Accurate local time independent of system clock

Default NTP Servers

  • time.cloudflare.com - Cloudflare's anycast NTP
  • time.google.com - Google's public NTP
  • time.apple.com - Apple's NTP servers
  • 0-3.pool.ntp.org - NTP Pool Project servers

All servers are stratum 1-2 for maximum accuracy.

Development

Setup```bash

Clone repository

git clone <repository-url>
cd chuk-mcp-time

Install development dependencies

make dev-install


### Testing```bash
# Run tests (skip network tests)
make test

# Run tests with coverage
make test-cov

# Run all tests including network tests
pytest -v

# Run specific test
pytest tests/test_consensus.py -v

Code Quality```bash

Run linter

make lint

Auto-format code

make format

Type checking

make typecheck

Security checks

make security

Run all checks

make check


### Building```bash
# Build distribution packages
uv build

# Build Docker image
make docker-build

# Run Docker container
make docker-run

Deployment

Fly.io```bash

Deploy to Fly.io

flyctl deploy

Or use GitHub Actions (push to main branch)

git push origin main


### Docker```bash
# Build image
docker build -t chuk-mcp-time .

# Run container
docker run -p 8000:8000 chuk-mcp-time

# With custom config
docker run -p 8000:8000 \
  -e TIME_SERVER_NTP_TIMEOUT=5.0 \
  -e TIME_SERVER_MIN_SOURCES=5 \
  chuk-mcp-time

Architecture```

chuk-mcp-time/
├── src/chuk_mcp_time/
│ ├── init.py
│ ├── config.py # Pydantic Settings configuration
│ ├── models.py # Pydantic models (enums, responses)
│ ├── ntp_client.py # Async NTP client
│ ├── consensus.py # Consensus algorithm engine
│ ├── timezone_utils.py # IANA timezone utilities
│ └── server.py # MCP server with 7 tools
├── tests/
│ ├── test_config.py
│ ├── test_consensus.py
│ ├── test_ntp_client.py
│ └── test_server_tools.py
├── pyproject.toml
├── Makefile
├── Dockerfile
├── fly.toml
└── README.md


## Use Cases

### 1. Detecting Clock Drift```python
# Use compare_system_clock to monitor clock health
response = await compare_system_clock(mode=&quot;accurate&quot;)

if response.status == &quot;error&quot;:
    print(f&quot;⚠️  System clock is off by {response.delta_ms:.1f}ms!&quot;)
    # Take corrective action...

2. Trusted Timestamps for Logs```python

Get consensus time for reliable logging

time_info = await get_time_utc(mode="fast")

log_entry = {
"event": "user_login",
"timestamp": time_info.iso8601_time,
"source_count": time_info.sources_used,
"error_ms": time_info.estimated_error_ms
}


### 3. Timezone Conversions for Scheduling```python
# Convert meeting time between timezones
result = await convert_time(
    datetime_str=&quot;2025-12-15T14:00:00&quot;,
    from_timezone=&quot;America/New_York&quot;,
    to_timezone=&quot;Asia/Tokyo&quot;
)

print(result.explanation)
# &quot;Asia/Tokyo is 14.0 hours ahead of America/New_York (UTC-5.0 → UTC+9.0)&quot;
print(f&quot;Meeting time in Tokyo: {result.to_datetime}&quot;)
# &quot;2025-12-16T04:00:00+09:00&quot;

4. Multi-Region Time Coordination```python

Get accurate local time for different regions

ny_time = await get_local_time("America/New_York")
london_time = await get_local_time("Europe/London")
tokyo_time = await get_local_time("Asia/Tokyo")

All from the same NTP consensus - guaranteed consistency

Each includes DST status, offset, and abbreviation

print(f"NY: {ny_time.local_datetime} ({ny_time.abbreviation})")
print(f"London: {london_time.local_datetime} ({london_time.abbreviation})")
print(f"Tokyo: {tokyo_time.local_datetime} ({tokyo_time.abbreviation})")


### 5. Discovering Valid Timezones```python
# Search for timezones to avoid hallucination
timezones = await list_timezones(search=&quot;New&quot;)

for tz in timezones.timezones:
    print(f&quot;{tz.id} - {tz.example_city}&quot;)
# America/New_York - New York
# America/North_Dakota/New_Salem - New Salem
# ...

6. Planning Around DST Transitions```python

Get upcoming DST transitions

info = await get_timezone_info("America/New_York")

print(f"Current: {info.current_abbreviation} (DST: {info.current_is_dst})")
print(f"Upcoming transitions:")
for transition in info.transitions:
print(f" {transition.from_datetime}: {transition.abbreviation} (DST: {transition.is_dst})")


### 7. Financial/Trading Applications```python
# High-accuracy mode for financial operations
time_info = await get_time_utc(mode=&quot;accurate&quot;)

if time_info.estimated_error_ms &lt; 20:
    # Error &lt; 20ms, safe to use for timestamp-sensitive operations
    execute_trade(timestamp=time_info.epoch_ms)
else:
    # Too much uncertainty, defer or use alternative timing
    log_warning(&quot;Time uncertainty too high&quot;, error_ms=time_info.estimated_error_ms)

Why Use This Over System Time?

Problems with System Clocks

  • Drift: System clocks drift over time (typically 10-50 ppm)
  • Virtualization: VMs can have severe time skew
  • Containers: Docker containers inherit host clock issues
  • Development: Dev machines often have incorrect time
  • Distributed Systems: Hard to trust time across multiple hosts

This Solution Provides

  • Independent Verification: Multiple external sources
  • Outlier Detection: Automatic removal of bad sources
  • Transparency: See all source data and warnings
  • Error Bounds: Know the accuracy of the time
  • Auditability: Full data for debugging time issues

Performance

  • Fast Mode: ~40-150ms (queries 4 servers)
  • Accurate Mode: ~100-300ms (queries 7 servers)
  • Typical Accuracy: ±10-50ms (much better than system clock drift)
  • Throughput: Limited by NTP query rate (recommend caching for high-frequency use)

Latency Breakdown

  • NTP queries (concurrent): 20-100ms per server
  • Consensus calculation: <1ms
  • Latency compensation: Automatically added to timestamp
  • Total round-trip: 40-300ms depending on mode and network

Limitations

  • Network Required: Requires internet access to NTP servers
  • Latency: 100-500ms per query (not suitable for microsecond precision)
  • Rate Limiting: Don't query too frequently (respect NTP pool guidelines)
  • Accuracy: ±10-50ms typical (good enough for most applications, not atomic clock precision)

Contributing

Contributions welcome! Please:

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes with tests
  4. Run make check to ensure quality
  5. Submit a pull request

License

Apache License 2.0 - See LICENSE for details.

Credits

Built with:
- chuk-mcp-server - High-performance MCP server framework
- Pydantic - Data validation using Python type hints
- NTP Pool Project servers

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Chuk MCP Time 怎么安装?

在客户端按下面的安装命令接入:uvx chuk-mcp-time。装完在客户端配置里引用同一个包或端点。

Chuk MCP Time 怎么在 Claude Desktop、Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Chuk MCP Time 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Chuk MCP Time 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Chuk MCP Time 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Chuk MCP Time 能提供哪些能力?

资料显示约 7 个工具;能力标签包括 分布式系统、Python、Claude。具体工具清单以官方文档为准。

Chuk MCP Time 需要什么运行环境?

运行时为 Python;属于本地进程,需要在本机装好运行环境。

Chuk MCP Time 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。