Shirabe Japan Data Hub is an MCP server published by dev.shirabe, hosted at shirabe.dev. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 5 tools, including lookup_calendar, normalize_japanese_address, split_japanese_name, corporation_lookup, corporation_search.
Japan data tools for AI agents: calendar (rokuyo), address, name splitting, corporate number lookup
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
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).
| Parameter | Type | Description |
|---|---|---|
| date * | string | Target date in YYYY-MM-DD (between 1873-01-01 and 2100-12-31). |
| categories | array | Optional purpose categories to score (e.g. marriage, funeral, groundbreaking). Omit to return all available categories. |
{
"name": "lookup_calendar",
"title": "Look up Japanese calendar",
"description": "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).",
"inputSchema": {
"type": "object",
"required": [
"date"
],
"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."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Look up Japanese calendar",
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
Inferred from the host name and headers: what a server runs on, not who runs 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.
| Parameter | Type | Description |
|---|---|---|
| address * | string | A raw Japanese address string (may include postal code, building, floor). |
{
"name": "normalize_japanese_address",
"title": "Normalize Japanese address",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"description": "A raw Japanese address string (may include postal code, building, floor)."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Normalize Japanese address",
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | A Japanese personal name, e.g. 山田良介. |
{
"name": "split_japanese_name",
"title": "Split Japanese personal name",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "A Japanese personal name, e.g. 山田良介."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Split Japanese personal name",
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| law_id * | string | A 13-digit Japanese corporate number (法人番号), e.g. 1234567890123. |
{
"name": "corporation_lookup",
"title": "Look up Japanese corporation by number",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"law_id"
],
"properties": {
"law_id": {
"type": "string",
"description": "A 13-digit Japanese corporate number (法人番号), e.g. 1234567890123."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Look up Japanese corporation by number",
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | A Japanese company name, e.g. 株式会社テックウェル (variants like ㈱テックウェル are accepted). |
{
"name": "corporation_search",
"title": "Search Japanese corporations by name",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "A Japanese company name, e.g. 株式会社テックウェル (variants like ㈱テックウェル are accepted)."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Search Japanese corporations by name",
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Shirabe exposes Japan-specific APIs (calendar lookup, address normalization, Japanese name splitting, and corporate-number lookup/search) for AI agents; a cross-identifier enrich tool is added as it goes live. Call tools/list to see available tools.
Names, descriptions and schemas were written by the server and are shown as data.