Skip to content
MCP server

UTC end of the current year

Remote MCP utility that reports the UTC end of the current year, for autonomous clients

Install
Platforms
API
Runs
Remotely
Version
1.0.0
Listing updated
today

Similar MCP servers

About UTC end of the current year

UTC end of the current year is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.

This is a single-purpose remote MCP server registered as io.github.sadri-dridi/y-end. Its registry entry describes it only as returning the UTC end of the current year, so it fits a client that needs a year-boundary timestamp without computing it locally.

It is served over streamable HTTP from a hosted endpoint, with no package to install. A client connects to the remote URL listed in the registry. The server belongs to a collection called Named MCP utilities, where each folder maps to one official registry name with its own intake endpoint.

The sibling servers in that collection cover similar small date and format checks, such as ISO week dates and leap-year tests. The README does not list the tools this server exposes or document its inputs and outputs.

Install

Run in a terminal

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

Add to Settings → Connectors → Add custom connector

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

Add to ~/.cursor/mcp.json

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

Add to .vscode/mcp.json

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

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

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

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

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

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

What it does

Year-end UTC value
Provides the UTC end of the current year as described in its registry entry.
Remote streamable HTTP
Runs as a hosted endpoint reached over streamable HTTP, so nothing needs to be installed locally.
Single-purpose design
Each server in the collection maps to one registry name and one narrow function.
Registry listed
Published in the official MCP registry as io.github.sadri-dridi/y-end.

Good for

  • Get a year-end timestamp for an agent's date calculations
  • Check how long remains until the current year closes in UTC
  • Test an MCP client against a minimal remote server
  • Anchor scheduling or reporting logic to the year boundary

UTC end of the current year FAQ

How does a client connect?

Through the remote streamable HTTP endpoint listed in the registry entry; no package is installed.

What does it return?

The registry describes it as the UTC end of the current year. Exact output fields are not documented.

Is it part of a larger project?

Yes, it is one of the Named MCP utilities servers in the sadri-dridi repository, each with its own registry name.

How do I add UTC end of the current year to Claude Code?

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

What are the best alternatives to UTC end of the current year?

The closest alternatives to UTC end of the current year are UTC year, Days in current UTC year, UTC start of the current year, UTC ISO week-date YYYY-Www-D and UTC ISO week-date shape.

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