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

Annual leave loading calculator plus its published inputs, tables and enquiry fields.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/leavecalc`
- 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 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 265 tokens (~66/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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/leavecalc MCP server?

io.github.CloudCorpRecords/leavecalc runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/leavecalc: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-leavecalc -- docker run --rm -i ghcr.io/cloudcorprecords/leavecalc:0.1.0 mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### Hermes

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

### Netclaw

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

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-leavecalc": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/leavecalc: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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 41)

First indexed and scored.

## MCP tools (4)

### `calculator_describe` (~35 tokens)

What Annual leave loading calculator computes

The inputs this calculator takes (with units, ranges and defaults), the outputs it returns, and the assumptions and tables behind it.

### `calculate` (~113 tokens)

Annual leave loading calculator

Run the Annual leave loading calculator calculator: Base weekly pay; Base pay for the leave period; Leave loading; Penalties you would have earned. Missing inputs fall back to their documented defaults.

Input parameters:

- `hourlyRate` (number): Base hourly rate
- `hoursPerWeek` (number): Ordinary hours per week
- `leaveWeeks` (number): Weeks of annual leave being paid
- `loadingPct` (number): Leave loading in your award or agreement
- `penaltyPct` (number): Weekend or shift penalties you normally get

### `enquiry_describe` (~69 tokens)

What you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)

Read first. States plainly what submit_enquiry does on Leave Loading Calculator: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.

### `enquiry_fields` (~48 tokens)

The questions the enquiry asks

Every field of the Leave Loading Calculator enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

## Diagnostics

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

## Score history

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

## Common questions

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

io.github.CloudCorpRecords/leavecalc is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/leavecalc. Annual leave loading calculator plus its published inputs, tables and enquiry fields. This page covers its container image (ghcr.io/cloudcorprecords/leavecalc).

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

io.github.CloudCorpRecords/leavecalc 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/leavecalc MCP server expose?

io.github.CloudCorpRecords/leavecalc exposes 4 tools: calculator_describe, calculate, enquiry_describe, enquiry_fields. Their descriptions and schemas cost roughly 265 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/leavecalc 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/leavecalc MCP server under?

io.github.CloudCorpRecords/leavecalc 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/leavecalc MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/leavecalc, 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/leavecalc: 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/leavecalc
- Repository: https://github.com/CloudCorpRecords/leavecalc
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-leavecalc/ghcr-io-cloudcorprecords-leavecalc.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-leavecalc/ghcr-io-cloudcorprecords-leavecalc/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-leavecalc/ghcr-io-cloudcorprecords-leavecalc.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-leavecalc/ghcr-io-cloudcorprecords-leavecalc
