Shirabe Japan Data Hub MCP server
dev.shirabe/hubshirabe.devstreamable-httpv0.1.0Scanned
Japan data tools for AI agents: calendar (rokuyo), address, name splitting, corporate number lookup
5 tools: 2 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Shirabe Japan Data Hub MCP server can do
The Shirabe Japan Data Hub MCP server is published by shirabe.dev, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: normalize_japanese_address and split_japanese_name), but cannot delete data. 3 tools only read.
1 tool reads private data (lookup_calendar).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
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 3Show 3 read-only tools
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
corporation_searchSearch the Japanese corporate-number registry (National Tax Agency) by company name and return matching companies, each with its 13-digit corporate number (法人番号), registered name a…No findings
Why it is in this group
- The name "corporation_search" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- title: Search Japanese corporations by name
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…Reads private dataNo findings
Why it is in this group
- The name "lookup_calendar" says "lookup": a word for reading.
What it can reach
- private-dataThe name "lookup_calendar" says "lookup" and "calendar": it reads calendars.
- private-dataThe description's first sentence says "calendar": it reads calendars.
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://shirabe.dev/mcp: tools/list returned 5 tools to an anonymous client, including normalize_japanese_address (write), split_japanese_name (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude mcp add --transport http hub https://shirabe.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hub. Review it before you use it.
Capability tags behind 1 rule
- mcp__hub__lookup_calendar private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.shirabe/hub/verify?hash=e2ee8564896aa41c855823eb830ba6aa1fbb1ffd8bbb7bdd46b07bf900f88636" | jq -e '.changed == false'Pinned hash e2ee8564896a, from Nov 15, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.shirabe/hub/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.shirabe/hub)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.
Shirabe Japan Data Hub MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Shirabe Japan Data Hub MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Shirabe Japan Data Hub MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Shirabe Japan Data Hub MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Shirabe Japan Data Hub MCP server have?
- 5 tools: 2 write, 3 read. normalize_japanese_address, split_japanese_name, lookup_calendar, corporation_lookup and corporation_search.
Does the Shirabe Japan Data Hub MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Shirabe Japan Data Hub MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Shirabe Japan Data Hub MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.