io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026
Japanese station, accessibility, hazard and alert data from official sources, in English.
Local bridge to a hosted MCP server that relays official Japanese station, accessibility, hazard and live alert data in English.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
ekidata is a small local bridge to a hosted MCP server that relays official Japanese public data in English: municipality and station context, accessible-toilet lookups, station hazard categories from MLIT data, station search, live JMA river and landslide alerts, and Tokyo-area train status.
The bridge keeps no dataset of its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched. Every tool in the captured surface only reads public data.
ping — connection test and freshness check. No
arguments and no required fields.get_municipality_context — official data for a
municipality by 5-digit code or exact name. Required:
name_or_code. Optional: fields.get_station_context — the same municipality context
resolved from a station name or station_id. Its
captured schema carries an empty required list, so
either identifier may be supplied.get_toilet_by_station — accessible toilets inside a
station, with floor, equipment and nearest exit.
Required: station.get_public_toilet_by_city — public toilets in a
municipality, with accessibility flags, address and
coordinates. Required: city.get_station_hazard — official disaster-risk
categories at a station, relayed from MLIT data.
Required: station_name.station_search — find stations by describing what
should be around them, in English or Japanese, with
optional filters such as name_contains, pref,
limit, ramen, toilet, diaper and flood-rank options.
Required: q.get_active_alerts — live JMA river flood forecasts
and landslide alerts. Optional: area. No required
fields.get_station_alerts — those same JMA alerts for a
station's prefecture. Required: station_name.get_train_status — live Tokyo-area train service
status by line or station name. Required: query.GACHI_MCP_URL (optional) — override the upstream
endpoint. Defaults to https://api.gachi-tokusuru.com/mcp.
(The override hook is this rebuild's own labelled
reconstruction.)GACHI_API_KEY (optional) — when set, every upstream
request carries an Authorization: Bearer <key> header.
When it is not set, no auth header is sent. (This
forwarding is also a labelled reconstruction; the
original surface was captured keyless.)On the first tool call the client opens a streamable
HTTP session with the upstream: a JSON-RPC initialize
request (protocolVersion 2025-03-26, clientInfo name
ekidata), then a notifications/initialized
notification, then the tools/call request carrying
the caller's arguments unchanged. When the upstream
answers initialize with an Mcp-Session-Id header,
that value rides on every later request of the session,
which is reused for the life of the process. Replies
may arrive as plain JSON or as server-sent events;
both are read.
Successful upstream results pass through verbatim,
including any isError flag the upstream sets.
Failures — a JSON-RPC error, a non-2xx status, an
unreadable response, or a request that cannot be
completed — come back as an isError result whose
text starts with ekidata error: (this rendering is
this rebuild's own labelled reconstruction).
Each tool is also a subcommand taking one JSON argument string (omit it for tools that take none):
Exit codes: 0 on success, 1 on an isError
result, 2 on a usage error.
MCP client config:
The container's default command is mcp, so the first
form is a stdio MCP server; any other arguments reach
the CLI normally.
The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.
MIT — see LICENSE.
Source: README.md at commit d485b75
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.
Takes no parameters.
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 / 新宿区).
fieldsname_or_coderequiredSame 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.
fieldsstation_idstation_nameLook 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.
stationrequiredList 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.
cityrequiredOfficial 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.
station_namerequiredDiscover 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.
qrequiredpreflimitdiaperramen_minlate_ramenmorning_ramenname_containsflood_rank_maxaccessible_toilet_minLive 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.
areaLive 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.
station_namerequiredLive 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).
queryrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx @reneturcios/ekidata pingnpx @reneturcios/ekidata get_municipality_context '{"name_or_code":"13104"}'npx @reneturcios/ekidata station_search '{"q":"terminal station with late-night ramen"}'npx @reneturcios/ekidata get_train_status '{"query":"Yamanote"}'npx @reneturcios/ekidata --versionnpx -y @reneturcios/ekidata mcp{ "mcpServers": { "ekidata": { "command": "npx", "args": ["-y", "@reneturcios/ekidata", "mcp"] } }}docker run -i ghcr.io/cloudcorprecords/ekidatadocker run --rm ghcr.io/cloudcorprecords/ekidata --versionnpm installnpm run buildnpm testnpm run dev