AI-native REST API + MCP server for Japanese calendar (rokuyo/暦注/kanshi/24 solar
AI-native REST API + MCP server for Japanese calendar (rokuyo/暦注/kanshi/24 solar terms) with purpose-specific auspicious-day judgments. OpenAPI 3.1, GPTs Actions, Claude Tool Use, Gemini Function Calling ready. 日本の暦APIを天文学的精度で。
active Production-safe Score 96/100 http no auth
At a glance
| Endpoint | https://shirabe.dev/mcp |
|---|---|
| Source | https://github.com/techwell-inc-jp/shirabe-calendar-api |
| Transport | http |
| Tools | 5 |
| Auth | none |
| First seen | 2026-05-25 00:46:10 |
| Last checked | 2026-11-17 21:44:41 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 253 / 403 ms |
| Last successful check | 2026-11-17 21:44:41 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (5)
lookup_calendar— Look up Japanese calendar information for a given date: Rokuyo (six-day cycle such as Taian/Butsumetsu), Rekichu (almanac notes), Eto (sexagnormalize_japanese_address— Normalize a free-form Japanese address against the official Address Base Registry (ABR, all 47 prefectures). Returns the canonical form, strsplit_japanese_name— Split a Japanese personal name into family and given parts using IPAdic person-name POS tags (with whitespace/length heuristics as fallback)corporation_lookup— Look up a Japanese company by its 13-digit corporate number (法人番号) against the National Tax Agency (NTA) corporate-number registry. Returnscorporation_search— Search the Japanese corporate-number registry (National Tax Agency) by company name and return matching companies, each with its 13-digit co
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:44:41 | ✓ | ✓ | 214 ms | 94 | active |
| 2026-11-17 21:29:36 | ✓ | ✓ | 206 ms | 94 | active |
| 2026-11-17 21:14:23 | ✓ | ✓ | 204 ms | 94 | active |
| 2026-11-17 20:59:03 | ✓ | ✓ | 367 ms | 91 | active |
| 2026-11-17 20:44:02 | ✓ | ✓ | 341 ms | 91 | active |
| 2026-11-17 20:29:02 | ✓ | ✓ | 206 ms | 94 | active |
| 2026-11-17 20:13:59 | ✓ | ✓ | 170 ms | 94 | active |
| 2026-11-17 19:56:08 | ✓ | ✓ | 335 ms | 91 | active |
| 2026-11-17 19:41:00 | ✓ | ✓ | 145 ms | 94 | active |
| 2026-11-17 19:25:43 | ✓ | ✓ | 149 ms | 94 | active |
| 2026-11-17 19:10:39 | ✓ | ✓ | 302 ms | 91 | active |
| 2026-11-17 18:55:31 | ✓ | ✓ | 394 ms | 91 | active |
| 2026-11-17 18:40:24 | ✓ | ✓ | 185 ms | 94 | active |
| 2026-11-17 18:25:18 | ✓ | ✓ | 391 ms | 91 | active |
| 2026-11-17 18:10:03 | ✓ | ✓ | 568 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://shirabe.dev/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/shirabe-dev-mcp # JSON