io.github.skypier-jp-works/mcp-jp-calendar
NPM · MCP-JP-CALENDAR · SCANNED OCT 1
MCP server for Japanese business days, holidays, and fiscal-period 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 64 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1195 tokens (~170/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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
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-calendar server?
io.github.skypier-jp-works/mcp-jp-calendar runs locally as an npm package, launched with npx -y mcp-jp-calendar. 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-calendar
claude mcp add skypier-jp-works-mcp-jp-calendar -- npx -y mcp-jp-calendar
{
"mcpServers": {
"skypier-jp-works-mcp-jp-calendar": {
"command": "npx",
"args": [
"-y",
"mcp-jp-calendar"
]
}
}
} {
"servers": {
"skypier-jp-works-mcp-jp-calendar": {
"command": "npx",
"args": [
"-y",
"mcp-jp-calendar"
]
}
}
} codex mcp add skypier-jp-works-mcp-jp-calendar -- npx -y mcp-jp-calendar
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"skypier-jp-works-mcp-jp-calendar": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-jp-calendar"
],
"enabled": true
}
}
} openclaw mcp add skypier-jp-works-mcp-jp-calendar --command npx --arg -y --arg mcp-jp-calendar
mcp_servers:
skypier-jp-works-mcp-jp-calendar:
command: "npx"
args: ["-y", "mcp-jp-calendar"] {
"McpServers": {
"skypier-jp-works-mcp-jp-calendar": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-jp-calendar"
]
}
}
} assistant mcp add skypier-jp-works-mcp-jp-calendar -t stdio -c npx -a -y mcp-jp-calendar
{
"mcpServers": {
"skypier-jp-works-mcp-jp-calendar": {
"command": "npx",
"args": [
"-y",
"mcp-jp-calendar"
]
}
}
} 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 −3
- Stability: pass → 0.80 functional
- 30 Sept 26 0
- Stability: 0.97 → pass security
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −2
- 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 0
- Stability: 0.97 → pass security
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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-calendar@1.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 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 →
add_business_days N営業日後/前の日付を計算 ~213
指定日から N 営業日後(Nが負の場合はN営業日前)の日付を返します。
| Name | Type | Req | Description |
|---|---|---|---|
| businessDays | integer | yes | 加算する営業日数。負の数を指定するとN営業日前になります |
| customHolidays | array | – | 会社独自の休業日 (YYYY-MM-DD形式の配列)。例: 年末年始 ["2026-12-29","2026-12-30","2026-12-31","2027-01-01","2027-01-02","2027-01-03"] |
| date | string | yes | 日付 (YYYY-MM-DD形式、例: 2026-08-15) |
| weekendDays | array | – | 休みとする曜日の配列 (0=日,1=月,2=火,3=水,4=木,5=金,6=土)。省略時は土日([0,6]) |
No output schema declared.
No examples provided.
count_business_days 営業日数カウント ~194
2つの日付の間(両端を含む)の営業日数を数えます。
| Name | Type | Req | Description |
|---|---|---|---|
| customHolidays | array | – | 会社独自の休業日 (YYYY-MM-DD形式の配列)。例: 年末年始 ["2026-12-29","2026-12-30","2026-12-31","2027-01-01","2027-01-02","2027-01-03"] |
| endDate | – | yes | – |
| startDate | string | yes | 日付 (YYYY-MM-DD形式、例: 2026-08-15) |
| weekendDays | array | – | 休みとする曜日の配列 (0=日,1=月,2=火,3=水,4=木,5=金,6=土)。省略時は土日([0,6]) |
No output schema declared.
No examples provided.
fiscal_period 年度・四半期判定 ~95
指定日が何年度の第何四半期かを返します。年度の開始月は指定可能(省略時は4月)。
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | 日付 (YYYY-MM-DD形式、例: 2026-08-15) |
| fiscalYearStartMonth | integer | – | 年度の開始月 (1〜12)。省略時は4(4月始まり) |
No output schema declared.
No examples provided.
is_business_day 営業日判定 ~208
指定した日が営業日かどうかを判定します。土日・日本の祝日・振替休日・国民の休日・会社独自の休業日を考慮します。
| Name | Type | Req | Description |
|---|---|---|---|
| customHolidays | array | – | 会社独自の休業日 (YYYY-MM-DD形式の配列)。例: 年末年始 ["2026-12-29","2026-12-30","2026-12-31","2027-01-01","2027-01-02","2027-01-03"] |
| date | string | yes | 日付 (YYYY-MM-DD形式、例: 2026-08-15) |
| weekendDays | array | – | 休みとする曜日の配列 (0=日,1=月,2=火,3=水,4=木,5=金,6=土)。省略時は土日([0,6]) |
No output schema declared.
No examples provided.
list_holidays 祝日一覧 ~60
指定年の日本の祝日を一覧で返します。対応期間: 2020年〜2030年。
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | yes | 対象の年 (西暦4桁、例: 2026) |
No output schema declared.
No examples provided.
month_end_info 月末締め日情報 ~194
指定月の月末日と、月末が休日の場合に前倒しした実質的な締め日を返します。
| Name | Type | Req | Description |
|---|---|---|---|
| customHolidays | array | – | 会社独自の休業日 (YYYY-MM-DD形式の配列)。例: 年末年始 ["2026-12-29","2026-12-30","2026-12-31","2027-01-01","2027-01-02","2027-01-03"] |
| weekendDays | array | – | 休みとする曜日の配列 (0=日,1=月,2=火,3=水,4=木,5=金,6=土)。省略時は土日([0,6]) |
| yearMonth | string | yes | 対象の年月 (YYYY-MM形式、例: 2026-08) |
No output schema declared.
No examples provided.
next_gotobi 次の五十日を計算 ~231
指定日以降で最も近い五十日(ごとおび。5日・10日・15日・20日・25日・月末)を返します。その日が休日の場合は、直前の営業日に前倒しした実際の日付も一緒に返します。
| Name | Type | Req | Description |
|---|---|---|---|
| customHolidays | array | – | 会社独自の休業日 (YYYY-MM-DD形式の配列)。例: 年末年始 ["2026-12-29","2026-12-30","2026-12-31","2027-01-01","2027-01-02","2027-01-03"] |
| date | string | yes | 日付 (YYYY-MM-DD形式、例: 2026-08-15) |
| weekendDays | array | – | 休みとする曜日の配列 (0=日,1=月,2=火,3=水,4=木,5=金,6=土)。省略時は土日([0,6]) |
No output schema declared.
No examples provided.
What is the io.github.skypier-jp-works/mcp-jp-calendar server?
io.github.skypier-jp-works/mcp-jp-calendar is listed in the public MCP registry as io.github.skypier-jp-works/mcp-jp-calendar. MCP server for Japanese business days, holidays, and fiscal-period calculations. This page covers its npm package (mcp-jp-calendar).
Is the io.github.skypier-jp-works/mcp-jp-calendar server safe to use?
io.github.skypier-jp-works/mcp-jp-calendar scores 80 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-calendar server expose?
io.github.skypier-jp-works/mcp-jp-calendar exposes 7 tools: is_business_day, add_business_days, count_business_days, next_gotobi, month_end_info, and 2 more. Their descriptions and schemas cost roughly 1,195 tokens of context every time the server is loaded.
Is the io.github.skypier-jp-works/mcp-jp-calendar server still maintained?
io.github.skypier-jp-works/mcp-jp-calendar 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-calendar server under?
io.github.skypier-jp-works/mcp-jp-calendar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.