# UTC second

> UTC second is an MCP server for time utilities. Remote MCP endpoint for the current UTC second, aimed at autonomous agent clients. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Platforms:** API
- **Repository:** https://github.com/sadri-dridi/named-mcp-utilities
- **MCP Registry name:** io.github.sadri-dridi/second-utc
- **Categories:** [time utilities](https://ai-powered.com/categories/time-utilities)
- **Listing updated:** 2026-11-18

## About

This is a small remote MCP endpoint published under the registry name io.github.sadri-dridi/second-utc. It is reachable over streamable HTTP through a hosted worker URL, so there is no package to install and clients connect directly to the remote address.

It belongs to a collection called Named MCP utilities, in which each folder maps to one official registry name with its own intake. Sibling entries cover narrow checks such as UTC ISO week dates, leap-year tests for several calendars and identifier-format probes. The README does not document the tools this particular server exposes, and it describes the collection as listed for autonomous clients.

It suits developers who want to experiment with minimal, single-purpose MCP endpoints in an agent workflow. Treat details such as exact output format as something to confirm by connecting to the endpoint.

## Features

- **Remote streamable HTTP:** Connects over a hosted streamable-http endpoint, with no local package to install.
- **Single-purpose utility:** Registered as its own named MCP server focused on the UTC second.
- **Official registry name:** Listed in the MCP registry as io.github.sadri-dridi/second-utc.
- **Part of a utilities set:** Sits alongside many similar narrow date, time and identifier-shape servers in the same repository.

## Good for

- Giving an agent a simple time-related lookup via MCP
- Testing MCP client connections against a minimal remote server
- Exploring small utility servers for autonomous agent workflows

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http second-utc https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/second-utc/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/second-utc/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "second-utc": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/second-utc/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "second-utc": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/second-utc/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "second-utc": {
      "serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/second-utc/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "second-utc": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/second-utc/mcp"
    }
  }
}
```

## FAQ

### How do I connect to this server?

Use the streamable-http remote URL from the registry entry: https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/second-utc/mcp.

### Does it need to be installed locally?

No. The registry entry lists no packages, only a remote endpoint.

### What is its registry name?

io.github.sadri-dridi/second-utc.

### Where does it come from?

It is one folder in the sadri-dridi/named-mcp-utilities GitHub repository, which lists many similar public MCP servers.

### How do I add UTC second to Claude Code?

Run this command in your terminal: claude mcp add --transport http second-utc https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/second-utc/mcp

### What are the best alternatives to UTC second?

The closest alternatives to UTC second are UTC second 0-60 band, UTC second 0-60 band, UTC offset hours, Seconds to minutes and UTC quarter.

## Where this comes from

- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [UTC second 0-60 band](https://ai-powered.com/mcp/utc-second-0-60-band): UTC second 0-60 band is an MCP server for time utilities.
- [UTC second 0-60 band](https://ai-powered.com/mcp/utc-second-0-60-band-2): UTC second 0-60 band is an MCP server for time utilities.
- [UTC offset hours](https://ai-powered.com/mcp/utc-offset-hours): UTC offset hours is an MCP server for developer tools.
- [Seconds to minutes](https://ai-powered.com/mcp/seconds-to-minutes): Seconds to minutes is an MCP server for time utilities.
- [UTC quarter](https://ai-powered.com/mcp/utc-quarter): UTC quarter is an MCP server for time utilities.
- [Whether UTC second can be 60](https://ai-powered.com/mcp/whether-utc-second-can-be-60): Whether UTC second can be 60 is an MCP server for time utilities.
- [UTC year](https://ai-powered.com/mcp/utc-year): UTC year is an MCP server for developer tools.
- [Etc/UTC clock](https://ai-powered.com/mcp/etc-utc-clock): Etc/UTC clock is an MCP server for time utilities.

---
Source: https://ai-powered.com/mcp/utc-second
