io.github.skypier-jp-works/mcp-jp-paid-leave
NPM · MCP-JP-PAID-LEAVE · SCANNED OCT 1
MCP server for Japanese statutory annual paid leave (nenkyu) calculations.
Available components
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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 63 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2938 tokens (~419/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the io.github.skypier-jp-works/mcp-jp-paid-leave server?
io.github.skypier-jp-works/mcp-jp-paid-leave runs locally as an npm package, launched with npx -y mcp-jp-paid-leave. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-jp-paid-leave
claude mcp add skypier-jp-works-mcp-jp-paid-leave -- npx -y mcp-jp-paid-leave
{
"mcpServers": {
"skypier-jp-works-mcp-jp-paid-leave": {
"command": "npx",
"args": [
"-y",
"mcp-jp-paid-leave"
]
}
}
} {
"servers": {
"skypier-jp-works-mcp-jp-paid-leave": {
"command": "npx",
"args": [
"-y",
"mcp-jp-paid-leave"
]
}
}
} codex mcp add skypier-jp-works-mcp-jp-paid-leave -- npx -y mcp-jp-paid-leave
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"skypier-jp-works-mcp-jp-paid-leave": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-jp-paid-leave"
],
"enabled": true
}
}
} openclaw mcp add skypier-jp-works-mcp-jp-paid-leave --command npx --arg -y --arg mcp-jp-paid-leave
mcp_servers:
skypier-jp-works-mcp-jp-paid-leave:
command: "npx"
args: ["-y", "mcp-jp-paid-leave"] {
"McpServers": {
"skypier-jp-works-mcp-jp-paid-leave": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-jp-paid-leave"
]
}
}
} assistant mcp add skypier-jp-works-mcp-jp-paid-leave -t stdio -c npx -a -y mcp-jp-paid-leave
{
"mcpServers": {
"skypier-jp-works-mcp-jp-paid-leave": {
"command": "npx",
"args": [
"-y",
"mcp-jp-paid-leave"
]
}
}
} 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.
- 1 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 1 Oct 2026 · Analysed npm/mcp-jp-paid-leave@1.0.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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
apply_company_policy 自社規程の上乗せを適用 ~134
法定最低基準の日数に、自社規程による上乗せ設定を適用します。自社規程が法定を下回る場合は、法定最低基準に補正した上で警告を返します(労働基準法第13条)。
| Name | Type | Req | Description |
|---|---|---|---|
| companyPolicyDays | number | – | 自社規程で定めている日数(省略時は法定最低基準をそのまま返す) |
| legalMinimumDays | number | yes | 他のツールで計算した法定最低基準の日数 |
No output schema declared.
No examples provided.
calculate_carryover 繰越・時効消滅日数の計算 ~188
複数回の付与記録と取得記録から、時効2年(労働基準法第115条)による消滅日数と、基準日時点の残日数を計算します。取得は古い付与分から順に消化するものとして計算します。
| Name | Type | Req | Description |
|---|---|---|---|
| asOfDate | string | yes | 基準日(この日時点の残日数・消滅日数を計算する) (YYYY-MM-DD形式、例: 2026-08-15) |
| grants | array | yes | 付与記録の配列(複数年分をまとめて渡せる) |
| usageRecords | array | – | 年次有給休暇を取得した記録の配列(省略時は消化なしとして計算) |
No output schema declared.
No examples provided.
calculate_entitlement 年次有給休暇の付与日・付与日数を計算 ~572
入社日と算定基準日方式(原則の個別付与/斉一的取扱い)から、指定した回(第何回目)の年次有給休暇の付与日と付与日数(法定最低基準)を計算します。斉一的取扱いでは前倒しの連鎖を計算し、前倒しにより短縮された期間も返します。検証済み下限日(2001-04-01)はその回の基準日(算定基準日)にかかるものであり、入社日自体が古くても、指定した回の基準日が下限以降であればエラーにはなりません。
| Name | Type | Req | Description |
|---|---|---|---|
| annualScheduledDays | number | – | 1年間の所定労働日数(週所定労働日数が不定の場合に指定。指定するとweeklyScheduledDaysより優先される) |
| grantNumber | integer | yes | 付与回数(第何回目の付与か)。1=第1回(雇入れ後6ヶ月時点), 2=第2回(1年6ヶ月時点)... 7以降は第7回以降(6年6ヶ月以上)としてすべて同じ日数上限になる |
| hireDate | string | yes | 入社日 (YYYY-MM-DD形式、例: 2026-08-15) |
| referenceDateMethod | string | – | 基準日の算定方式。"individual"=原則どおり労働者ごとに個別付与(省略時のデフォルト)。"uniform"=斉一的取扱い(全労働者共通の基準日に統一して前倒し付与) |
| uniformBasisMonthDays | array | – | 斉一的取扱い(uniform)で使う、会社共通の基準日候補("MM-DD"形式の配列。例: ["04-01"] や ["04-01","10-01"])。referenceDateMethodが"uniform"の場合は必須 |
| weeklyScheduledDays | integer | – | 週所定労働日数(比例付与を計算したい場合に指定。1〜4日で比例付与対象、5日以上は通常の労働者扱い) |
| weeklyScheduledHours | number | – | 週所定労働時間(任意。30時間以上の場合は比例付与の対象外であることの検証に使う) |
No output schema declared.
No examples provided.
check_attendance_rate 出勤率8割の判定 ~976
年次有給休暇の付与要件である出勤率8割を満たすか判定します。呼び出し側は「分子に加算すべきか」「分母から除外すべきか」を判断する必要はありません。算定期間中の日数を種類別にそのまま渡してください。分類(分子への算入・分母からの除外・全労働日への不算入・通常欠勤のいずれに当たるか)は、労働基準法第39条第10項および平成25年7月10日基発0710第3号に基づき、このツール内部で行います。すべての日数は必須です(該当がなければ0を指定してください。省略や推測による補完はできません)。scheduledWorkingDaysは、workedOnScheduledDayOffDaysを除く他の9つの日数区分の合計と一致している必要があり、一致しない場合はエラーになります。判定結果には、各区分をどう分類したか(分母・分子への算入方法と根拠条文)を示す内訳を必ず含めます。
| Name | Type | Req | Description |
|---|---|---|---|
| actualWorkedDays | number | yes | 実出勤日数。実際に出勤して労働した日数(年次有給休暇取得日・各種休業日は含まない) |
| asOfDate | string | – | この判定の対象期間の終了日等(任意)。データ陳腐化の警告判定にのみ使用する (YYYY-MM-DD形式、例: 2026-08-15) |
| childcareOrFamilyCareLeaveDays | number | yes | 育児休業・介護休業等育児又は家族介護を行う労働者の福祉に関する法律に規定する育児休業又は介護休業をした日数 |
| employerCausedSuspensionDays | number | yes | 使用者の責に帰すべき事由による休業日数(使用者側の経営上・管理上の障害による休業を含む。例: 発注元の都合による事業場閉鎖、資材不足による休業) |
| forceMajeureSuspensionDays | number | yes | 天災事変等、不可抗力による休業日数 |
| lawfulLaborDisputeDays | number | yes | 正当な同盟罷業その他正当な争議行為により労務の提供が全くなされなかった日数 |
| maternityLeaveDays | number | yes | 産前産後休業(労働基準法第65条)により休業した日数 |
| otherAbsenceDays | number | yes | 上記のいずれにも該当しない、通常の欠勤日数(無断欠勤、私傷病による欠勤、遅刻・早退による全休扱いなど)。分母には含むが分子には算入しない |
| paidLeaveTakenDays | number | yes | 年次有給休暇を取得した日数 |
| scheduledWorkingDays | number | yes | 所定労働日数の合計(算定期間中に労働義務があった日数)。所定休日は含まない。下記の actualWorkedDays + paidLeaveTakenDays + workInjuryOrIllnessLeaveDays + maternityLeaveDays + childcareOrFamilyCareLeaveDays + employerCausedSuspensionDays + l… |
| workInjuryOrIllnessLeaveDays | number | yes | 業務上の負傷又は疾病により療養のため休業した日数(私傷病による欠勤は含まない。私傷病はotherAbsenceDaysに含める) |
| workedOnScheduledDayOffDays | number | yes | 所定休日(もともと労働義務のない日、例: 会社カレンダー上の休日)に労働させた日数。この日数はscheduledWorkingDaysには含めない(そもそも所定労働日ではないため) |
No output schema declared.
No examples provided.
check_mandatory_five_days 年5日取得義務の充足判定 ~266
年10日以上の年次有給休暇が付与される労働者を対象とする、年5日取得義務(労働基準法第39条第7項・第8項)の対象者判定と、充足状況・残り必要日数を返します。
| Name | Type | Req | Description |
|---|---|---|---|
| asOfDate | string | – | 判定基準日(任意。省略可) (YYYY-MM-DD形式、例: 2026-08-15) |
| employeeRequestedDays | number | – | 労働者自らの請求・取得により取得した日数(5日から控除できる) |
| employerDesignatedDays | number | – | 使用者が既に時季指定して取得させた日数 |
| grantDate | string | yes | 付与日(基準日) (YYYY-MM-DD形式、例: 2026-08-15) |
| grantedDays | number | yes | その基準日に付与された年次有給休暇の日数 |
| plannedGrantDays | number | – | 計画年休制度により取得させた日数(5日から控除できる) |
No output schema declared.
No examples provided.
list_grant_schedule 付与予定の一覧化 ~464
入社日から指定した回数(年数)分の年次有給休暇の付与予定(付与日・付与日数)を一覧で返します。入社が古く、一部の回の基準日が検証済み下限日(2001-04-01)より前になる場合でも呼び出し全体はエラーにならず、該当の回だけ supported:false としてマークされ、それ以外の回は通常どおり計算されます。
| Name | Type | Req | Description |
|---|---|---|---|
| annualScheduledDays | number | – | 1年間の所定労働日数(週所定労働日数が不定の場合に指定。指定するとweeklyScheduledDaysより優先される) |
| hireDate | string | yes | 入社日 (YYYY-MM-DD形式、例: 2026-08-15) |
| numberOfYears | integer | yes | 一覧化する付与回数(何回分/何年分) |
| referenceDateMethod | string | – | 基準日の算定方式。"individual"=原則どおり労働者ごとに個別付与(省略時のデフォルト)。"uniform"=斉一的取扱い(全労働者共通の基準日に統一して前倒し付与) |
| uniformBasisMonthDays | array | – | 斉一的取扱い(uniform)で使う、会社共通の基準日候補("MM-DD"形式の配列。例: ["04-01"] や ["04-01","10-01"])。referenceDateMethodが"uniform"の場合は必須 |
| weeklyScheduledDays | integer | – | 週所定労働日数(比例付与を計算したい場合に指定。1〜4日で比例付与対象、5日以上は通常の労働者扱い) |
| weeklyScheduledHours | number | – | 週所定労働時間(任意。30時間以上の場合は比例付与の対象外であることの検証に使う) |
No output schema declared.
No examples provided.
proportional_entitlement 比例付与日数の計算 ~338
週所定労働日数(または年間所定労働日数)から、パート・アルバイト等への年次有給休暇の比例付与日数(法定最低基準)を計算します。
| Name | Type | Req | Description |
|---|---|---|---|
| annualScheduledDays | number | – | 1年間の所定労働日数(週所定労働日数が不定の場合に指定。指定するとweeklyScheduledDaysより優先される) |
| asOfDate | string | – | 比例付与表のどの世代を使うか判定する対象日(任意、省略時は現在日) (YYYY-MM-DD形式、例: 2026-08-15) |
| grantNumber | integer | yes | 付与回数(第何回目の付与か)。1=第1回(雇入れ後6ヶ月時点), 2=第2回(1年6ヶ月時点)... 7以降は第7回以降(6年6ヶ月以上)としてすべて同じ日数上限になる |
| weeklyScheduledDays | integer | – | 週所定労働日数(比例付与を計算したい場合に指定。1〜4日で比例付与対象、5日以上は通常の労働者扱い) |
| weeklyScheduledHours | number | – | 週所定労働時間(任意。30時間以上の場合は比例付与の対象外であることの検証に使う) |
No output schema declared.
No examples provided.
What is the io.github.skypier-jp-works/mcp-jp-paid-leave server?
io.github.skypier-jp-works/mcp-jp-paid-leave is listed in the public MCP registry as io.github.skypier-jp-works/mcp-jp-paid-leave. MCP server for Japanese statutory annual paid leave (nenkyu) calculations. This page covers its npm package (mcp-jp-paid-leave).
Is the io.github.skypier-jp-works/mcp-jp-paid-leave server safe to use?
io.github.skypier-jp-works/mcp-jp-paid-leave scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 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.skypier-jp-works/mcp-jp-paid-leave server expose?
io.github.skypier-jp-works/mcp-jp-paid-leave exposes 7 tools: calculate_entitlement, check_attendance_rate, list_grant_schedule, proportional_entitlement, calculate_carryover, and 2 more. Their descriptions and schemas cost roughly 2,938 tokens of context every time the server is loaded.
Is the io.github.skypier-jp-works/mcp-jp-paid-leave server still maintained?
io.github.skypier-jp-works/mcp-jp-paid-leave is still listed as active in the MCP registry. We last reached this channel on 1 October 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.skypier-jp-works/mcp-jp-paid-leave server under?
io.github.skypier-jp-works/mcp-jp-paid-leave declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.