Asia/Tashkent clock
Remote MCP endpoint that reports the current local time in Asia/Tashkent
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Asia/Tashkent clock
Asia/Tashkent clock is an MCP server for time utilities. It runs as a hosted remote server, so there is nothing to install locally.
This server is a single-purpose remote endpoint: it returns the present local time for the Asia/Tashkent timezone. It is published under the registry name io.github.sadri-dridi/tz-asia-tashkent and is reached over streamable HTTP, with no package to install.
It belongs to a collection of small named MCP utilities in one repository, where each folder maps to its own registry name. The same repository also lists other narrow utilities and a group of Agent Ads entries that route autonomous agents to an advertising service, so the endpoint is hosted on a shared sensor domain rather than run locally.
It suits agent clients that need a quick timezone lookup for Uzbekistan without bundling their own date library. The registry entry does not list individual tool names or parameters.
Install
Run in a terminal
claude mcp add --transport http tz-asia-tashkent https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-tashkent/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-tashkent/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"tz-asia-tashkent": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-tashkent/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"tz-asia-tashkent": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-tashkent/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"tz-asia-tashkent": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-tashkent/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"tz-asia-tashkent": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-tashkent/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Tashkent local time
- Returns the current local time for the Asia/Tashkent timezone.
- Streamable HTTP transport
- Connects to a hosted remote URL using streamable HTTP, with no local package required.
- Registry-listed endpoint
- Published in the official MCP registry as io.github.sadri-dridi/tz-asia-tashkent.
- Part of a utility set
- One of many narrow named MCP servers kept in a single repository, each with its own registry name.
Good for
- Let an agent check the current time in Uzbekistan
- Schedule or timestamp messages for Tashkent-based contacts
- Convert an agent's UTC context into Tashkent local time
- Test remote MCP client connections with a minimal server
Asia/Tashkent clock FAQ
What does this MCP server do?
It reports the current local time in the Asia/Tashkent timezone.
How do I connect to it?
Use the streamable HTTP remote URL listed in the registry entry; there is no package to install.
Where is the source?
It is listed in the sadri-dridi/named-mcp-utilities repository on GitHub, which collects many small named MCP servers.
Does the server list its tools?
No tool names or parameters are listed in the registry entry or README.
How do I add Asia/Tashkent clock to Claude Code?
Run this command in your terminal: claude mcp add --transport http tz-asia-tashkent https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-tashkent/mcp
What are the best alternatives to Asia/Tashkent clock?
The closest alternatives to Asia/Tashkent clock are Asia/Samarkand clock, Asia/Dushanbe clock, Asia/Ashgabat clock, Asia/Tomsk clock and Asia/Baku clock.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.