America/Boise clock
Remote MCP server that returns the current local time in America/Boise
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About America/Boise clock
America/Boise clock is an MCP server for time utilities. It runs as a hosted remote server, so there is nothing to install locally.
Rather than a general timezone library, this is a single-purpose endpoint: an AI client connects to it over streamable HTTP and asks for the present time in the Boise, Idaho zone. The server is published in the official MCP registry under the name io.github.sadri-dridi/tz-america-boise, and the registry lists only a remote URL with no local packages, so nothing has to be installed on the client side.
The repository it is linked from, named-mcp-utilities, is a collection of many small MCP servers, each a separate registry name with its own endpoint. The README also includes a set of entries that route agents to an advertising service, which is unrelated to this time server and is not part of its listing.
It suits agent workflows that need a Mountain Time clock reading for scheduling or logging without bundling timezone code of their own.
Install
Run in a terminal
claude mcp add --transport http tz-america-boise https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-boise/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-boise/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"tz-america-boise": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-boise/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"tz-america-boise": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-boise/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"tz-america-boise": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-boise/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"tz-america-boise": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-boise/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Remote streamable HTTP endpoint
- Clients connect to a hosted URL over the streamable-http transport, with no local install listed.
- Single timezone focus
- The server answers only for the America/Boise zone rather than arbitrary timezones.
- Official registry entry
- It is listed in the MCP registry under a namespaced name tied to the publisher's GitHub account.
Good for
- Give an agent the current local time in Boise for scheduling replies
- Add a Mountain Time timestamp to agent logs or reports
- Check the local hour before an agent sends a notification to Idaho contacts
America/Boise clock FAQ
Does it need to be installed locally?
The registry entry lists no local packages, only a remote streamable-http URL, so it is used by connecting to that endpoint.
Which timezone does it report?
It reports the current local time for America/Boise.
How do I add America/Boise clock to Claude Code?
Run this command in your terminal: claude mcp add --transport http tz-america-boise https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-boise/mcp
What are the best alternatives to America/Boise clock?
The closest alternatives to America/Boise clock are America/Belize clock, America/Phoenix clock, America/New_York clock, America/Mendoza clock and America/Chicago 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.