Jp Paid Leave MCP server
MCP server for Japanese statutory annual paid leave (nenkyu) calculations.
0 stars21 downloads/wk
Reviews
Write oneNobody has reviewed Jp Paid Leave yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Jp Paid Leave tools (7)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
apply_company_policy法定最低基準の日数に、自社規程による上乗せ設定を適用します。自社規程が法定を下回る場合は、法定最低基準に補正した上で警告を返します(労働基準法第13条)。
calculate_carryover複数回の付与記録と取得記録から、時効2年(労働基準法第115条)による消滅日数と、基準日時点の残日数を計算します。取得は古い付与分から順に消化するものとして計算します。
calculate_entitlement入社日と算定基準日方式(原則の個別付与/斉一的取扱い)から、指定した回(第何回目)の年次有給休暇の付与日と付与日数(法定最低基準)を計算します。斉一的取扱いでは前倒しの連鎖を計算し、前倒しにより短縮された期間も返します。検証済み下限日(2001-04-01)はその回の基準日(算定基準日)にかかるものであり、入社日自体が古くても、指定した回の基準日が下限以降であればエラーにはなりません。
check_attendance_rate年次有給休暇の付与要件である出勤率8割を満たすか判定します。呼び出し側は「分子に加算すべきか」「分母から除外すべきか」を判断する必要はありません。算定期間中の日数を種類別にそのまま渡してください。分類(分子への算入・分母からの除外・全労働日への不算入・通常欠勤のいずれに当たるか)は、労働基準法第39条第10項および平成25年7月10日基発0710第3号に基づき、このツール内部で行います。すべての日数は必須です(該当がなければ0を指定してください。省略や推測による補完はできません)。scheduledWorkingDaysは、workedOnScheduledDayOffDaysを除く他の9つの日数区分の合計と一致している必要があり、一致しない場合はエラーになります。判定結果には、各区分をどう分類したか(分母・分子への算入方法と根拠条文)を示す内訳を必ず含めます。
check_mandatory_five_days年10日以上の年次有給休暇が付与される労働者を対象とする、年5日取得義務(労働基準法第39条第7項・第8項)の対象者判定と、充足状況・残り必要日数を返します。
list_grant_schedule入社日から指定した回数(年数)分の年次有給休暇の付与予定(付与日・付与日数)を一覧で返します。入社が古く、一部の回の基準日が検証済み下限日(2001-04-01)より前になる場合でも呼び出し全体はエラーにならず、該当の回だけ supported:false としてマークされ、それ以外の回は通常どおり計算されます。
proportional_entitlement週所定労働日数(または年間所定労働日数)から、パート・アルバイト等への年次有給休暇の比例付与日数(法定最低基準)を計算します。
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan7 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 55 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How Jp Paid Leave compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,255 servers
- Tools
- 7
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 21
- more than 8% of 12,191 servers with a package
What its tools let an agent do: 6 read · 1 run or deploy
Install Jp Paid Leave in Claude Code, Cursor or VS Code
Runs npx -y mcp-jp-paid-leave on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-jp-paid-leave -- npx -y mcp-jp-paid-leave
What the publisher says
From the Jp Paid Leave repository's README, as published. We do not edit it. Read it on GitHub
mcp-jp-paid-leave
日本語版 README はこちら
An MCP (Model Context Protocol) server for calculating Japan's statutory annual paid leave ("nenkyu") under the Labor Standards Act: entitlement grants, attendance-rate checks, proportional grants for part-time workers, carryover/prescription, and the 5-day mandatory-use rule. It lets MCP-capable clients such as Claude Desktop invoke these calculations directly.
No network access is used at runtime. All statutory rules are embedded as constants in the code.
Core design principle
argument to applycompanypolicy.
- Every number and judgment this server returns is the statutory minimum under the Labor Standards Act.
- Any company policy that grants more than the statutory minimum must be passed explicitly as an
it to the statutory minimum and returns a warning.
- Every tool response includes a basis field:
- "legal_minimum": the statutory minimum value
- "companypolicyapplied": the value after applying a company policy (only from applycompanypolicy)
- If a company policy value is below the statutory minimum, applycompanypolicy automatically corrects
(such as the standard grant-days table) are stored as "rule generations with an effective date," and the generation valid at the calculation-target date is selected automatically. Calculating for a past period still uses the rules that were in force at that time. Every tool response includes a meta field with the effective date and source URL of each rule actually used, the date the data was last verified (dataVerifiedOn), and a staleness warning when applicable. See Versioning policy and Maintenance policy below.
- Resilience to legal amendments: rules that are known to have changed as of a specific effective date
Disclaimer
is not guaranteed.**
- **This tool computes the statutory minimum under the Labor Standards Act. The accuracy of its output
precedence over this tool's output.
- If your work rules (shugyo kisoku) provide more favorable terms to employees, those always take
always confirm with a qualified professional (e.g., a licensed Shakai Hoken Roumushi / labor and social security attorney).**
- **For any important labor/HR decision (including anything touching discipline, dismissal, or payroll),
Tools (7 total)
1. calculate_entitlement
Give the hire date (hireDate) and which grant occurrence to compute (grantNumber: 1 = the first grant at 6 months of service, 2 = the second grant at 1 year 6 months, etc.).
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Jp Paid Leave: common questions
- Is Jp Paid Leave MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Jp Paid Leave safety report
- How do I install Jp Paid Leave?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Jp Paid Leave need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Jp Paid Leave maintained?
- The last commit was 96 days ago (2026-07-31). The latest release is v1.0.0.
- How does Jp Paid Leave compare with other MCP servers?
- safety score 85/100 (higher than 70% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.