# Whether UTC day can have a leap second

> Whether UTC day can have a leap second is an MCP server for time utilities. Answers whether a UTC day can contain a leap second, for MCP-compatible agents and 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/leap-sec
- **Categories:** [time utilities](https://ai-powered.com/categories/time-utilities)
- **Listing updated:** 2026-11-18

## About

This server answers one narrow calendar question: whether a UTC day can have a leap second. Clients connect to a remote streamable HTTP endpoint, so there is no local package to install. The registry entry lists no installable packages, only the remote URL.

The server is one of several single-purpose utilities published under the same registry namespace. Each covers a single time or identifier rule rather than a general date toolkit, so its scope is limited to the leap-second question. The README describes the collection as independently listed public MCP servers for autonomous clients.

It suits developers and agents that need a yes-or-no answer on UTC leap-second behaviour while writing or testing date logic. The listing does not describe pricing, licence terms or the specific tool names it exposes.

## Features

- **Single-purpose leap-second check:** Returns whether a UTC day can carry a leap second, covering one calendar rule only.
- **Remote streamable HTTP endpoint:** Clients connect by URL using the streamable-http transport, with no local package required.
- **Registry-listed MCP server:** Published in the official MCP registry under the io.github.sadri-dridi namespace.

## Good for

- Check whether a date-handling routine needs to account for a UTC leap second
- Give an agent a verifiable answer to a UTC leap-second question during a multi-step task
- Test time-library assumptions about UTC day length in scheduling or logging code

## Install

### Claude Code (Terminal)

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

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

```sh
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/leap-sec/mcp
```

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

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

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

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

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

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

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

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

## FAQ

### How do I connect to this server?

The registry entry gives a remote streamable-http URL. MCP clients that support that transport can connect to it directly.

### Is there a package to install locally?

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

### How do I add Whether UTC day can have a leap second to Claude Code?

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

### What are the best alternatives to Whether UTC day can have a leap second?

The closest alternatives to Whether UTC day can have a leap second are Whether UTC second can be 60, Whether current UTC year has Feb 29, UTC leap-year flag, Leap year check and UTC second day of the current month.

## 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

- [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.
- [Whether current UTC year has Feb 29](https://ai-powered.com/mcp/whether-current-utc-year-has-feb-29): Whether current UTC year has Feb 29 is an MCP server for time utilities.
- [UTC leap-year flag](https://ai-powered.com/mcp/utc-leap-year-flag): UTC leap-year flag is an MCP server for time utilities.
- [Leap year check](https://ai-powered.com/mcp/leap-year-check): Leap year check is an MCP server for time utilities.
- [UTC second day of the current month](https://ai-powered.com/mcp/utc-second-day-of-the-current-month): UTC second day of the current month is an MCP server for time utilities.
- [UTC second](https://ai-powered.com/mcp/utc-second): UTC second is an MCP server for time utilities.
- [UTC last day of the current month](https://ai-powered.com/mcp/utc-last-day-of-the-current-month): UTC last day of the current month is an MCP server for time utilities.
- [Whether Persian year is leap](https://ai-powered.com/mcp/whether-persian-year-is-leap): Whether Persian year is leap is an MCP server for time utilities.

---
Source: https://ai-powered.com/mcp/whether-utc-day-can-have-a-leap-second
