Skip to content

Shirabe Japan Data Hub

by shirabe.dev · remote · no sign-in to list tools · v0.1.0 · published by dev.shirabe

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

Changes · 2
CompareRegistry entry

5 tools: 2 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http hub https://shirabe.dev/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 2Claude Code: ask
  • normalize_japanese_addressNormalize a free-form Japanese address against the official Address Base Registry (ABR, all 47 prefectures).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • title: Normalize Japanese address
  • split_japanese_nameSplit a Japanese personal name into family and given parts using IPAdic person-name POS tags (with whitespace/length heuristics as fallback).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • title: Split Japanese personal name
Only reads 3Claude Code: allow
  • corporation_lookupLook up a Japanese company by its 13-digit corporate number (法人番号) against the National Tax Agency (NTA) corporate-number registry.No findings

    Why it is in this group

    • The name "corporation_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • title: Look up Japanese corporation by number
  • lookup_calendarLook 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 purpos…No findings

    Why it is in this group

    • The name "lookup_calendar" says "lookup": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • title: Look up Japanese calendar

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http hub https://shirabe.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hub__lookup_calendar",
      "mcp__hub__corporation_lookup",
      "mcp__hub__corporation_search"
    ],
    "ask": [
      "mcp__hub__normalize_japanese_address",
      "mcp__hub__split_japanese_name"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as hub. Review it before you use it.