Repository avatar
Other Tools
v0.1.0
active

dayrule

io.github.CloudCorpRecords/dayrule

NZ working-day math with the law section cited, holidays, and IRD, NZ bank and ABN checks.

Documentation

dayrule

dayrule is a small local bridge to the hosted itsmyship agent-tools MCP server, which answers questions about New Zealand working days and checks a few Australasian identifiers by checksum. Working days in New Zealand are not defined the same way in every statute, so the day tools work under a named rule: each answer reports the date or count together with the section of law that definition comes from and, for additions, the holidays that were skipped.

The bridge computes nothing itself. It answers the tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning whatever comes back untouched. All seven tools are read-only utilities over values the caller supplies — there is no account lookup, no payment, and nothing that sends anything anywhere.

Tools

  • add_working_days — move a date forward or back by a number of working days under a named rule. Required: rule, start_date, days. Optional: region and jurisdiction (default NZ). The start date itself is not counted. Returns the resulting date, the section cited, and the holidays skipped.
  • count_working_days — count the working days after a start date up to and including an end date under a named rule. Required: rule, from_date, to_date. Optional: region and jurisdiction (default NZ).
  • list_rules — read the catalogue of working-day rules, each with its section reference, text, and version. Takes no required arguments; optional jurisdiction defaults to NZ. Note the captured schema for this tool carries no required key at all, and that is how it is served here.
  • nz_holidays — New Zealand public holidays for a year from 2020 to 2030, with actual and observed dates plus provincial anniversary days. Required: year. Optional: region (for example wellington) and jurisdiction (default NZ).
  • validate_ird — check the check digit of an NZ IRD number a caller supplies. Required: number. Optional: jurisdiction (default NZ). Described upstream as free. Checksum only.
  • validate_nz_bank — check an NZ bank account number a caller supplies using the Inland Revenue algorithm. Required: account. Optional: jurisdiction (default NZ). Described upstream as free. Checksum only; the branch is not verified against the Payments NZ register.
  • validate_abn — check the checksum of an Australian Business Number a caller supplies using the ABR algorithm. Required: abn. Optional: jurisdiction (default AU). Described upstream as free.

Configuration

  • ITSMYSHIP_MCP_URL (optional) — override the upstream endpoint. Defaults to https://itsmyship.com/agent-tools/mcp. (The override hook is this rebuild's own labelled reconstruction.)
  • ITSMYSHIP_API_KEY (optional) — when set, every upstream request carries an Authorization: Bearer <key> header. When it is not set, no key header is sent. (The header name is pinned by the original's registry record; the record pins no package env name, so the Bearer form and forwarding the key from this env var are labelled reconstructions — the original surface was captured keyless.)

Forwarding mechanics

On the first tool call the client opens a streamable HTTP session upstream: a JSON-RPC initialize request (protocolVersion 2025-03-26, clientInfo name dayrule), then a notifications/initialized notification, then the tools/call request carrying the caller's arguments unchanged. When the upstream answers initialize with an Mcp-Session-Id header, that value rides on every later request of the session, which is reused for the life of the process. Replies may arrive as plain JSON or as server-sent events; both are read.

Successful upstream results pass through verbatim, including any isError flag the upstream sets. Failures — a JSON-RPC error, a non-2xx status, an unreadable response, or a request that cannot be completed — come back as an isError result whose text starts with dayrule error: (this rendering is this rebuild's own labelled reconstruction).

CLI

Each tool is also a subcommand taking one JSON argument string:

npx @reneturcios/dayrule add_working_days '{"rule":"holidays-act","start_date":"2026-12-24","days":5}'
npx @reneturcios/dayrule count_working_days '{"rule":"holidays-act","from_date":"2026-12-24","to_date":"2027-01-06"}'
npx @reneturcios/dayrule list_rules '{}'
npx @reneturcios/dayrule nz_holidays '{"year":2027}'
npx @reneturcios/dayrule validate_ird '{"number":"123456785"}'
npx @reneturcios/dayrule validate_nz_bank '{"account":"01-1234-0123456-00"}'
npx @reneturcios/dayrule validate_abn '{"abn":"51824753556"}'
npx @reneturcios/dayrule --version

Exit codes: 0 on success, 1 on an isError result, 2 on a usage error.

MCP server

npx -y @reneturcios/dayrule mcp

MCP client config:

{
  "mcpServers": {
    "dayrule": {
      "command": "npx",
      "args": ["-y", "@reneturcios/dayrule", "mcp"]
    }
  }
}

Docker

docker run -i ghcr.io/cloudcorprecords/dayrule
docker run --rm ghcr.io/cloudcorprecords/dayrule --version

The container's default command is mcp, so the first form is a stdio MCP server; any other arguments reach the CLI normally.

Development

npm install
npm run build
npm test
npm run dev

The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.

License

MIT — see LICENSE.

NPM
@reneturcios/dayrule
Install Command
npm install @reneturcios/dayrule
Runtime: npx
OCI
ghcr.io/cloudcorprecords/dayrule:0.1.0
Install Command
docker pull ghcr.io/cloudcorprecords/dayrule:0.1.0:undefined
Runtime: docker