PlugRail Japanese Calendar
REMOTE · JP-CALENDAR.PLUGRAIL.DEV · SCANNED SEP 27
Japanese holiday and business-day calculations using official Japan Cabinet Office data.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 986 tokens (~246/item across 4 items; 4 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 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
How do I install the PlugRail Japanese Calendar MCP server?
PlugRail Japanese Calendar is a hosted endpoint at https://jp-calendar.plugrail.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · jp-calendar.plugrail.dev
claude mcp add --transport http dev-plugrail-jp-calendar 'https://jp-calendar.plugrail.dev/mcp'
{
"mcpServers": {
"dev-plugrail-jp-calendar": {
"url": "https://jp-calendar.plugrail.dev/mcp"
}
}
} {
"servers": {
"dev-plugrail-jp-calendar": {
"type": "http",
"url": "https://jp-calendar.plugrail.dev/mcp"
}
}
} [mcp_servers.dev-plugrail-jp-calendar] url = "https://jp-calendar.plugrail.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-plugrail-jp-calendar": {
"type": "remote",
"url": "https://jp-calendar.plugrail.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-plugrail-jp-calendar --url 'https://jp-calendar.plugrail.dev/mcp' --transport streamable-http
mcp_servers:
dev-plugrail-jp-calendar:
url: "https://jp-calendar.plugrail.dev/mcp" {
"McpServers": {
"dev-plugrail-jp-calendar": {
"Transport": "http",
"Url": "https://jp-calendar.plugrail.dev/mcp"
}
}
} assistant mcp add dev-plugrail-jp-calendar -t streamable-http -u 'https://jp-calendar.plugrail.dev/mcp'
{
"mcpServers": {
"dev-plugrail-jp-calendar": {
"type": "http",
"url": "https://jp-calendar.plugrail.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 2 Aug 26 0
- Schema quality: 212 → 246 ▼ functional
- 31 Jul 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 Jul 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
- 26 Jul 26 0
First indexed and scored.
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 27 Sept 2026 · Probed https://jp-calendar.plugrail.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=plugrail.dev | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 87c4b71654b8a9770ec7ceffea691a73 |
| SANs: plugrail.dev, jp-calendar.plugrail.dev, *.jp-calendar.plugrail.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jp-calendar.plugrail.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| plugrail.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jp-calendar.plugrail.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jp-calendar.plugrail.dev/mcp | Inconclusive | 406 |
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 ~331
指定した日付(date)の翌日から数えてN営業日目(days)の日付を返します。dateの当日は数えません。daysが負の場合は過去方向（dateの前日から遡ってN営業日目）に計算します。土日・日本の祝日を除外し、calendar="banking"を指定すると銀行休業日（12/31〜1/3）も除外します。dateが営業日かどうかだけ知りたい場合は is_holiday を使ってください（days=0でも同じ情報がskipped経由で得られます）。入力例: {"date": "2026-07-10", "days": 3}
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | – | "standard"（既定）または"banking"（銀行休業日も除外）。 |
| date | string | yes | 起点日 YYYY-MM-DD。例: "2026-07-10"。この日自体は数えません。 |
| days | number | yes | 何営業日先(正)/前(負)かを表す整数。0も指定可: dateをそのまま返し、dateが非営業日ならskippedに1件（date自身とその理由）を記録します。 |
| extra_closed_dates | array | – | 顧客固有の追加休業日（YYYY-MM-DD の配列）。例: ["2026-12-29", "2026-12-30"] |
No output schema declared.
No examples provided.
business_days_between ~419
from〜to間の営業日数を数えます。既定では「fromを含まず、toを含む」境界です（例:「今日から支払期日まで何営業日か」）。include_from/include_toで境界を変更できます。土日・日本の祝日を除外し、calendar="banking"を指定すると銀行休業日（12/31〜1/3）も除外します。from > to の場合はエラーにせず、from/toとinclude_from/include_toを入れ替えて計算した結果の符号を反転した値（負の営業日数）を返します（反対称則: count(A,B,x,y) = -count(B,A,y,x)。A≠B、すなわちfrom≠toの場合に成立する恒等式で、from===toはこの分岐に入らないため対象外）。入力例: {"from": "2026-07-10", "to": "2026-07-20"}
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | – | "standard"（既定）または"banking"（銀行休業日も除外）。 |
| extra_closed_dates | array | – | 顧客固有の追加休業日（YYYY-MM-DD の配列）。例: ["2026-12-29", "2026-12-30"] |
| from | string | yes | 起点日 YYYY-MM-DD。例: "2026-07-10"。 |
| include_from | boolean | – | fromを営業日数に含めるか。既定はfalse。 |
| include_to | boolean | – | toを営業日数に含めるか。既定はtrue。 |
| to | string | yes | 終点日 YYYY-MM-DD。例: "2026-07-20"。fromより前の日付も指定可（結果は負の営業日数になります）。 |
No output schema declared.
No examples provided.
is_holiday ~87
指定した日付が日本の祝日（国民の祝日・休日）かどうかを判定します。内閣府公表データに基づきます。入力例: {"date": "2026-01-01"}
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD形式の日付。例: "2026-01-01" |
No output schema declared.
No examples provided.
list_holidays ~149
指定した年または期間の日本の祝日一覧を返します。入力例: {"year": 2026} または {"from": "2026-01-01", "to": "2026-06-30"}
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | 期間開始日 YYYY-MM-DD。例: "2026-01-01"。yearとは併用不可。 |
| to | string | – | 期間終了日 YYYY-MM-DD。例: "2026-06-30"。yearとは併用不可。 |
| year | integer | – | 西暦年。例: 2026。from/toとは併用不可。 |
No output schema declared.
No examples provided.
What is the PlugRail Japanese Calendar MCP server?
PlugRail Japanese Calendar is an MCP server listed in the public MCP registry as dev.plugrail/jp-calendar. Japanese holiday and business-day calculations using official Japan Cabinet Office data. This page covers its hosted endpoint (https://jp-calendar.plugrail.dev/mcp).
Is the PlugRail Japanese Calendar MCP server safe to use?
PlugRail Japanese Calendar scores 73 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 PlugRail Japanese Calendar MCP server expose?
PlugRail Japanese Calendar exposes 4 tools: is_holiday, list_holidays, add_business_days, business_days_between. Their descriptions and schemas cost roughly 986 tokens of context every time the server is loaded.
Does the PlugRail Japanese Calendar MCP server require authentication?
No. We connected to PlugRail Japanese Calendar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PlugRail Japanese Calendar MCP server still maintained?
PlugRail Japanese Calendar is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.