japan-data-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@japan-data-mcp Is tomorrow a public holiday in Japan?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
japan-data-mcp
npm:
@mameta/japan-data-mcp· MCP Registry:io.github.Mameta29/japan-data-mcp· transport: stdio
An MCP server that gives AI agents (Claude Desktop, Cursor, Cline, …) one-call access to the agentic-jp.com suite of Japanese data APIs. Every call is settled per-use over the x402 payment protocol — no account, no subscription, no API key.
What it covers — 28 tools across 7 APIs
API | Tools | What it does |
address |
| Japanese address normalization, geocoding, postal-code lookup, free-form parsing |
furigana |
| Reading conversion, name readings, text classification |
transit |
| Real-time rail delays + delay-aware route planning (ODPT) |
diet |
| National Diet members and full-text proceedings search |
holiday |
| Public holidays + business-day math |
weather |
| JMA forecasts and warnings |
houjin |
| Corporate-number (法人番号) registry — 5.78M corporations, one-call KYB report |
Related MCP server: x402-mcp
How payment works
x402 is a buyer-pays protocol. This MCP server holds your wallet and pays each API call transparently — the agent never sees a payment prompt. Calls cost roughly $0.001–$0.10 each (mostly sub-cent), settled in USDC on Base.
You fund a wallet with a small amount of USDC.
You set
EVM_PRIVATE_KEYto that wallet's key.The server pays as it goes; per-call cost is well under a cent for most tools.
Without EVM_PRIVATE_KEY the server still starts and lists every tool, but a
paid tool call returns a clear "payment not configured" message — nothing is
charged.
Security: the key in
EVM_PRIVATE_KEYcan spend that wallet's funds. Use a dedicated wallet funded with only what you intend to spend — never a primary wallet.
Setup
No install step — npx fetches and runs the server on demand.
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"japan-data": {
"command": "npx",
"args": ["-y", "@mameta/japan-data-mcp"],
"env": {
"EVM_PRIVATE_KEY": "0xYOUR_FUNDED_WALLET_KEY"
}
}
}
}Without EVM_PRIVATE_KEY the server still starts and lists all 28 tools;
the paid tools then return a clear "payments disabled" error instead of
running. Add a USDC-funded wallet key to enable them.
Cursor / Cline
Point the MCP client at npx -y @mameta/japan-data-mcp with the same
EVM_PRIVATE_KEY env var. Transport is stdio.
From source
git clone https://github.com/Mameta29/japan-data-mcp.git
cd japan-data-mcp
npm install && npm run build
# then point the MCP client at: node /abs/path/to/dist/index.jsExample prompts
Once connected, just ask the agent in natural language:
"「東京都千代田区丸の内1-1」を正規化して緯度経度も出して" —
address_normalize+address_geocode"Is tomorrow a public holiday in Japan? If so, when is the next business day?" —
holiday_is_holiday+holiday_add_business_days"山手線いま遅れてる?渋谷から東京駅までの代替ルートは?" —
transit_line_disruptions+transit_alternative_routes"Look up the corporation with corporate number 7010401056220" —
houjin_corporation"国会で「デジタル庁」がいつどの委員会で議論されたか調べて" —
diet_minutes_search
Configuration
Env var | Required | Description |
| for paid tools | Private key of a USDC-funded wallet (Base / Polygon). Paid tools are disabled if absent. |
Development
npm run dev # run from source with tsx
npm run typecheck # tsc --noEmit
npm run build # compile to dist/License
Apache-2.0
Available Tools
28 toolsaddress_geocodeARead-only
Geocode a Japanese address to WGS84 lat/lng coordinates, with a granularity level and confidence score. Japan-only.
Inputs: address (required).
address_normalizeARead-only
Normalize a Japanese address into clean prefecture/city/town/chome components, fixing fullwidth/halfwidth and old-form kanji, and resolving the postal code. Returns a 0-1 confidence score.
Inputs: address (required).
address_parseARead-only
Extract a fully structured Japanese address — including building name, room number, and addressee — from free-form, OCR, or voice-transcribed text.
Inputs: text (required).
address_postal_codeARead-only
Look up Japanese address candidates for a 7-digit postal code (郵便番号), backed by Japan Post KEN_ALL data.
Inputs: zip (required).
address_reverse_geocodeARead-only
Reverse-geocode WGS84 lat/lng coordinates within Japan to a normalized address.
Inputs: lat (required), lng (required).
diet_memberARead-only
Full profile of a Japanese National Diet member by canonical id — party, constituency, committees, positions.
Inputs: id (required).
diet_members_searchARead-only
Search current Japanese National Diet members by name (kanji/kana/romaji), party, house, or constituency.
Inputs: q, house, limit, party, +2 more.
diet_minutes_searchARead-only
Full-text search the official Japanese Diet proceedings archive (国会会議録), filterable by date, house, committee, and speaker.
Inputs: query (required), house, limit, offset, +4 more.
furigana_classifyARead-only
Classify a Japanese string as person_name / company_name / place_name / general / mixed, with a probability and character-type breakdown.
Inputs: text (required).
furigana_convertARead-only
Convert kanji-mixed Japanese text to hiragana, katakana, or romaji, with a per-token reading breakdown.
Inputs: text (required), to.
furigana_name_readingsARead-only
List the possible readings of a Japanese name (person, company, or place), each with a probability — names are ambiguous without context.
Inputs: name (required), name_type.
holiday_add_business_daysARead-only
Add (or subtract) a number of Japanese business days to a date, skipping weekends and public holidays.
Inputs: date (required), business_days (required).
holiday_business_days_betweenARead-only
Count the Japanese business days between two dates (inclusive of neither endpoint by default).
Inputs: to (required), from (required).
holiday_is_holidayARead-only
Classify a Japanese calendar date as a public holiday, weekend, or business day. Backed by official Cabinet Office data.
Inputs: date (required).
holiday_listARead-only
List all Japanese public holidays for a given year.
Inputs: year (required).
houjin_corporationARead-only
Look up one Japanese corporation by its 13-digit corporate number (法人番号), against the National Tax Agency registry.
Inputs: number (required).
houjin_kyb_reportARead-only
One-call KYB report on a Japanese corporation: official registry record, lifecycle status (active/closed), kana + romaji name readings, machine-actionable risk flags, an English summary, and the dataset vintage. Accepts a 13-digit corporate number or a company name. Premium composite ($0.25) — replaces 3-4 separate lookups.
Inputs: city, name, prefecture, corporate_number.
houjin_searchARead-only
Search the Japanese corporate registry by trade name and/or location. Matches Japanese and registered English names.
Inputs: name (required), city, limit, corp_kind, +1 more.
houjin_verifyARead-only
Name-match (名寄せ) a company name plus location against the Japanese corporate registry, returning the most likely corporate number with a confidence score. Closed/dissolved companies are reported as not verified.
Inputs: name (required), address.
transit_alternative_routesARead-only
Suggest delay-aware alternative routes for Japanese train travel — ranked routes that avoid currently-disrupted lines.
Inputs: to (required), from (required).
transit_line_disruptionsBRead-only
Current service disruptions on a specific Japanese train line.
Inputs: line (required).
transit_linesARead-only
Directory of Japanese rail operators and their lines, with canonical ids. Use to discover valid line identifiers.
Inputs: no named parameters.
transit_route_planARead-only
Plan a route between two Japanese train stations with transfers, duration, and fare.
Inputs: to (required), from (required).
transit_stations_searchARead-only
Fuzzy-search Japanese train stations by name (kanji, kana, or romaji).
Inputs: q (required).
transit_station_statusARead-only
Real-time delay and operational status for a Japanese train station, per line, with a bilingual summary. Sourced from ODPT.
Inputs: name (required).
weather_areasARead-only
List the valid JMA region codes and names accepted by the weather tools.
Inputs: no named parameters.
weather_forecastARead-only
Japanese weather forecast for a region — today's conditions, near-term outlook, and a 7-day forecast. Sourced from the JMA.
Inputs: area (required).
weather_warningsARead-only
Active Japanese weather warnings and advisories for a region, from the JMA.
Inputs: area (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 28 tools
Each tool targets a distinct data source or operation, but some overlap exists: transit_route_plan vs transit_alternative_routes both plan routes, and houjin_corporation/search/verify/kyb_report all deal with corporate lookup. However, descriptions clearly differentiate them (e.g., alternative routes are delay-aware; verify returns confidence score).
All tool names follow a clear domain prefix (furigana_, transit_, diet_, holiday_, weather_, houjin_, address_) with snake_case throughout. While some are noun phrases and others verb phrases, the uniform prefix and lowercase underscore convention make the set highly predictable.
28 tools is above the typical well-scoped range, but the server covers seven distinct Japan-related domains (transit, diet, holidays, weather, corporate, address, furigana), each with a focused set of 3-6 tools. The breadth justifies the count, though it feels slightly heavy.
The server covers core operations across all its domains: search, lookup, and some derived actions. Minor gaps exist (e.g., no transit station details beyond status, no diet committee listings, no historical weather), but the surface is broadly coherent and without dead ends.
Maintenance
Related MCP Connectors
Remote MCP server exposing 330 production AI-agent services for web/data processing, validation, AI utilities, blockchain/crypto utilities, and x402 pay-per-use access.
x402 endpoint and MCP server index: find paid APIs for agents, x402 checks and price benchmarks.
Paid deterministic utilities and automation services for AI agents via MCP and x402.
Hosted MCP server for live public-data APIs and Skills for AI agents.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to search, pay for, and call paid APIs using the x402 protocol, with automatic USDC settlement.2MIT- AlicenseNot gradedqualityDmaintenanceMCP server for the x402 protocol that lets AI agents discover and call payment-gated HTTP APIs automatically.223 npmApache 2.0

oom-x402-mcpofficial
FlicenseNot gradedqualityBmaintenanceMCP server exposing 1,000+ pay-per-call API endpoints across agent infrastructure (memory, coordination, secrets, verification), data, compute, finance, weather, geography, and reference categories — payments via x402 protocol in USDC on Base.-- AlicenseNot gradedqualityDmaintenanceMCP server providing raw Japanese regulatory corporate data, including pension headcount logs, statutory financial disclosures, and government procurement records, metered via x402 micro-payments.MIT