Shirabe Japan Data Hub
REMOTE · SHIRABE.DEV · SCANNED SEP 22
Japan data tools for AI agents: calendar (rokuyo), address, name splitting, corporate number lookup
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 714 tokens (~142/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Shirabe Japan Data Hub MCP server?
Shirabe Japan Data Hub is a hosted endpoint at https://shirabe.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · shirabe.dev
claude mcp add --transport http dev-shirabe-hub 'https://shirabe.dev/mcp'
{
"mcpServers": {
"dev-shirabe-hub": {
"url": "https://shirabe.dev/mcp"
}
}
} {
"servers": {
"dev-shirabe-hub": {
"type": "http",
"url": "https://shirabe.dev/mcp"
}
}
} [mcp_servers.dev-shirabe-hub] url = "https://shirabe.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-shirabe-hub": {
"type": "remote",
"url": "https://shirabe.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-shirabe-hub --url 'https://shirabe.dev/mcp' --transport streamable-http
mcp_servers:
dev-shirabe-hub:
url: "https://shirabe.dev/mcp" {
"McpServers": {
"dev-shirabe-hub": {
"Transport": "http",
"Url": "https://shirabe.dev/mcp"
}
}
} assistant mcp add dev-shirabe-hub -t streamable-http -u 'https://shirabe.dev/mcp'
{
"mcpServers": {
"dev-shirabe-hub": {
"type": "http",
"url": "https://shirabe.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://shirabe.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shirabe.dev | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f875ca529c23ff4c0ee401c873f0352f |
| SANs: shirabe.dev, *.shirabe.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of shirabe.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| shirabe.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shirabe.dev/mcp | Verified | 200 | |
| http (plaintext) | http://shirabe.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
corporation_lookup Look up Japanese corporation by number ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| law_id | string | yes | A 13-digit Japanese corporate number (法人番号), e.g. 1234567890123. |
No output schema declared.
No examples provided.
corporation_search Search Japanese corporations by name ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A Japanese company name, e.g. 株式会社テックウェル (variants like ㈱テックウェル are accepted). |
No output schema declared.
No examples provided.
lookup_calendar Look up Japanese calendar ~158
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).
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Optional purpose categories to score (e.g. marriage, funeral, groundbreaking). Omit to return all available categories. |
| date | string | yes | Target date in YYYY-MM-DD (between 1873-01-01 and 2100-12-31). |
No output schema declared.
No examples provided.
normalize_japanese_address Normalize Japanese address ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | A raw Japanese address string (may include postal code, building, floor). |
No output schema declared.
No examples provided.
split_japanese_name Split Japanese personal name ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A Japanese personal name, e.g. 山田良介. |
No output schema declared.
No examples provided.
What is the Shirabe Japan Data Hub MCP server?
Shirabe Japan Data Hub is an MCP server listed in the public MCP registry as dev.shirabe/hub. Japan data tools for AI agents: calendar (rokuyo), address, name splitting, corporate number lookup. This page covers its hosted endpoint (https://shirabe.dev/mcp).
Is the Shirabe Japan Data Hub MCP server safe to use?
Shirabe Japan Data Hub scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Shirabe Japan Data Hub MCP server expose?
Shirabe Japan Data Hub exposes 5 tools: lookup_calendar, normalize_japanese_address, split_japanese_name, corporation_lookup, corporation_search. Their descriptions and schemas cost roughly 663 tokens of context every time the server is loaded.
Does the Shirabe Japan Data Hub MCP server require authentication?
No. We connected to Shirabe Japan Data Hub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Shirabe Japan Data Hub MCP server still maintained?
Shirabe Japan Data Hub is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.