# UTC ISO week-yearing year

> UTC ISO week-yearing year is an MCP server for time utilities. Remote MCP utility that reports the current ISO week-year in UTC for agents. 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/iso-year
- **Categories:** [time utilities](https://ai-powered.com/categories/time-utilities)
- **Listing updated:** 2026-11-18

## About

This is one of a set of small, single-purpose MCP servers published under the sadri-dridi registry namespace. Each folder in the parent repository maps to one registry name, and this one is named iso-year, with the registry describing it as the UTC ISO week-year.

It runs as a remote endpoint over streamable HTTP, served from a Cloudflare Workers host, so there is nothing to install locally; an MCP client connects directly to the URL. No package is published.

The README and registry entry give only a one-line description and do not document tool names or parameters. Sibling servers in the same repository cover related date and calendar checks, such as the ISO week-date format and the Thursday of the current ISO week. The repository also lists several servers that route agents to an advertising service, so users should check what each endpoint does before connecting.

## Features

- **ISO week-year in UTC:** Targets the ISO week-numbering year based on UTC, as described in the registry entry.
- **Remote streamable HTTP:** Connects over a hosted streamable-HTTP endpoint, with no local package to install.
- **Single-purpose server:** Exposes one narrow utility under its own official registry name.
- **Related date utilities:** Sits alongside sibling servers for ISO week-date, ISO century and week Thursday checks.

## Good for

- Letting an agent look up the current ISO week-year without calculating it itself
- Checking year boundaries around ISO week 1 or week 52/53 in scheduling workflows
- Testing remote MCP client connections to a minimal streamable-HTTP server

## Install

### Claude Code (Terminal)

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

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

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

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

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

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

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

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

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

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

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

## FAQ

### How do I connect to this server?

Point an MCP client at the remote streamable-HTTP URL listed in the registry entry. No local package is provided.

### Which time zone does it use?

The registry description specifies UTC.

### Does it have sibling servers?

Yes. The parent repository lists many similar single-purpose servers, including iso-century, weekdate-ok and iso-week-thu.

### How do I add UTC ISO week-yearing year to Claude Code?

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

### What are the best alternatives to UTC ISO week-yearing year?

The closest alternatives to UTC ISO week-yearing year are ISO year-week YYYY-Www, UTC ISO week-year century, ISO week number, UTC ISO week number and UTC ISO week-date YYYY-Www-D.

## 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

- [ISO year-week YYYY-Www](https://ai-powered.com/mcp/iso-year-week-yyyy-www): ISO year-week YYYY-Www is an MCP server for time utilities.
- [UTC ISO week-year century](https://ai-powered.com/mcp/utc-iso-week-year-century): UTC ISO week-year century is an MCP server for time utilities.
- [ISO week number](https://ai-powered.com/mcp/iso-week-number-2): ISO week number is an MCP server for time utilities.
- [UTC ISO week number](https://ai-powered.com/mcp/utc-iso-week-number): UTC ISO week number is an MCP server for developer tools.
- [UTC ISO week-date YYYY-Www-D](https://ai-powered.com/mcp/utc-iso-week-date-yyyy-www-d): UTC ISO week-date YYYY-Www-D is an MCP server for developer tools.
- [UTC ISO week-date](https://ai-powered.com/mcp/utc-iso-week-date): UTC ISO week-date is an MCP server for time utilities.
- [UTC ISO semester 1-2](https://ai-powered.com/mcp/utc-iso-semester-1-2): UTC ISO semester 1-2 is an MCP server for time utilities.
- [ISO week 01-53 band](https://ai-powered.com/mcp/iso-week-01-53-band): ISO week 01-53 band is an MCP server for time utilities.

---
Source: https://ai-powered.com/mcp/utc-iso-week-yearing-year
