Japan Data Api MCP server
{
"mcpServers": {
"gachi-data": {
"type": "http",
"url": "https://api.gachi-tokusuru.com/mcp"
}
}
}{
"mcpServers": {
"gachi-data": {
"type": "http",
"url": "https://api.gachi-tokusuru.com/mcp"
}
}
}{
"mcpServers": {
"gachi-data": {
"type": "http",
"url": "https://api.gachi-tokusuru.com/mcp"
}
}
}{
"servers": {
"gachi-data": {
"type": "http",
"url": "https://api.gachi-tokusuru.com/mcp"
}
}
}{
"mcpServers": {
"gachi-data": {
"type": "http",
"url": "https://api.gachi-tokusuru.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.1
What it does
Gachi Data API is a hosted MCP server providing accessibility and hazard data for Japanese stations and municipalities. It offers accessible toilet locations in 526 Tokyo stations, public toilet data for 612 municipalities, and official hazard information (flood, liquefaction, storm surge) from Japan's Ministry of Land, Infrastructure, Transport and Tourism.
- Find accessible toilets (wheelchair, ostomate, diaper table equipped) at a specific Tokyo station along with the nearest exit.
- Locate public toilets with accessibility features in a Japanese municipality by coordinates or city name.
- Check official hazard categories (flood inundation depth, liquefaction risk, storm surge presence) at a station to assess local risks.
Tools this server exposes
| Tool | Does |
|---|---|
| get_toilet_by_station | Returns accessible toilets in a Tokyo station with equipment flags and nearest exit information; accepts Japanese or romaji station names. |
| get_public_toilet_by_city | Returns public toilets in a municipality with wheelchair, baby-seat, and ostomate accessibility flags; accepts Japanese city names. |
| get_station_hazard | Returns official MLIT hazard categories at a station (flood, liquefaction, storm surge) relayed live and cached for 14 days; accepts Japanese or romaji station |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.