Australia/Hobart clock
Remote MCP server that returns the current local time in Hobart, Australia
- Pricing
- Open source
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Australia/Hobart clock
Australia/Hobart clock is an open-source MCP server for time utilities. It runs as a hosted remote server, so there is nothing to install locally.
This server exposes a single narrow capability: the current local time for the Australia/Hobart timezone. It is hosted as a remote streamable-http endpoint, so there is nothing to install; an MCP client simply connects to the URL listed in the registry.
It is one of many small single-purpose servers in the Named MCP utilities repository, where each folder maps to its own official registry name. Other entries in that collection cover things like calendar leap-year checks and ID-format inspections, and the same repository also lists a set of Agent Ads placement endpoints.
It suits autonomous clients and developers who need a quick timezone lookup for Tasmania without bundling a timezone library or writing their own time logic.
Install
Run in a terminal
claude mcp add --transport http tz-australia-hobart https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-australia-hobart/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-australia-hobart/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"tz-australia-hobart": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-australia-hobart/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"tz-australia-hobart": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-australia-hobart/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"tz-australia-hobart": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-australia-hobart/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"tz-australia-hobart": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-australia-hobart/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Hobart local time
- Returns the current local time in the Australia/Hobart timezone.
- Remote streamable-http
- Runs as a hosted endpoint reachable over streamable-http, with no local package to install.
- Single-purpose design
- Does one narrow job, which keeps the tool surface small for agent clients.
- Registry listed
- Published in the official MCP registry as io.github.sadri-dridi/tz-australia-hobart.
Good for
- Letting an agent check the current time in Tasmania before scheduling a call
- Adding a timezone lookup to an MCP client without extra libraries
- Testing a client's handling of remote streamable-http MCP servers
- Timestamping agent outputs with Hobart local time
Pricing
Open source
Australia/Hobart clock FAQ
What does this server return?
The current local time in the Australia/Hobart timezone.
How do I connect to it?
Use the streamable-http remote URL from the registry entry: https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-australia-hobart/mcp.
Do I need to install a package?
No. The registry entry lists no packages, only a hosted remote endpoint.
Where is the source repository?
It is part of the sadri-dridi/named-mcp-utilities repository on GitHub.
Is Australia/Hobart clock free?
Yes. Australia/Hobart clock is open source, so you can use and self-host it for free.
How do I add Australia/Hobart clock to Claude Code?
Run this command in your terminal: claude mcp add --transport http tz-australia-hobart https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-australia-hobart/mcp
What are the best alternatives to Australia/Hobart clock?
The closest alternatives to Australia/Hobart clock are Australia/Sydney clock, Asia/Taipei clock, Australia/Perth clock, Australia/Darwin clock and Atlantic/Azores 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.