# io.github.CloudCorpRecords/ekidata (npm · @reneturcios/ekidata)

Japanese station, accessibility, hazard and alert data from official sources, in English.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/ekidata`: 69/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-ekidata/reneturcios-ekidata.md), [page](https://verifymcp.io/servers/cloudcorprecords-ekidata/reneturcios-ekidata)
- oci · `ghcr.io/cloudcorprecords/ekidata`: 40/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-ekidata/ghcr-io-cloudcorprecords-ekidata.md), [page](https://verifymcp.io/servers/cloudcorprecords-ekidata/ghcr-io-cloudcorprecords-ekidata)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/ekidata`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1984 tokens (~198/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/ekidata MCP server?

io.github.CloudCorpRecords/ekidata runs locally as an npm package, launched with npx -y @reneturcios/ekidata. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-ekidata -- npx -y @reneturcios/ekidata
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-ekidata": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/ekidata"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-ekidata": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/ekidata"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-ekidata -- npx -y @reneturcios/ekidata
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-ekidata": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/ekidata"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-ekidata --command npx --arg -y --arg @reneturcios/ekidata
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-ekidata:
    command: "npx"
    args: ["-y", "@reneturcios/ekidata"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-ekidata": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/ekidata"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-ekidata -t stdio -c npx -a -y @reneturcios/ekidata
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-ekidata": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/ekidata"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 69)

First indexed and scored.

## MCP tools (10)

### `ping` (~71 tokens)

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.

### `get_municipality_context` (~150 tokens)

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

Input parameters:

- `fields` (string): Optional comma-separated subset: vacancy,ridership,population,hazard,land_price,livability.
- `name_or_code` (string, required): 5-digit 全国地方公共団体コード (e.g. 13104) or exact municipality name (Shinjuku-ku / 新宿区).

### `get_station_context` (~161 tokens)

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.

Input parameters:

- `fields` (string): Optional comma-separated subset: vacancy,ridership,population,hazard,land_price,livability.
- `station_id` (string): Japan Station Master station_id (e.g. st_00001). Alternative to station_name.
- `station_name` (string): Station name in English/romaji (Shinjuku) or Japanese (新宿). Provide this or station_id.

### `get_toilet_by_station` (~175 tokens)

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.

Input parameters:

- `station` (string, required): Station name in Japanese (新宿, 渋谷) or romaji for major stations (Shinjuku, Shibuya, Kita-Senju).

### `get_public_toilet_by_city` (~113 tokens)

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.

Input parameters:

- `city` (string, required): Municipality name in Japanese (e.g. 那覇市, 渋谷区, 上天草市). Prefix the prefecture for accuracy.

### `get_station_hazard` (~181 tokens)

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.

Input parameters:

- `station_name` (string, required): Station name in Japanese (新宿, 武蔵小杉) or romaji (Shinjuku, Musashi-Kosugi).

### `station_search` (~756 tokens)

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.

Input parameters:

- `accessible_toilet_min` (number): Require at least this many in-station accessible toilets (Tokyo stations only; auto-inferred from 車椅子/wheelchair…).
- `diaper` (boolean): Require a diaper changing table in station toilets (auto-inferred from おむつ/子連れ…).
- `flood_rank_max` (number): Max official flood inundation-depth rank 0–6 (0 = no assumed inundation; auto-inferred from 水害リスク低/flood-safe…).
- `late_ramen` (boolean): Require late-night ramen nearby (auto-inferred from 深夜/late night…).
- `limit` (number): Max results (default 10; max 20, or 300 when name_contains is given — set limit >= name_matches_total for exhaustive name-match coverage).
- `morning_ramen` (boolean): Require morning-ramen availability nearby (auto-inferred from 朝ラー/morning…).
- `name_contains` (string): Substring filter on the station name (matches both 日本語 name_ja and romaji name, e.g. "谷" or "sakura"). ANDs with other filters; q still ranks the matches. Use for "stations whose name contains X" req…
- `pref` (string): Optional prefecture filter, Japanese (東京都, 千葉 OK) or romaji (tokyo/osaka). Auto-inferred from the query text when omitted.
- `q` (string, required): Natural-language description of the station/area you want (ja/en). Concrete attribute words (朝ラー, wheelchair toilet, terminal, 水害リスク低) match best.
- `ramen_min` (number): Require at least this many ramen shops nearby (e.g. 30).

### `get_active_alerts` (~169 tokens)

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.

Input parameters:

- `area` (string): Optional prefecture code (01–47, e.g. 13 = Tokyo) or JMA forecast-area code.

### `get_station_alerts` (~91 tokens)

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.

Input parameters:

- `station_name` (string, required): Station name in Japanese (新宿) or romaji (Shinjuku).

### `get_train_status` (~117 tokens)

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

Input parameters:

- `query` (string, required): Line or station name (English or Japanese), e.g. "Yamanote" or "新宿".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-ekidata/reneturcios-ekidata#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 69

## Common questions

### What is the io.github.CloudCorpRecords/ekidata MCP server?

io.github.CloudCorpRecords/ekidata is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/ekidata. Japanese station, accessibility, hazard and alert data from official sources, in English. This page covers its npm package (@reneturcios/ekidata).

### Is the io.github.CloudCorpRecords/ekidata MCP server safe to use?

io.github.CloudCorpRecords/ekidata scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.CloudCorpRecords/ekidata MCP server expose?

io.github.CloudCorpRecords/ekidata exposes 10 tools: ping, get_municipality_context, get_station_context, get_toilet_by_station, get_public_toilet_by_city, and 5 more. Their descriptions and schemas cost roughly 1,984 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/ekidata MCP server still maintained?

io.github.CloudCorpRecords/ekidata is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.CloudCorpRecords/ekidata MCP server under?

io.github.CloudCorpRecords/ekidata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/ekidata
- Socket report: https://socket.dev/npm/package/@reneturcios/ekidata
- Repository: https://github.com/CloudCorpRecords/ekidata
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-ekidata/reneturcios-ekidata.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-ekidata/reneturcios-ekidata.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-ekidata/reneturcios-ekidata