Skip to content
MCP server

Leap year check

Hosted MCP server that tells whether a given year is a leap year

Install
Platforms
API
Runs
Remotely
Version
1.0.0
Listing updated
today

Similar MCP servers

About Leap year check

Leap year check is an MCP server for time utilities. It runs as a hosted remote server, so there is nothing to install locally.

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.

Install

Run in a terminal

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

Add to Settings → Connectors → Add custom connector

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/leap-year/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "leap-year": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/leap-year/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

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

Add to ~/.codeium/windsurf/mcp_config.json

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

Add to your client's MCP settings (most use this shape)

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

Using several servers? Build one config file with the MCP config generator.

What it does

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

Leap year check 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.

How AIPoweredBot checks servers