America/Detroit clock
Remote MCP server returning the current local time in America/Detroit for agents
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About America/Detroit clock
America/Detroit clock is an MCP server for time utilities. It runs as a hosted remote server, so there is nothing to install locally.
This is a single-purpose remote MCP server that reports the present local time for the America/Detroit time zone. It is served over streamable HTTP from a hosted endpoint, so there is nothing to install; an MCP client simply connects to the remote URL.
It is one of many small, narrowly named utility servers published from the same repository, each registered under its own official registry name. The repository describes them as public MCP servers intended for autonomous clients. The README also lists separate servers tied to a placement service for agents, but this one is a plain time lookup.
It suits agents or workflows that need a quick, reliable Eastern-time reading for Detroit without bundling a time zone library. The registry entry does not list individual tool names, so exact inputs and output format are best checked by connecting to the endpoint.
Install
Run in a terminal
claude mcp add --transport http tz-america-detroit https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-detroit/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-detroit/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"tz-america-detroit": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-detroit/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"tz-america-detroit": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-detroit/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"tz-america-detroit": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-detroit/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"tz-america-detroit": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-detroit/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Detroit local time
- Returns the current local time for the America/Detroit time zone.
- Remote streamable HTTP
- Runs as a hosted remote endpoint using the streamable-http transport, with no local package to install.
- Dedicated registry name
- Registered in the official MCP registry as io.github.sadri-dridi/tz-america-detroit.
- Single-purpose design
- Does one narrow job, which keeps it simple for agents to discover and call.
Good for
- Give an agent the current time in Detroit for scheduling
- Check Eastern-time business hours for a Michigan-based contact
- Timestamp logs or messages in Detroit local time
- Avoid bundling time zone data in a lightweight agent
America/Detroit clock FAQ
What does this server do?
It returns the current local time in the America/Detroit time zone.
How do I connect to it?
Use the streamable-http remote URL from the registry entry in an MCP client that supports remote servers; no package is installed.
Is there a local package to install?
No. The registry entry lists no packages, only a remote endpoint.
Where is the source?
The repository is github.com/sadri-dridi/named-mcp-utilities, which hosts many similar small servers.
How do I add America/Detroit clock to Claude Code?
Run this command in your terminal: claude mcp add --transport http tz-america-detroit https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-detroit/mcp
What are the best alternatives to America/Detroit clock?
The closest alternatives to America/Detroit clock are America/New_York clock, America/Chicago clock, America/Toronto clock, America/Dawson clock and America/Denver 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.