JP Raw M2M Data Gateway — MCP Server

Remote MCP (Model Context Protocol) server exposing raw Japanese regulatory corporate data to AI agents, metered per call with the x402 payment protocol.

• MCP endpoint (Streamable HTTP, stateless): https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp
• Machine index: llms.txt · API contract: openapi.yaml · Catalog: JSON-LD dataset pages

Unlike generic corporate registries, this gateway serves un-aggregated, regulatory-enforced raw logs for Japanese companies, keyed by the 13-digit corporate number (法人番号):

Connect

Listed on Smithery and the official MCP Registry (io.github.kodandy/jp-m2m-gateway).

Claude Code:

claude mcp add --transport http jp-m2m https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp

Generic MCP client configuration:

{
  "mcpServers": {
    "jp-m2m": {
      "type": "streamable-http",
      "url": "https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp"
    }
  }
}

No API key and no initialize handshake required — the server is stateless; tools/call works directly.

How payment works (x402)

Paid tools return a structured HTTP 402 payment challenge instead of data:

{
  "status": 402,
  "error": "Payment Required",
  "dataset": "pension",
  "amount_usdc": 0.05,
  "x402": { "header": "X-402-Payment-Required", "descriptor": "usdc_request_mock_v1_base_…" },
  "resource": "https://…/v1/companies/{corporate_id}/pension",
  "how_to_pay": "Settle 0.05 USDC via x402, then retry the resource with an X-PAYMENT header."
}

Per-resource descriptors are stable. x402 settlement (USDC on Base, testnet first) is being enabled during the current private beta; agents that send X-PAYMENT retries are prioritized for access.

Notes

• Machine-to-machine only. Human/browser UX is intentionally not provided — browsers receive a plain-text 402 by design.
• Status: closed private beta. Endpoints, pricing and datasets may change.
• Source of the gateway lives in a private repository; this repo hosts the public MCP server documentation and registry manifest.

License

MIT