# Leap year check

> Leap year check is an MCP server for time utilities. Hosted MCP server that tells whether a given 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-year
- **Categories:** [time utilities](https://ai-powered.com/categories/time-utilities)
- **Listing updated:** 2026-11-18

## About

The README describes this as one of a set of small, independently listed MCP servers for autonomous clients, each published under its own registry name. This one answers a single question: whether a year is a leap year under the Gregorian rules. It is reached over streamable HTTP at a remote endpoint, so there is nothing to install locally.

Because the server is a narrow utility, it suits agents that need a deterministic date check as one step in a larger workflow, such as validating a date field or scheduling logic. The README lists sibling servers in the same collection that cover other calendars and calendar-adjacent checks, but it does not list a separate tool set for this one.

The listing does not state pricing, licence terms or any rate limits, so those are left unspecified.

## Features

- **Gregorian leap year check:** Determines whether a given year is a leap year through an MCP tool call.
- **Streamable HTTP transport:** Connects to MCP clients over a remote streamable HTTP endpoint.
- **Registry-listed server:** Published in the official MCP registry under the io.github.sadri-dridi namespace.

## Good for

- Validating year values inside an agent's date-handling workflow
- Checking February 29 eligibility before generating a date
- Adding a calendar utility to an MCP-enabled assistant

## Install

### Claude Code (Terminal)

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

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

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

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

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

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

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

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

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

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

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

## FAQ

### How is this server reached?

The registry entry lists a remote streamable HTTP endpoint, and no local package is provided.

### Is the source code available?

The README points to the named-mcp-utilities repository on GitHub, where the collection's folders are kept.

### How do I add Leap year check to Claude Code?

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

### What are the best alternatives to Leap year check?

The closest alternatives to Leap year check are Whether current UTC year has Feb 29, Gregorian leap-year band, Whether Persian year is leap, UTC leap-year flag and Whether UTC day can have a leap second.

## 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 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.
- [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 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.
- [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.
- [Persian year band](https://ai-powered.com/mcp/persian-year-band): Persian year band is an MCP server for time utilities.
- [Minguo year band](https://ai-powered.com/mcp/minguo-year-band): Minguo year band 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.

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