MCP servers · cloudcorprecords

ekidata: English access to Japanese station and public alert data via MCP

An MCP bridge that relays a hosted server offering English-language access to official Japanese station, accessibility, hazard and alert data.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The bridge serves the upstream server's tool list locally and forwards each tool call without keeping a dataset of its own, returning results unchanged. The tools cover municipality context, accessible and public toilet lookups, station hazard categories from MLIT data, station search, live JMA river flood forecasts and landslide alerts, and Tokyo-area train status. Every tool only reads public data.

It suits work that needs Japanese station accessibility, disaster-risk or alert information in English. Station search accepts descriptions in English or Japanese, with filters such as toilet, diaper and flood-rank options, so it can find stations matching given conditions.

It can run as a stdio MCP server, as a CLI where each tool is a subcommand taking one JSON argument, or in Docker, whose default command starts the MCP server. On the first call it opens a streamable HTTP session with the upstream endpoint. An optional API key can be set to add a bearer header to upstream requests, and the endpoint can be overridden through an environment variable. Failures are returned as error results. The test suite runs against a stubbed upstream and makes no live network calls. Licensed under MIT.

Limitations and requirements

Requires network access to the hosted upstream MCP endpoint; the default endpoint can be overridden through configuration. An API key is optional and is sent only when configured. Upstream failures, such as non-success status codes or unreadable responses, are returned as error results rather than data. Coverage is limited to Japanese public data, and train status covers only the Tokyo area.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/ekidata

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

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026