Odel
jp m2m mcp

jp m2m mcp

@kodandyData & AnalyticsMITUpdated 1w ago

Raw Japanese regulatory data for AI agents: pension, gazette, gBizINFO. x402-metered (USDC).

Server endpointStreamable HTTP

This is the third-party server itself — Odel doesn't run it. Hitting this URL directly talks straight to the upstream server with no auth or proxying. Connect through Odel to front it with managed auth.

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.

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

ToolDatasetPrice
list_company_datasetsCatalog lookup for one corporate numberFree
get_pension_headcount_logJapan Pension Service monthly insured-headcount raw log (month-over-month deltas)0.05 USDC / call
get_gazette_financialsOfficial Gazette (官報) statutory financial disclosures, raw text blocks0.05 USDC / call
get_government_recordsgBizINFO procurement / subsidy / certification raw log0.05 USDC / call

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