ISO Week Number MCP Server

by gumballtools Your server? Claim it

not responding

ISO Week Number is listed as active in the registry but did not answer our last check. It exposes 1 tools.

ISO 8601 week numbers: date to week, week to date, weeks-per-year.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 4 days of history · worst day 11%

4 days agonow

8.6%

Uptime 24h

8 of 93 checks

Tools

read from the server

963 ms

Response time

average over 24h

open, no key

Access

streamable-http

ISO Week Number does not always answer

Over the last week it answered 66.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add iso-week --transport http https://iso-week.gumballtools.com/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "iso-week": {
      "url": "https://iso-week.gumballtools.com/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.iso-week]
url = "https://iso-week.gumballtools.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "iso-week": {
      "url": "https://iso-week.gumballtools.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "iso-week": {
      "url": "https://iso-week.gumballtools.com/api/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

run

run

Converts between calendar dates and ISO 8601 week numbers, in either direction, and reports how many weeks an ISO year has. Use this whenever a date needs to be expressed as a week number, or a week number needs to be turned back into a date — sprint planning, report periods, "week 37" style scheduling, or reconciling two systems that disagree about what week it is. DO NOT compute this yourself with day-of-year divided by 7. ISO 8601 week 1 is defined as the week (Monday-Sunday) containing the year's first Thursday, not the week containing January 1st. This has two consequences that are easy to get wrong from memory: late-December dates can belong to ISO week 1 of the NEXT calendar year, and early-January dates can belong to ISO week 52 or 53 of the PREVIOUS calendar year. A year has 53 ISO weeks (not the usual 52) exactly when January 1 is a Thursday, or the year is a leap year and January 1 is a Wednesday — a rule nobody carries around, and getting it wrong produces a plausible-looking but incorrect week number with no visible sign of the error. Input is a single string, and the shape of the string picks the operation: "2027-01-01" a calendar date (YYYY-MM-DD) -> returns its ISO year, week, and weekday "2026-W53" an ISO week, no weekday given -> returns the Monday of that week "2026-W53-5" an ISO week and weekday (1-7, Mon-Sun) -> returns that exact date "2026" a bare 4-digit year -> returns whether it has 52 or 53 ISO weeks Refuses rather than guesses: slash-separated dates like "03/04/2025" are rejected as ambiguous (month/day vs day/month), two-digit years are rejected as a guess, invalid calendar dates (Feb 30) are rejected, and a week number beyond what that ISO year actually has (e.g. week 53 of a 52-week year) is rejected and told how many weeks that year has.

Endpoints

URL	Transport	State	Latency	Checked
https://iso-week.gumballtools.com/api/mcp	streamable-http	answering	172 ms	3 min ago

Alternatives to ISO Week Number

same job, measured the same way

ISO week number

UTC ISO week number

ISO week-year

UTC ISO week-date

UTC ISO week-date shape

by sadri-dridi

UTC ISO week-date shape

Unix week number

Unix year number

ISO 8601 datetime shape

by sadri-dridi

ISO 8601 datetime shape

30 tools answering

ISO Week Number — questions

Answers built from our own checks of this server.

What can ISO Week Number do?

It exposes 1 tools, read directly from the server on our last check. Among them: run. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is ISO Week Number working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 8 of 93 checks got a reply (8.6%), average response time 963 ms. The bar chart above shows every period we have measured.

Is ISO Week Number still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists ISO Week Number as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect ISO Week Number?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does ISO Week Number need an API key?

No. ISO Week Number completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is ISO Week Number?

It answers our handshake in 963 ms on average, which is faster than 10% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.