# Shirabe Japan Data Hub

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

- name: dev.shirabe/hub
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 75/100 flags: no-repository
- quality: 85/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/dev.shirabe%2Fhub
- tools: https://api.protogrid.dev/v1/servers/dev.shirabe%2Fhub/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "hub": {
      "type": "http",
      "url": "https://shirabe.dev/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 99
- freshness: 65
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-97% ~updated-108d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: lookup_calendar (openWorldHint); normalize_japanese_address (openWorldHint); split_japanese_name (openWorldHint); …
- pass `tools.token_cost`: about 963 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 963 tokens to load them all
- tool set hash: 84250f9d9e67dfc210cff22f4966853f
- badge: [![protogrid quality](https://protogrid.dev/badge/dev.shirabe/hub.svg)](https://protogrid.dev/servers/dev.shirabe/hub)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://shirabe.dev/mcp (streamable-http, auth none, reachable true, uptime30d 0.9655172)

## Packages

_none_

## Tools (5)

- `corporation_lookup`: 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.
- `corporation_search`: 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.
- `lookup_calendar`: 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).
- `normalize_japanese_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.
- `split_japanese_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.