JP-Verify MCP server

jp-verify-mcp

<!-- mcp-name: xyz.obolpay/jp-verify -->

An MCP server for JP-Verify, the English-first API that verifies Japanese companies: qualified-invoice registration numbers (T-numbers), Corporate Numbers (法人番号), English names and major shareholders.

It is a thin client. Each tool call is one HTTPS request to JP-Verify's public API at https://jp-verify.obolpay.xyz. The package holds no register data and contacts no other site; it downloads nothing from the National Tax Agency or from EDINET.

Tools

All four are read-only. Each answered call (HTTP 200) is one metered lookup on your JP-Verify plan; the batch tool counts one per well-formed number. verifyjapanesecompany and getmajorshareholders reject a number that fails JP-Verify's own format or check-digit rule locally, without a call; the batch tool sends the list as given and JP-Verify lists such numbers under invalid, free of charge.

Every result has two parts:

disclaimers and the attribution strings;

• jpverifyresponse: JP-Verify's answer exactly as sent, including dataasof, notes,

the quota headers (limit, remaining, resets_at) and where the data comes from.

• metadata: the endpoint, the HTTP status, whether an API key or the key-less sandbox was used,

HTTP errors (400, 401, 404, 429, 503, 5xx) and network failures come back as tool errors with a one-line explanation. JP-Verify does not charge for 400, 401, 404, 429 or 503 answers.

Install and run

Requires Python 3.10 or later.

uvx jp-verify-mcp                # or: pip install jp-verify-mcp && jp-verify-mcp

From a source checkout: pip install ., then jp-verify-mcp.

stdio (default)

For Claude Desktop, Claude Code (.mcp.json), Cursor and other clients that start a local server:

{
  "mcpServers": {
    "jp-verify": {
      "command": "uvx",
      "args": ["jp-verify-mcp"],
      "env": { "JPVERIFY_API_KEY": "your key (optional)" }
    }
  }
}

Leave out env to use the key-less sandbox.

Streamable HTTP

jp-verify-mcp --transport streamable-http --host 127.0.0.1 --port 8000
# endpoint: http://127.0.0.1:8000/mcp  (stateless, JSON responses)

call only and takes precedence over JPVERIFYAPIKEY.

• A client may send its own key in an X-API-Key header. It is forwarded to JP-Verify for that

--allowed-host your.host.name (repeatable).

• A loopback bind gets DNS-rebinding protection automatically. For a public host name pass

every caller without its own key would use it. Pass --allow-shared-key if that is intended.

• On a non-loopback address the server refuses to start while JPVERIFYAPIKEY is set, because

host's allowance.

• The sandbox allowance is per IP address, so key-less callers of a hosted endpoint share the

Configuration

Shortened. The full README is on GitHub.