Shirabe Japan Data Hub

Japan data tools for AI agents: calendar (rokuyo), address, name splitting, corporate number lookup

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~976Tokens (tool definitions)
~678 BTypical response size
Moderate attention impact (0.76% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "hub": {
      "url": "https://shirabe.dev/mcp"
    }
  }
}

Remote endpoints

https://shirabe.dev/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟒 Read-only🟑 WriteπŸ”΄ Deleteβšͺ Unknown
🟒lookup_calendar(date, categories)

Look up Japanese calendar information for a given date: Rokuyo (six-day cycle such as Taian/Butsumetsu), Rekichu (almanac notes), Eto (sexagenary cycle), 24 solar terms, and purpose-based auspiciousness scores. Useful when an AI agent needs canonical Japanese calendar facts (e.g. choosing an auspicious date for a wedding or ceremony). Source: Shirabe Calendar API (shirabe.dev).

Input Schema

{
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "Target date in YYYY-MM-DD (between 1873-01-01 and 2100-12-31)."
    },
    "categories": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional purpose categories to score (e.g. marriage, funeral, groundbreaking). Omit to return all available categories."
    }
  },
  "required": [
    "date"
  ],
  "additionalProperties": false
}
🟒normalize_japanese_address(address)

Normalize a free-form Japanese address against the official Address Base Registry (ABR, all 47 prefectures). Returns the canonical form, structured components (prefecture/city/town/block/building), postal code, WGS84 coordinates, match level (0-4) and confidence, plus mandatory CC BY 4.0 attribution. Useful when an AI agent must clean or de-duplicate Japanese B2B/customer records. Source: Shirabe Address API.

Input Schema

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "A raw Japanese address string (may include postal code, building, floor)."
    }
  },
  "required": [
    "address"
  ],
  "additionalProperties": false
}
🟒split_japanese_name(name)

Split a Japanese personal name into family and given parts using IPAdic person-name POS tags (with whitespace/length heuristics as fallback). Returns family, given, and a confidence score (0-1; warning when low). Useful for normalizing name fields in HR, CRM, or form data. Source: Shirabe Text API.

Input Schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "A Japanese personal name, e.g. ε±±η”°θ‰―δ»‹."
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false
}
🟒corporation_lookup(law_id)

Look up a Japanese company by its 13-digit corporate number (法人η•ͺ号) against the National Tax Agency (NTA) corporate-number registry. Returns the registered trade name, head-office address, change history and other public fields as JSON, plus mandatory NTA attribution. Useful when an AI agent already has a corporate number and needs canonical company facts (e.g. validating or enriching a B2B record). To go the other way (company name β†’ number), use corporation_search. Source: Shirabe Corporation API.

Input Schema

{
  "type": "object",
  "properties": {
    "law_id": {
      "type": "string",
      "description": "A 13-digit Japanese corporate number (法人η•ͺ号), e.g. 1234567890123."
    }
  },
  "required": [
    "law_id"
  ],
  "additionalProperties": false
}
🟒corporation_search(name)

Search the Japanese corporate-number registry (National Tax Agency) by company name and return matching companies, each with its 13-digit corporate number (法人η•ͺ号), registered name and address, plus mandatory NTA attribution. Handles trade-name variants (㈱ / (ζ ͺ) / ζ ͺ式会瀾) via normalization. Useful when an AI agent has a company name and needs to resolve its corporate number / canonical record. To go the other way (number β†’ company), use corporation_lookup. Source: Shirabe Corporation API.

Input Schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "A Japanese company name, e.g. ζ ͺεΌδΌšη€Ύγƒ†γƒƒγ‚―γ‚¦γ‚§γƒ« (variants like γˆ±γƒ†γƒƒγ‚―γ‚¦γ‚§γƒ« are accepted)."
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools
verifiedversion not recorded5 tools