ISO Week Number MCP server
ISO 8601 week numbers: date to week, week to date, weeks-per-year.
Little public usage data yet
Reviews
Write oneNobody has reviewed ISO Week Number yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
ISO Week Number tools (1, 1 write)
write = sends, deletes, buys or postsrunwrite actionFreeConverts 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.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1360ms20/20
- Tool poisoning1 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancerepository not readable: repo not found3/15
- Maintainer identityverified namespace with website, no repo4/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
Install directly
claude mcp add --transport http iso-week https://iso-week.gumballtools.com/api/mcp
ISO Week Number: common questions
- Is ISO Week Number MCP server safe?
- With care: it is graded C, so read the findings first (60/100). Read the ISO Week Number safety report
- How do I install ISO Week Number?
- It runs remotely at iso-week.gumballtools.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does ISO Week Number need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is ISO Week Number maintained?
- The latest release is v0.1.0.
- Is ISO Week Number up?
- 100% of our last 6 checks got an answer. We check remote servers about four times a day.