Julian leap-year check from UTC
Remote MCP server that checks whether the current UTC year is a Julian leap year
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Julian leap-year check from UTC
Julian leap-year check from UTC is an MCP server for time utilities. It runs as a hosted remote server, so there is nothing to install locally.
This is a single-purpose remote MCP server that answers one narrow calendar question: whether a year, derived from UTC, counts as a leap year under the Julian calendar rules. It is exposed over streamable HTTP, so an MCP client connects to a hosted URL and nothing needs to be installed locally.
It is one entry in a collection of small, independently registered utility servers published from the same repository. Sibling servers cover other calendar and identifier checks such as Hebrew, Islamic, Persian and Indian leap years, ISO week dates and ID-format layouts. The repository describes them as aimed at autonomous clients.
The registry entry lists no tool names or input schema, so the exact call signature is not documented. The repository notes that the same author also runs a set of advertising-related intake servers alongside these utilities.
Install
Run in a terminal
claude mcp add --transport http julian-leap https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/julian-leap/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/julian-leap/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"julian-leap": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/julian-leap/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"julian-leap": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/julian-leap/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"julian-leap": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/julian-leap/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"julian-leap": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/julian-leap/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Julian leap-year check
- Reports whether a year is a leap year under Julian calendar rules, based on UTC.
- Remote streamable HTTP
- Runs as a hosted endpoint, so clients connect by URL with no local package.
- Single-purpose design
- Each server in the collection does one narrow check, keeping the surface small for agents.
- Registry-listed name
- Published in the official MCP registry as io.github.sadri-dridi/julian-leap.
Good for
- Let an agent verify Julian calendar leap-year status in a date-conversion workflow
- Test an MCP client against a minimal remote streamable-HTTP server
- Cross-check historical date calculations that use the Julian calendar
Julian leap-year check from UTC FAQ
How do I connect to it?
Use the remote streamable-HTTP URL from the registry entry: https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/julian-leap/mcp.
Do I need to install anything?
No. The registry lists no packages, only a hosted remote endpoint.
What is its registry name?
io.github.sadri-dridi/julian-leap.
Are there related servers?
Yes. The same repository lists similar single-check servers for Hebrew, Islamic, Persian and Indian leap years, ISO week dates and other formats.
How do I add Julian leap-year check from UTC to Claude Code?
Run this command in your terminal: claude mcp add --transport http julian-leap https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/julian-leap/mcp
What are the best alternatives to Julian leap-year check from UTC?
The closest alternatives to Julian leap-year check from UTC are Whether current UTC year has Feb 29, Leap year check, UTC leap-year flag, Gregorian leap-year band and Julian day number.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.