Gachi Data API — Japan Station & Accessibility Data MCP server
com.gachi-tokusuru/japan-data-apigachi-tokusuru.comstreamable-httpv1.0.1Scanned
Deep, obscure Japanese station, accessibility & hazard data for AI agents. English-first.
10 tools: 10 only read.
- Reads private data · 1
- Reads text others write · 4
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- 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 Gachi Data API — Japan Station & Accessibility Data MCP server can do
The Gachi Data API — Japan Station & Accessibility Data MCP server is published by gachi-tokusuru.com, a domain the MCP Registry verified. It has 10 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (get_toilet_by_station); 4 tools bring in text other people can write (get_station_hazard, get_active_alerts, get_station_alerts and 1 more).
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 10, 2026, version 1.0.1.
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.
10 tools
Only reads 10Show 10 read-only tools
get_active_alertsLive river flood forecasts and landslide alerts for Japan (JMA official).Reads text others writeNo findings
Why it is in this group
- The name "get_active_alerts" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Live river flood forecasts and landslide alerts for Japan (JMA official). NOT general weather warnings (storm/heavy rain/snow) and NOT earthquakes. Covers JMA 指定河川洪水予報 (river flood forecast, levels 2–5) and 土砂災害警戒情報 (landslide warning), each with level, affected area, official summary and issue time. Optional `area` filters by 2-digit prefecture code (e.g. 13 = Tokyo) or a JMA forecast-area code. Relay of official facts — not a warning issued by this service, not a life-safety system.
Annotations the server declares
- title: Live JMA flood/landslide alerts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_municipality_contextOfficial Japanese government data for any municipality, one call — housing vacancy (2003–2023), nearest-station ridership trend, hazard categories, land prices, livability counts.No findings
Why it is in this group
- The name "get_municipality_context" says "get": a word for reading.
Description, as the server wrote it Official Japanese government data for any municipality, one call — housing vacancy (2003–2023), nearest-station ridership trend, hazard categories, land prices, livability counts. No scores, no judgment — official values only. Accepts a 5-digit municipality code (13104) or an exact name (Shinjuku-ku / 新宿区).
Annotations the server declares
- title: Municipality context (official data)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_public_toilet_by_cityList public toilets in a Japanese municipality, with wheelchair / baby-seat / ostomate flags, address and coordinates.No findings
Why it is in this group
- The name "get_public_toilet_by_city" says "get": a word for reading.
Description, as the server wrote it List public toilets in a Japanese municipality, with wheelchair / baby-seat / ostomate flags, address and coordinates. Covers 612 municipalities nationwide (large cities capped at the top 50 results). Municipality names accept Japanese (e.g. 那覇市, 渋谷区); prefixing the prefecture improves accuracy.
Annotations the server declares
- title: Public toilets in a city
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_station_alertsLive JMA river flood forecasts and landslide alerts affecting a station's prefecture — NOT general weather warnings.Reads text others writeNo findings
Why it is in this group
- The name "get_station_alerts" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Live JMA river flood forecasts and landslide alerts affecting a station's prefecture — NOT general weather warnings. Ask by station name in Japanese (新宿) or romaji (Shinjuku). Prefecture-level match (station master is Greater Tokyo). Relay of official JMA facts.
Annotations the server declares
- title: Live JMA alerts near a station
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_station_contextSame official municipality data as get_municipality_context, resolved from a station: pass a station name (Shinjuku / 新宿 / Musashi-Kosugi) or a Japan Station Master station_id (e.g…No findings
Why it is in this group
- The name "get_station_context" says "get": a word for reading.
Description, as the server wrote it Same official municipality data as get_municipality_context, resolved from a station: pass a station name (Shinjuku / 新宿 / Musashi-Kosugi) or a Japan Station Master station_id (e.g. st_00001), and it returns the context for that station's municipality. Official values only — no scores.
Annotations the server declares
- title: Station-area context (official data)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_station_hazardOfficial disaster-risk categories at a Japanese train station, relayed live from the MLIT 不動産情報ライブラリ (Real Estate Information Library): flood inundation-depth rank, landform / liqu…Reads text others writeNo findings
Why it is in this group
- The name "get_station_hazard" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Official disaster-risk categories at a Japanese train station, relayed live from the MLIT 不動産情報ライブラリ (Real Estate Information Library): flood inundation-depth rank, landform / liquefaction classification, and storm-surge inundation-area presence (landslide & tsunami are license-restricted and return available:false with a link to the official maps). Returns the official values/categories as-is — no composite score, no judgment. Accepts a station name in Japanese (新宿, 武蔵小杉) or romaji (Shinjuku, Musashi-Kosugi). For research/analytics; NOT a substitute for official government hazard maps or evacuation decisions.
Annotations the server declares
- title: Station disaster-risk (official)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_toilet_by_stationLook up wheelchair-accessible / multipurpose toilets inside a train station, including floor, gender, equipment (wheelchair, ostomate, diaper table) and the nearest exit.Reads private dataNo findings
Why it is in this group
- The name "get_toilet_by_station" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "table": it reads databases.
Description, as the server wrote it Look up wheelchair-accessible / multipurpose toilets inside a train station, including floor, gender, equipment (wheelchair, ostomate, diaper table) and the nearest exit. Covers 526 Tokyo stations (Tokyo Bureau of Social Welfare data). Major stations outside Tokyo (Yokohama, Kawasaki, Omiya, Chiba, Fujisawa, Shin-Yokohama…) return an in-station layer that groups accessible toilets by ticket gate — inside vs outside — per railway operator. Accepts Japanese (新宿, 横浜) or romaji (Shinjuku, Yokohama) for major stations.
Annotations the server declares
- title: Accessible toilets in a station
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_train_statusLive train service status for Tokyo-area lines — delays, suspensions, resumptions.Reads text others writeNo findings
Why it is in this group
- The name "get_train_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Live train service status for Tokyo-area lines — delays, suspensions, resumptions. Ask 'is the Yamanote Line running?' by line or station name, English or Japanese. Status enum: normal / delayed / suspended / resumed. Cause text relayed from ODPT (English summary for known patterns, else original text + null). Data via ODPT (CC BY 4.0).
Annotations the server declares
- title: Live Tokyo-area train status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
pingConnection test / health check — call this first to confirm the server is reachable.No findings
Why it is in this group
- The name "ping" says "ping": a word for reading.
Description, as the server wrote it Connection test / health check — call this first to confirm the server is reachable. Returns server identity, deploy version, tool count, station coverage, and the update times of the realtime layers (JMA alerts, train status) so you can confirm freshness, not just liveness. No auth, no arguments, lightweight.
Annotations the server declares
- title: Connection test / health check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
station_searchDiscover Japanese train stations by describing what you want around them, in English or Japanese — "朝ラーメンが食べられて車椅子トイレがある駅", "terminal station with late-night ramen", "水害リスクが低くてラーメン…No findings
Why it is in this group
- The name "station_search" says "search": a word for reading.
Description, as the server wrote it Discover Japanese train stations by describing what you want around them, in English or Japanese — "朝ラーメンが食べられて車椅子トイレがある駅", "terminal station with late-night ramen", "水害リスクが低くてラーメンが多い駅". Semantic search over 9,035 station profiles (lines/terminal size, ramen density & styles, in-station accessible-toilet equipment, official hazard categories, ridership) with hybrid metadata filters — the filters guarantee the constraint, the embedding ranks by fit. Filter intent in the query text (朝ラー/深夜/おむつ/車椅子/水害リスク低…) is auto-applied (filter_source: inferred); explicit params win. Water-hazard intent (水害/洪水/浸水/高潮…リスク低) expands to flood rank AND storm-surge zone; 液状化/地盤 intent filters on the official liquefaction-tendency category; results carry risk_notes when other official hazard categories are high. Inferred facility filters with partial data coverage (おむつ/車椅子 — Tokyo-only data) BOOST confirmed stations instead of excluding unknowns (see soft_filters); explicit params remain strict. Taste/quality words (うまい, "good food", delicious…) are not evaluated (no review data); ramen ranking reflects shop density and style variety only. name_contains gives exact substring matching on station names (日本語/romaji) when the name itself is the requirement. Coverage notes: toilet stats = Tokyo stations only; ridership = Greater Tokyo operators only; hazard = official MLIT categories relayed as-is, NOT a safety judgment. Role split: station_search finds candidate stations — then get_toilet_by_station / search_ramen / get_station_hazard / get_station_context for detail on one station.
Annotations the server declares
- title: Station discovery (semantic + filters)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- 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:38 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
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.gachi-tokusuru.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.gachi-tokusuru.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
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 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http japan-data-api https://api.gachi-tokusuru.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http japan-data-api https://api.gachi-tokusuru.com/mcp --header 'Authorization: <your-authorization>'Run 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__japan-data-api__ping",
"mcp__japan-data-api__get_municipality_context",
"mcp__japan-data-api__get_station_context",
"mcp__japan-data-api__get_toilet_by_station",
"mcp__japan-data-api__get_public_toilet_by_city",
"mcp__japan-data-api__get_station_hazard",
"mcp__japan-data-api__station_search",
"mcp__japan-data-api__get_active_alerts",
"mcp__japan-data-api__get_station_alerts",
"mcp__japan-data-api__get_train_status"
],
"ask": [],
"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 japan-data-api. Review it before you use it.
Capability tags behind 5 rules
- mcp__japan-data-api__get_toilet_by_station private-data
- mcp__japan-data-api__get_station_hazard untrusted-input
- mcp__japan-data-api__get_active_alerts untrusted-input
- mcp__japan-data-api__get_station_alerts untrusted-input
- mcp__japan-data-api__get_train_status untrusted-input
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/com.gachi-tokusuru/japan-data-api/verify?hash=6079938f18cf9a494e58561d9cdb35c183f0dcaa4f36bdb346e4b14621bd80d6" | jq -e '.changed == false'Pinned hash 6079938f18cf, from Nov 10, 2026, 16:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.gachi-tokusuru/japan-data-api/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.gachi-tokusuru/japan-data-api)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:55 UTC.
Gachi Data API — Japan Station & Accessibility Data MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Gachi Data API — Japan Station & Accessibility Data MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Gachi Data API — Japan Station & Accessibility Data MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Gachi Data API — Japan Station & Accessibility Data 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 Gachi Data API — Japan Station & Accessibility Data MCP server have?
- 10 tools: 10 read. ping, get_municipality_context, get_station_context, get_toilet_by_station, get_public_toilet_by_city, get_station_hazard, station_search, get_active_alerts and 2 more.
Does the Gachi Data API — Japan Station & Accessibility Data MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Gachi Data API — Japan Station & Accessibility Data MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Gachi Data API — Japan Station & Accessibility Data MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.