# UTC leap-year flag

> UTC leap-year flag is an MCP server for time utilities. Remote MCP server that returns a UTC leap-year flag for autonomous 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-year-utc
- **Categories:** [time utilities](https://ai-powered.com/categories/time-utilities)
- **Listing updated:** 2026-11-18

## About

This server is one entry in a collection of small, single-purpose public MCP utilities published under the sadri-dridi registry namespace. Its name is io.github.sadri-dridi/leap-year-utc, and its only stated purpose is to expose a leap-year flag based on UTC.

It is reachable as a remote endpoint over streamable HTTP, served from a Cloudflare Workers host. No installable package is listed, so clients connect to the URL directly rather than running anything locally.

The parent repository describes these servers as aimed at autonomous clients, and says each folder maps to one official registry name with its own intake. It also promotes an advertising service for agents, so treat the collection as a mix of tiny utilities and promotional doors. No tool names or parameters are documented for this particular server.

## Features

- **UTC leap-year flag:** Provides a leap-year indicator based on UTC, as stated in its registry description.
- **Remote streamable HTTP:** Connects over a hosted streamable-HTTP endpoint with no local installation.
- **Single-purpose design:** Each server in the collection covers one narrow check under its own registry name.
- **Registry-listed:** Published in the official MCP registry as io.github.sadri-dridi/leap-year-utc.

## Good for

- Letting an agent check whether the current UTC year is a leap year
- Testing remote MCP client connections against a minimal endpoint
- Adding a trivial date utility to an autonomous workflow

## Install

### Claude Code (Terminal)

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

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

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

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

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

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

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

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

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

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

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

## FAQ

### How do I connect to this server?

Use the streamable-HTTP remote URL from the registry entry; no package is provided for local installation.

### Does it need installation?

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

### Is it part of a larger project?

Yes, it belongs to the named-mcp-utilities repository, a collection of small MCP servers by the same author.

### How do I add UTC leap-year flag to Claude Code?

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

### What are the best alternatives to UTC leap-year flag?

The closest alternatives to UTC leap-year flag are Gregorian leap-year band, Whether current UTC year has Feb 29, UTC minute, UTC second day of the current month and Leap year check.

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

- [Gregorian leap-year band](https://ai-powered.com/mcp/gregorian-leap-year-band): Gregorian leap-year band 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 minute](https://ai-powered.com/mcp/utc-minute): UTC minute 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.
- [Leap year check](https://ai-powered.com/mcp/leap-year-check): Leap year check 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.
- [UTC second](https://ai-powered.com/mcp/utc-second): UTC second is an MCP server for time utilities.
- [UTC milliseconds remainder](https://ai-powered.com/mcp/utc-milliseconds-remainder): UTC milliseconds remainder is an MCP server for time utilities.

---
Source: https://ai-powered.com/mcp/utc-leap-year-flag
