jp-calendar
https://jp-calendar.plugrail.dev
Registry code: 1c599c4ace1a29fe
Japanese holiday and business-day calculations using official Japan Cabinet Office data.
from a public catalogue that lists it, not from the operator
- endpoint
- https://jp-calendar.plugrail.dev/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is jp-calendar live?
- Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
- Is jp-calendar free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does jp-calendar have?
- 4 tools: is_holiday, add_business_days, list_holidays, business_days_between.
- Is jp-calendar safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 4 tools
- down → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- check if a date is a japanese holiday
- add business days to a date
- count business days between dates
- list japanese holidays
- takes → gives
- data → data
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
is_holiday reads unknown 22h ago
指定した日付が日本の祝日(国民の祝日・休日)かどうかを判定します。内閣府公表データに基づきます。入力例: {"date": "2026-01-01"}
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "date" ], "properties": { "date": { "type": "string", "description": "YYYY-MM-DD形式の日付。例: \"2026-01-01\"" } } }arguments 13 linesadd_business_days reads unknown never probed
指定した日付(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}
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "date", "days" ], "properties": { "date": { "type": "string", "description": "起点日 YYYY-MM-DD。例: \"2026-07-10\"。この日自体は数えません。" }, "days": { "type": "number", "description": "何営業日先(正)/前(負)かを表す整数。0も指定可: dateをそのまま返し、dateが非営業日ならskippedに1件(date自身とその理由)を記録します。" }, "calendar": { "type": "string", "description": "\"standard\"(既定)または\"banking\"(銀行休業日も除外)。" }, "extra_closed_dates": { "type": "array", "items": { "type": "string" }, "description": "顧客固有の追加休業日(YYYY-MM-DD の配列)。例: [\"2026-12-29\", \"2026-12-30\"]" } } }arguments 29 lineslist_holidays reads unknown 19h ago
指定した年または期間の日本の祝日一覧を返します。入力例: {"year": 2026} または {"from": "2026-01-01", "to": "2026-06-30"}
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "to": { "type": "string", "description": "期間終了日 YYYY-MM-DD。例: \"2026-06-30\"。yearとは併用不可。" }, "from": { "type": "string", "description": "期間開始日 YYYY-MM-DD。例: \"2026-01-01\"。yearとは併用不可。" }, "year": { "type": "integer", "maximum": 9007199254740991, "minimum": -9007199254740991, "description": "西暦年。例: 2026。from/toとは併用不可。" } } }arguments 20 linesbusiness_days_between reads unknown 22h ago
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"}
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "from", "to" ], "properties": { "to": { "type": "string", "description": "終点日 YYYY-MM-DD。例: \"2026-07-20\"。fromより前の日付も指定可(結果は負の営業日数になります)。" }, "from": { "type": "string", "description": "起点日 YYYY-MM-DD。例: \"2026-07-10\"。" }, "calendar": { "type": "string", "description": "\"standard\"(既定)または\"banking\"(銀行休業日も除外)。" }, "include_to": { "type": "boolean", "description": "toを営業日数に含めるか。既定はtrue。" }, "include_from": { "type": "boolean", "description": "fromを営業日数に含めるか。既定はfalse。" }, "extra_closed_dates": { "type": "array", "items": { "type": "string" }, "description": "顧客固有の追加休業日(YYYY-MM-DD の配列)。例: [\"2026-12-29\", \"2026-12-30\"]" } } }arguments 37 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id1c599c4ace1a29fe.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/1c599c4ace1a29fe/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/1c599c4ace1a29fe?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- jp-corporate.plugrail.dev jp-corporate
- jp-recall.plugrail.dev jp-recall