Skip to content
plugrail logo

plugrail

Hosts MCP servers that let AI assistants check Japanese public holidays, corporate registry records and nutrition data.

Developer toolsAPIFor developers
plugrail.dev ↗
AlternativesSet it up for my teamIs plugrail yours? Claim the card →
At a glanceswept 2026-10-14

309 installs/mo

Emerging

For
Developers connecting Japanese holiday, corporate and nutrition data to Claude through MCP servers
Price
Price not read
Activity
Maintainedrelease 3 months ago
Company
founding year not on record
Runs as
API
Used for
  • check whether a Japanese date is a public holiday
  • look up Japanese corporate numbers and invoice registrations
  • query Japanese nutrition and product recall information
How a program reaches itfound, not claimed · read 2026-10-15
  • MCP serverdev.plugrail/jp-calendarverified in the MCP registry
  • Stateanswers, 4 toolschecked 2026-10-15
  • Address to connectjp-calendar.plugrail.dev/mcp
  • MCP docsjp-calendar.plugrail.dev/mcpthe vendor's page ↗

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare plugrail with

Pick up to two.

All Developer tools tools →

Questions this page answers
  • What is plugrail?

    Hosts MCP servers that let AI assistants check Japanese public holidays, corporate registry records and nutrition data. It is listed in the Atlas under Developer tools.

  • Who is plugrail for?

    Developers connecting Japanese holiday, corporate and nutrition data to Claude through MCP servers

  • Do people use plugrail?

    Emerging: 309 installs/mo (npm).

  • Is plugrail still maintained?

    Maintained: release 3 months ago.

  • What are alternatives to plugrail?

    In Developer tools, by use: Agility CMS, MCP Bundles, Verifox AI, GreenCalculus, MCP-Builder.ai, OBTO.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.