Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@World Time By Api Ninjas what time is it in Tokyo right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
用于访问 World Time By Api Ninjas API 的 MCP 服务器。
EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-world_time_by_api_ninjas）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用
✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅！
Related MCP server: Timezone MCP Server
这是一个 MCP 服务器，用于访问 World Time By Api Ninjas API。
PyPI 包名: bach-world_time_by_api_ninjas
版本: 1.0.0
传输协议: stdio
pip install bach-world_time_by_api_ninjaspip install -e .# 运行（uvx 会自动安装并运行）
uvx --from bach-world_time_by_api_ninjas bach_world_time_by_api_ninjas
# 或指定版本
uvx --from bach-world_time_by_api_ninjas@latest bach_world_time_by_api_ninjaspython server.py# 安装
pip install bach-world_time_by_api_ninjas
# 运行（命令名使用下划线）
bach_world_time_by_api_ninjas此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-world_time_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-world_time_by_api_ninjas", "bach_world_time_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-world_time_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-world_time_by_api_ninjas", "bach_world_time_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}此服务器提供以下工具:
v1worldtimeAPI Ninjas World Time API endpoint. Returns the current date and time by city/state/country, location coordinates (latitude/longitude), or timezone. One of the following parameter combinations must be set: lat + lon, city (state and country optional), timezone
端点: GET /v1/worldtime
参数:
lat (string): Latitude of desired location.
lon (string): Longitude of desired location.
city (string): City name.
state (string): US state name or 2-letter abbreviation (for United States cities only).
country (string): Country name or 2-letter country code.
timezone (string): Timezone of desired location (e.g. Europe/London).
传输协议: stdio
HTTP 客户端: httpx
MIT License - 详见 LICENSE 文件。
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
API Ninjas World Time API endpoint. Returns the current date and time by city/state/country, location coordinates (latitude/longitude), or timezone. One of the following parameter combinations must be set: lat + lon, city (state and country optional), timezone
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | Latitude of desired location. | |
| lon | No | Longitude of desired location. | |
| city | No | City name. | |
| state | No | US state name or 2-letter abbreviation (for United States cities only). | |
| country | No | Country name or 2-letter country code. | |
| timezone | No | Timezone of desired location (e.g. Europe/London). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions the tool returns data but doesn't disclose behavioral traits like rate limits, authentication needs, error handling, or response format. The description is minimal and doesn't compensate for the lack of annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately sized and front-loaded, starting with the purpose and followed by parameter combination rules. Every sentence adds necessary information without waste, though it could be slightly more structured for clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (6 parameters, no output schema, no annotations), the description is incomplete. It lacks details on return values, error cases, or any behavioral context, making it insufficient for an AI agent to fully understand tool invocation and response handling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all 6 parameters. The description adds value by explaining the required parameter combinations (e.g., lat+lon, city with optional state/country, timezone), which clarifies semantics beyond individual param descriptions, but doesn't provide additional syntax or format details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Returns the current date and time' with multiple location input methods. It specifies the verb ('Returns') and resource ('current date and time'), but lacks differentiation from siblings since none exist, making it clear but not distinguishing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides implied usage by stating 'One of the following parameter combinations must be set' with examples, which guides when to use certain parameters. However, it lacks explicit when-not scenarios or alternative tool references, and no siblings exist for comparison, so guidance is basic.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0v1worldtimeWith only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'v1worldtime' has a clear and distinct purpose: retrieving world time data based on various location parameters.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'v1worldtime' follows a clear pattern (version prefix + descriptive name) and does not conflict with any other naming conventions.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. While this tool covers world time retrieval comprehensively, the server's scope feels thin with only one operation, which may hinder agent workflows that require more diverse interactions.
For the domain of world time retrieval, the tool provides robust coverage with support for city/state/country, coordinates, and timezone inputs. However, there are minor gaps, such as lacking tools for timezone conversion, historical time data, or batch queries, which could limit advanced use cases.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Current time, timezone conversion & date math for AI agents. On Cloudflare Workers.
Timezone MCP — wraps WorldTimeAPI (free, no auth)
Current time in any IANA time zone, plus the full time-zone list. Via timeapi.io.
Get the current time in any timezone. Explore concise timezone info to pick the right region. Simp…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/bachai-world-time-by-api-ninjas'
If you have feedback or need assistance with the MCP directory API, please join our Discord server