Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/leavecalc

NPM · @RENETURCIOS/LEAVECALC · 2 COMPONENTS

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

70 Trust /100

Last scanned (13 hours ago)

Scores higher than 41% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 265 tokens (~66/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 55

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@reneturcios/leavecalc@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~265 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
calculate ~113

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.

NameTypeReqDescription
hourlyRatenumber–Base hourly rate
hoursPerWeeknumber–Ordinary hours per week
leaveWeeksnumber–Weeks of annual leave being paid
loadingPctnumber–Leave loading in your award or agreement
penaltyPctnumber–Weekend or shift penalties you normally get

No output schema declared.

No examples provided.

calculator_describe ~35

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

enquiry_describe ~69

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

enquiry_fields ~48

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

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

io.github.CloudCorpRecords/leavecalc runs locally as an npm package, launched with npx -y @reneturcios/leavecalc mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/leavecalc

# add to Claude Code
claude mcp add cloudcorprecords-leavecalc -- npx -y @reneturcios/leavecalc mcp
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 npm package (@reneturcios/leavecalc).

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

io.github.CloudCorpRecords/leavecalc scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 15 checks on io.github.CloudCorpRecords/leavecalc, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/leavecalc: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.