MCP.Market

Gachi Data API — Japan Station & Accessibility Data MCP server

online · 100% uptime
by gachi-tokusuru.com·com.gachi-tokusuru/japan-data-api·v1.0.1·1 stars
No reviews yet

Deep, obscure Japanese station, accessibility & hazard data for AI agents. English-first.

B84/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B84/100

full report

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed Gachi Data API — Japan Station & Accessibility Data yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Gachi Data API — Japan Station & Accessibility Data tools (10)

write = sends, deletes, buys or posts
  • get_active_alertsFree

    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.

  • get_municipality_contextFree

    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 / 新宿区).

  • get_public_toilet_by_cityFree

    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.

  • get_station_alertsFree

    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.

  • get_station_contextFree

    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.

  • get_station_hazardFree

    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.

  • get_toilet_by_stationFree

    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.

  • get_train_statusFree

    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).

  • pingFree

    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.

  • station_searchFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 313ms20/20
  • Tool poisoning10 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 26 days ago15/15
  • Maintainer identitynamespace and repository owner differ; website matches verified namespace5/10
Overall 84/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Gachi Data API — Japan Station & Accessibility Data compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
84/100
higher than 68% of 48,255 servers
Tools
10
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
127 ms
faster than 78% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

What its tools let an agent do: 10 read

Install Gachi Data API — Japan Station & Accessibility Data in Claude Code, Cursor or VS Code

claude mcp add --transport http japan-data-api https://api.gachi-tokusuru.com/mcp
Add to Cursor

What the publisher says

From the Gachi Data API — Japan Station & Accessibility Data repository's README, as published. We do not edit it. Read it on GitHub

Gachi Data API — Japan Station & Accessibility Data (API · MCP · Open Datasets)

This is a hosted service. You do NOT self-host it.

Get a free API key at https://api.gachi-tokusuru.com and connect to the remote endpoint below.

The source in this repo is published for transparency; the data lives in the hosted backend, so a local clone will not return data.

Deep, obscure Japanese data you won't find anywhere else — stations, accessibility, vacancy, hazards. Hand-verified, English-first, built for AI agents. Available as an MCP server, a REST API, and free open datasets. One key works for both the API and MCP.

  • 526 Tokyo stations — accessible / multipurpose toilets with floor, gender, equipment flags (wheelchair, ostomate, diaper table) and the nearest station exit (an original first-party value computed by spatial join — not in any raw dataset).
  • 612 municipalities nationwide — public toilets with wheelchair / baby-seat / ostomate flags, address and coordinates.
  • Free open datasets — Japan Station Master (entity-resolved, 9,145 stations nationwide) & Ridership 2000–2025, sharing one station_id: https://github.com/eng213035/gachi-open-datasets (Zenodo DOI 10.5281/zenodo.21199500).

Station names accept Japanese (新宿) or romaji (Shinjuku, Kita-Senju) for major stations.

Connect

  • Endpoint: https://api.gachi-tokusuru.com/mcp
  • Transport: Streamable HTTP (remote)
  • Auth: Authorization: Bearer — free key at https://api.gachi-tokusuru.com
{
  "mcpServers": {
    "gachi-data": {
      "url": "https://api.gachi-tokusuru.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Tools

REST endpoints

  • GET /v1/station-toilets/search?station=Shinjuku — accessible toilets in a Tokyo station
  • GET /v1/toilets/nearby?lat=&lng=&radius=&wheelchair=&ostomate=&diaper= — public toilets near a point
  • GET /v1/stations/{stationid}/hazard — official MLIT hazard categories at a station, relayed live (flood inundation-depth rank, liquefaction/landform, storm-surge presence). Values are returned verbatim from 国土交通省 不動産情報ライブラリ with attribution, cached 14 days — no derived score, and not a substitute for official hazard maps. Landslide & tsunami source layers are 一部非商用 (license-restricted), so they return available:false with a link to the official hazard maps. Also available as the MCP tool getstationhazard(stationname). stationid comes from the Japan Station Master (e.g. st00001); 423 of 425 stations have coordinates (2 remain unlocated → hazard: null).

All endpoints use the same Authorization: Bearer and share one monthly quota. Full spec: /openapi.yaml, docs: /docs.

Example

curl -X POST https://api.gachi-tokusuru.com/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"get_toilet_by_station","arguments":{"station":"Shinjuku"}}}'

Pricing

Free 1k · Pro $19/100k · All Access $49/200k · Business $149/500k. Full details: https://api.gachi-tokusuru.com

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Gachi Data API — Japan Station & Accessibility Data: common questions

Is Gachi Data API — Japan Station & Accessibility Data MCP server safe?
Mostly: it is graded B (84/100). Read the Gachi Data API — Japan Station & Accessibility Data safety report
How do I install Gachi Data API — Japan Station & Accessibility Data?
It runs remotely at api.gachi-tokusuru.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Gachi Data API — Japan Station & Accessibility Data need an API key?
Yes. The registry entry asks for Authorization.
Is Gachi Data API — Japan Station & Accessibility Data maintained?
The last commit was 65 days ago (2026-08-31). The latest release is v1.0.1.
Is Gachi Data API — Japan Station & Accessibility Data up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Gachi Data API — Japan Station & Accessibility Data compare with other MCP servers?
safety score 84/100 (higher than 68% of 48,255 servers); tools 10 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.