Whether UTC second can be 60
Reports whether the current UTC second is a leap second, for AI clients over MCP
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Whether UTC second can be 60
Whether UTC second can be 60 is an MCP server for time utilities. It runs as a hosted remote server, so there is nothing to install locally.
Time arithmetic code often assumes every minute has 60 seconds, which breaks when the UTC timescale inserts an extra second. This server answers one narrow question: whether a leap second applies at the UTC moment being checked. It is exposed as a remote endpoint that MCP-compatible clients can call over streamable HTTP.
The server is one entry in a set of small, single-purpose MCP utilities published under the same GitHub account. The README describes each as a separate registry name with its own endpoint, so this one is meant to be connected on its own rather than bundled with the others. The repository does not state a licence or pricing for the hosted endpoint.
Install
Run in a terminal
claude mcp add --transport http sec-leap https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/sec-leap/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/sec-leap/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"sec-leap": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/sec-leap/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"sec-leap": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/sec-leap/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"sec-leap": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/sec-leap/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"sec-leap": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/sec-leap/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Leap second check
- Tells a client whether a UTC second can be 60 at the moment it is asked.
- Remote MCP endpoint
- Served over streamable HTTP at a public URL, so no local install is needed.
- Narrow scope
- Covers only the leap-second question rather than general date and time conversion.
Good for
- Checking timestamps in logs or audit trails for a possible 23:59:60 event
- Validating time-handling logic in agent workflows that rely on UTC
- Adding leap-second awareness to scheduling or data pipelines
Whether UTC second can be 60 FAQ
How do I connect to it?
The registry entry lists a single remote endpoint using the streamable-http transport, so any MCP client that supports that transport can connect to it.
How do I add Whether UTC second can be 60 to Claude Code?
Run this command in your terminal: claude mcp add --transport http sec-leap https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/sec-leap/mcp
What are the best alternatives to Whether UTC second can be 60?
The closest alternatives to Whether UTC second can be 60 are UTC second, UTC second 0-60 band, UTC second 0-60 band, UTC start of the current quarter and Etc/UTC clock.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.