MCP Tools Directory
← Browse integrations

Developer tools

Japan Data MCP

Free account · sign-in required

Contact Japan Data MCP

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

30 tools for Japanese data: address, furigana, transit, Diet, holidays, weather, corporate registry

Transport
stdio
Authentication
unknown
Initial setup
credentials
Runtime
unattended
Evidence
documented
Version
1.1.0
Package
@mameta/japan-data-mcp
Last compatibility test
Not independently tested

Connect your agent

@mameta/japan-data-mcp

Publisher documentation and package manifest were reviewed. EVM_PRIVATE_KEY is a wallet signing secret with spending authority, which does not fit the native authentication taxonomy; use a dedicated limited-funds wallet. The package, wallet flow, and APIs were not executed or independently security-audited.

Capabilities: Query Japanese address, furigana, transit, parliamentary, holiday, weather, and corporate datasets, Settle supported API calls through x402

Connected profiles

Additional details

Registry identifier

io.github.Mameta29/japan-data-mcp

Source ↗ · Checked 2026-09-17
Published version

1.1.0

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Source artifact

@mameta/japan-data-mcp

Source ↗ · Checked 2026-09-19
Source manifest version

1.2.0

Source ↗ · Checked 2026-09-19
Unattended configuration

Node.js 20+ stdio server launched on demand with npx; it starts without a wallet key but paid calls remain disabled until configured.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

Authentication is classified unknown because access uses EVM_PRIVATE_KEY as an x402 payment-signing wallet credential, not a conventional API key, OAuth flow, or client credential.

Source ↗ · Checked 2026-09-19
Connection configuration

Configure the MCP client to run npx -y @mameta/japan-data-mcp and set EVM_PRIVATE_KEY only when paid calls are intended.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19