# io.github.CloudCorpRecords/dayrule (oci · ghcr.io/cloudcorprecords/dayrule)

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

- Trust score: 43/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/dayrule`: 72/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-dayrule/reneturcios-dayrule.md), [page](https://verifymcp.io/servers/cloudcorprecords-dayrule/reneturcios-dayrule)
- oci · `ghcr.io/cloudcorprecords/dayrule`: 43/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-dayrule/ghcr-io-cloudcorprecords-dayrule.md), [page](https://verifymcp.io/servers/cloudcorprecords-dayrule/ghcr-io-cloudcorprecords-dayrule)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/dayrule`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 572 tokens (~81/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/dayrule MCP server?

io.github.CloudCorpRecords/dayrule runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/dayrule:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-dayrule -- docker run --rm -i ghcr.io/cloudcorprecords/dayrule:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-dayrule": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dayrule:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-dayrule": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dayrule:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-dayrule -- docker run --rm -i ghcr.io/cloudcorprecords/dayrule:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-dayrule": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dayrule:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-dayrule:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/dayrule:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-dayrule": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dayrule:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-dayrule": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dayrule:0.1.0",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 40)

First indexed and scored.

## MCP tools (7)

### `add_working_days` (~139 tokens)

Add (or subtract) working days under a NZ statute's definition. Returns the date, the section cited and the holidays skipped. The start date is not counted.

Input parameters:

- `days` (integer, required): Number of working days to add; a negative number subtracts.
- `jurisdiction` (string): Jurisdiction whose rules apply (default 'NZ').
- `region`: Optional region, e.g. 'wellington'.
- `rule` (string, required): Working-day rule name, e.g. 'holidays-act' (see list_rules).
- `start_date` (string, required): Date to start from, YYYY-MM-DD. The start date is not counted.

### `count_working_days` (~114 tokens)

Count working days after from_date up to and including to_date under a rule.

Input parameters:

- `from_date` (string, required): Start of the range; working days are counted after this date.
- `jurisdiction` (string): Jurisdiction whose rules apply (default 'NZ').
- `region`: Optional region, e.g. 'wellington'.
- `rule` (string, required): Working-day rule name, e.g. 'holidays-act' (see list_rules).
- `to_date` (string, required): End of the range, inclusive.

### `list_rules` (~39 tokens)

List the working-day rules with their section reference, text and version.

Input parameters:

- `jurisdiction` (string): Jurisdiction whose rules to list (default 'NZ').

### `nz_holidays` (~91 tokens)

NZ public holidays (actual and observed dates) and provincial anniversary days for a year (2020-2030). Optional region, e.g. 'wellington'.

Input parameters:

- `jurisdiction` (string): Jurisdiction (default 'NZ').
- `region`: Optional region for provincial anniversary days, e.g. 'wellington'.
- `year` (integer, required): Year to list holidays for (2020-2030).

### `validate_ird` (~75 tokens)

Free: check an NZ IRD number's check digit (Inland Revenue written steps; IRD's Example 3, 150000026, contradicts those steps and is reported invalid).

Input parameters:

- `jurisdiction` (string): Jurisdiction (default 'NZ').
- `number` (string, required): The NZ IRD number to check.

### `validate_nz_bank` (~64 tokens)

Free: check an NZ bank account number (Inland Revenue algorithm). Checksum only; branch not verified against the Payments NZ register.

Input parameters:

- `account` (string, required): The NZ bank account number to check.
- `jurisdiction` (string): Jurisdiction (default 'NZ').

### `validate_abn` (~50 tokens)

Free: check an Australian Business Number's checksum (ABR algorithm).

Input parameters:

- `abn` (string, required): The Australian Business Number to check.
- `jurisdiction` (string): Jurisdiction (default 'AU').

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-dayrule/ghcr-io-cloudcorprecords-dayrule#diagnostics

## Score history

- 2026-11-21: 43
- 2026-11-20: 42
- 2026-11-19: 42
- 2026-11-18: 41
- 2026-11-17: 41
- 2026-11-16: 40

## Common questions

### What is the io.github.CloudCorpRecords/dayrule MCP server?

io.github.CloudCorpRecords/dayrule is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/dayrule. NZ working-day math with the law section cited, holidays, and IRD, NZ bank and ABN checks. This page covers its container image (ghcr.io/cloudcorprecords/dayrule).

### Is the io.github.CloudCorpRecords/dayrule MCP server safe to use?

io.github.CloudCorpRecords/dayrule scores 43 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.CloudCorpRecords/dayrule MCP server expose?

io.github.CloudCorpRecords/dayrule exposes 7 tools: add_working_days, count_working_days, list_rules, nz_holidays, validate_ird, and 2 more. Their descriptions and schemas cost roughly 572 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/dayrule MCP server still maintained?

io.github.CloudCorpRecords/dayrule is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.CloudCorpRecords/dayrule MCP server under?

io.github.CloudCorpRecords/dayrule declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/dayrule MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/dayrule, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/dayrule: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/dayrule
- Repository: https://github.com/CloudCorpRecords/dayrule
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-dayrule/ghcr-io-cloudcorprecords-dayrule.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-dayrule/ghcr-io-cloudcorprecords-dayrule/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-dayrule/ghcr-io-cloudcorprecords-dayrule.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-dayrule/ghcr-io-cloudcorprecords-dayrule
