# Whether current UTC year has Feb 29

> Whether current UTC year has Feb 29 is an MCP server for time utilities. Remote MCP utility that reports if the current UTC year is a leap year. 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-day
- **Categories:** [time utilities](https://ai-powered.com/categories/time-utilities)
- **Listing updated:** 2026-11-18

## About

This server answers one narrow question for autonomous clients: does the current UTC year contain February 29? It runs as a hosted endpoint, so nothing needs to be installed locally.

It is one entry in a repository of small, single-purpose MCP utilities published under separate registry names, each with its own endpoint. Siblings cover other calendar and identifier checks such as Julian, Hebrew, Islamic and Persian leap years. The leap-day server connects over streamable HTTP.

It suits agents that need a quick calendar fact without computing it themselves. The README does not document the exact tool names or response format.

## Features

- **Leap-year check:** Reports whether the current UTC year includes February 29.
- **Hosted remote endpoint:** Served from a remote URL over streamable HTTP, with no package to install.
- **Single-purpose design:** Does one narrow job, keeping it simple for agents to call.
- **Part of a utility set:** Sits alongside other small calendar and identifier-check MCP servers from the same author.

## Good for

- Letting an agent check for a leap day before scheduling date-based tasks
- Testing MCP client connectivity against a minimal remote server
- Adding a simple calendar fact lookup to an autonomous workflow

## Install

### Claude Code (Terminal)

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

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

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

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

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

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

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

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

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

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

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

## FAQ

### What does this MCP server do?

It reports whether the current UTC year has a February 29.

### How do I connect to it?

Use the remote streamable-http endpoint listed in the registry entry; there is no package to install.

### Is it the only server in the repository?

No. The repository lists many other small utility servers, each with its own registry name and endpoint.

### How do I add Whether current UTC year has Feb 29 to Claude Code?

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

### What are the best alternatives to Whether current UTC year has Feb 29?

The closest alternatives to Whether current UTC year has Feb 29 are Leap year check, UTC leap-year flag, Whether UTC day can have a leap second, Whether UTC second can be 60 and UTC last 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

- [Leap year check](https://ai-powered.com/mcp/leap-year-check): Leap year check 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.
- [Whether UTC day can have a leap second](https://ai-powered.com/mcp/whether-utc-day-can-have-a-leap-second): Whether UTC day can have a leap second 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 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.
- [Gregorian leap-year band](https://ai-powered.com/mcp/gregorian-leap-year-band): Gregorian leap-year band 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.

---
Source: https://ai-powered.com/mcp/whether-current-utc-year-has-feb-29
