
Japan Jepx Mcp
io.github.atushi1841Published by GitHub account atushi1841v0.1.6Updated Oct 27, 2026
Japan JEPX Electricity Apify:apify.com/fruitful_quintessence | Gumroad:atushi5.gumroad.com/l/kutuxe
Overview
Read-only MCP server for Japanese wholesale electricity spot prices from JEPX, covering the nationwide system price and nine regional areas at 30-minute…
- What you can do
- Look up the latest spot price for an area, defaulting to Tokyo
- Get a full 48-period day curve with min, max and average
- Review daily-average price history over a chosen window
- Find the cheapest 30-minute slots or rank areas by cheapest price
- List available areas, units and the latest data date
- When to use it
- Useful when planning electricity costs in Japan: EV charging or home battery scheduling, shifting manufacturing load to cheap hours, monitoring or forecasting the JEPX market, and benchmarking energy costs by region.
- Requirements
- Runs locally as a stdio process, started with uv (Python) from the package directory; a bundled seed cache allows offline answers, and a live fetch to the JEPX site is attempted when network access is available. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Japan Jepx Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Japan JEPX Electricity Spot Price MCP
MCP server exposing Japanese wholesale electricity spot prices from JEPX (Japan Electric Power Exchange) — the system (nationwide) price plus 9 regional area prices at 30-minute granularity (48 periods/day), in JPY/kWh.
Data source: JEPX spot settlement prices (Government Standard Terms of Use),
with OCCTO area-price forecast for regional deltas. A bundled seed cache
(data/jepx_spot.json, ~400 days × 48 periods = 19,200 records) guarantees
offline/fallback answers; a live fetch to JEPX.org is attempted and gracefully
falls back to the seed when the site is IP-restricted.
Output sample
Tools (MCP, 5)
REST endpoints (OpenAPI gateway)
Areas (order of regional prices): system (nationwide), hokkaido,
tohoku, tokyo, chubu, hokuriku, kinki (aka kansai), chugoku,
shikoku, kyushu. Romaji and kanji (e.g. tokyo / 東京) both accepted.
Use cases
- EV charging scheduling / home-battery arbitrage
- Manufacturing load-shifting to cheap hours
- Electricity market monitoring and forecasting analysis
- Energy cost benchmarking for Japan
Local run
Deployment
Apify Actor japan-jepx-mcp (Standby mode, webServerMcpPath=/mcp,
Dockerfile CMD ["python", "-m", "src.main"]):
https://fruitful-quintessence--japan-jepx-mcp.apify.actor/mcp
Apify Store
This MCP server is also available as a managed Apify Actor:
- Apify Store: japan-jepx-mcp — Japanese wholesale electricity spot prices from JEPX (PPE课金). Run from the Apify Store (Run button), then point your MCP client at the endpoint.
Data & attribution
- Source: JEPX (Japan Electric Power Exchange) spot market settlement prices — jepx.org · OCCTO demand/supply area price forecast — occto.or.jp
- Data licensing: Government Standard Terms of Use (出典明示で商用利用可)
- Unit: JPY/kWh (円/kWh); 48 × 30-min periods per trading day
Install via Smithery
Connect this MCP server to your AI client (Claude Desktop, Cursor, VS Code) in one command:
Replace claude with cursor, vscode, or cline for other clients.
Alternatively, install directly from the Smithery registry.
Note: Smithery server listing is pending verification. Once verified, this server will appear in search results with useCount tracking.
MCP Registry
This server is registered on the official MCP Registry. Find it via search: japan-jepx-mcp
Data & Store
- Apify Store: https://apify.com/fruitful_quintessence
- Gumroad datasets: https://atushi5.gumroad.com/l/kutuxe
Source: README.md at commit ce06872
Tools
0Version history
4- v0.1.6LatestOct 23, 2026
- v0.1.5Oct 22, 2026
- v0.1.1Oct 18, 2026
- v0.1.0Oct 10, 2026
Score
40% 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.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.