Is the Plugrail Jp Calendar MCP server down?

mcp-registry/dev.plugrail/jp-calendar · v0.2.0

healthy
Last checked 2026-10-22 04:30 UTC · handshake 1.3s

As of 2026-10-22 04:30 UTC, the Plugrail Jp Calendar MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
100%
checks observed
4,226
outages (90d)
1
tools
4

Japanese holiday and business-day calculations using official Japan Cabinet Office data.

Install Plugrail Jp Calendar MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http plugrail-jp-calendar-mcp-server https://jp-calendar.plugrail.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "plugrail-jp-calendar-mcp-server": {
      "type": "http",
      "url": "https://jp-calendar.plugrail.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (83/100)

B (83/100): 0 error(s), 2 warning(s) across 4 tool(s); ~800 tokens of tool definitions.
Scores higher than 41% of 15,534 MCP servers Glimind has audited.
Its tool list costs an agent ~800 tokens per session — lighter than 80% of servers.
83 → 83 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability84

What to fix (4)

4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: add_business_days, business_days_between, is_holiday, list_holidays

Handshake + tools/list takes ~2,329 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 4 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.plugrail%2Fjp-calendar/fixes

add_business_days 1 change
{
  "name": "add_business_days",
  "description": "指定した日付(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}",
  "inputSchema": {
    "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\"]"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
list_holidays 1 change
{
  "name": "list_holidays",
  "description": "指定した年または期間の日本の祝日一覧を返します。入力例: {\"year\": 2026} または {\"from\": \"2026-01-01\", \"to\": \"2026-06-30\"}",
  "inputSchema": {
    "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とは併用不可。"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.plugrail/jp-calendar"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.plugrail/jp-calendar"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.plugrail%2Fjp-calendar.svg)](https://glimind.com/server/mcp-registry%2Fdev.plugrail%2Fjp-calendar?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.plugrail%2Fjp-calendar?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.plugrail%2Fjp-calendar.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.plugrail%2Fjp-calendar.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.plugrail%2Fjp-calendar?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:bf31b0bb11eb6ab2…, first seen 2026-10-17, included at leaf 1660 of 43,724. Version history · verify what your client received.

Tools (4)

Compare: most reliable calendar servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Plugrail Jp Calendar MCP server down right now?

As of 2026-10-22 04:30 UTC, the Plugrail Jp Calendar MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.

How many tools does Plugrail Jp Calendar MCP server provide?

Plugrail Jp Calendar MCP server advertises 4 tools, including add_business_days, business_days_between, is_holiday, list_holidays.

How do I install Plugrail Jp Calendar MCP server?

Point your MCP client at this streamable-http endpoint: https://jp-calendar.plugrail.dev/mcp

Is the Plugrail Jp Calendar MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Plugrail Jp Calendar MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve