Asia/Vladivostok clock
Returns the current local time in Asia/Vladivostok over a remote MCP endpoint
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Asia/Vladivostok clock
Asia/Vladivostok clock is an MCP server for time utilities. It runs as a hosted remote server, so there is nothing to install locally.
The server runs as a hosted streamable-HTTP endpoint rather than a package to install locally, so clients connect to a URL and receive the present time for the Asia/Vladivostok zone. Its registry entry gives a one-line purpose and lists no local packages, only that remote.
The repository it belongs to, named-mcp-utilities, is a collection of small single-purpose MCP servers, each published under its own registry name. Each one covers a narrow calculation or format check, so this entry is best read as one focused time lookup rather than a general timekeeping service.
It suits developers and autonomous agent builders who need a timezone-aware clock reading inside an MCP-capable client. The README also includes a separate section of promotional endpoints for a third-party agent advertising service, which is unrelated to the clock itself.
Install
Run in a terminal
claude mcp add --transport http tz-asia-vladivostok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-vladivostok/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-vladivostok/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"tz-asia-vladivostok": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-vladivostok/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"tz-asia-vladivostok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-vladivostok/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"tz-asia-vladivostok": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-vladivostok/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"tz-asia-vladivostok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-vladivostok/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Timezone-specific current time
- Reports the current local time for the Asia/Vladivostok zone.
- Remote streamable-HTTP access
- Served as a hosted endpoint that MCP clients can connect to by URL.
- Registry-listed MCP name
- Published to the official MCP registry under a dedicated server name.
Good for
- Giving an AI agent the current local time in Vladivostok when scheduling or reporting
- Adding a timezone-aware clock lookup to an MCP-enabled assistant
- Testing how an MCP client handles a remote streamable-HTTP tool
Asia/Vladivostok clock FAQ
What does this server return?
Its registry entry describes it as the current local time in Asia/Vladivostok.
How is it connected?
The registry entry lists one remote endpoint using the streamable-http transport and no local packages.
How do I add Asia/Vladivostok clock to Claude Code?
Run this command in your terminal: claude mcp add --transport http tz-asia-vladivostok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-asia-vladivostok/mcp
What are the best alternatives to Asia/Vladivostok clock?
The closest alternatives to Asia/Vladivostok clock are Asia/Tomsk clock, Asia/Novosibirsk clock, Asia/Magadan clock, Asia/Ulaanbaatar clock and Asia/Kamchatka 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.