Skip to main content
Glama

jp-verify-mcp

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

Tool

JP-Verify endpoint

Returns

verify_japanese_company

GET /v1/verify

Registration status and dates, Corporate Number, Japanese name and address, English name and address (labelled official or machine-romanised)

verify_japanese_companies_batch

POST /v1/verify

The same for many numbers: up to 100 per call on the sandbox and Starter keys, 500 on Growth, 1,000 on Reseller. Malformed numbers are listed under invalid and not charged

get_major_shareholders

GET /v1/shareholders

The 「大株主の状況」 (major shareholders) table from a company's securities report on EDINET, or a no_public_disclosure statement. Optional as_of (YYYY-MM-DD)

find_japanese_company_by_name

GET /v1/resolve

Candidate Corporate Numbers for a company name (rule-based exact matching, not fuzzy search)

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. verify_japanese_company and get_major_shareholders 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:

  • jp_verify_response: JP-Verify's answer exactly as sent, including data_as_of, notes, disclaimers and the attribution strings;

  • metadata: the endpoint, the HTTP status, whether an API key or the key-less sandbox was used, the quota headers (limit, remaining, resets_at) and where the data comes from.

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.

Related MCP server: irkumo-mcp

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)
  • A client may send its own key in an X-API-Key header. It is forwarded to JP-Verify for that call only and takes precedence over JPVERIFY_API_KEY.

  • A loopback bind gets DNS-rebinding protection automatically. For a public host name pass --allowed-host your.host.name (repeatable).

  • On a non-loopback address the server refuses to start while JPVERIFY_API_KEY is set, because every caller without its own key would use it. Pass --allow-shared-key if that is intended.

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

Configuration

Variable

Default

Meaning

JPVERIFY_API_KEY

unset

Your JP-Verify API key, sent as X-API-Key. Unset: the key-less sandbox

JPVERIFY_BASE_URL

https://jp-verify.obolpay.xyz

API origin. Plain http:// is accepted only for localhost

JPVERIFY_TIMEOUT

20

Seconds per request (at most 120)

Other options: jp-verify-mcp --help.

Keys and plans

Data, sources and attribution

  • Registration status, Corporate Number and Japanese name and address come from data published by Japan's National Tax Agency (国税庁): 国税庁適格請求書発行事業者公表サイト (qualified invoice issuers) and 国税庁法人番号公表サイト (Corporate Numbers), mirrored and processed by JP-Verify. They are not produced or guaranteed by the National Tax Agency.

  • English names: official-en where the company filed an English name with the Corporate Number register; otherwise generated, a machine romanisation that is not authoritative. Most companies have not filed one.

  • Sole proprietors: number, status and dates only. No name or address is returned.

  • Major shareholders: the 「大株主の状況」 tables companies file on the FSA's EDINET, extracted by JP-Verify. Organisations are named; every other holder, including every individual, is reported without a name, normally as an aggregate (always on the sandbox). Only companies that file a 有価証券報告書 or 半期報告書 publish this table; for any other company JP-Verify returns no_public_disclosure, a statement of why nothing is published (not a claim that the company has no shareholders). Some filers may show not_yet_available while JP-Verify's ingest catches up. JP-Verify switches this route on separately (its /health reports major_shareholders.enabled); until then the tool answers route_not_enabled.

  • JP-Verify may add the FSA's EDINET code list (PDL1.0) and GLEIF LEI data (CC0 1.0) to a result.

  • When you republish data from a response, keep its attribution strings and *_register blocks (JP-Verify Terms, Article 5).

  • These are register facts as of the dates each response states. They are not tax, legal, investment or ownership advice. JP-Verify answers 503 rather than serve data older than its freshness window.

Privacy

The server sends JP-Verify only what a tool is asked about (numbers, a name, a date) and the API key, if any. It stores nothing, keeps no cache, never retries a call and adds no logging of its own; at the default log level (WARNING) request contents are not logged. JP-Verify's privacy statement: https://jp-verify.obolpay.xyz/v1/privacy. Terms: https://jp-verify.obolpay.xyz/terms.

Development

python3 -m venv .venv && .venv/bin/pip install -e '.[test]'
.venv/bin/python -m pytest

The tests never reach JP-Verify: HTTP is mocked, or answered by a stand-in on 127.0.0.1.

Company and contact

Yanagi the First Co., Ltd. (株式会社ヤナギtheファースト) · yanagithefirst11@gmail.com · https://jp-verify.obolpay.xyz

License

MIT, for this client. Use of the JP-Verify service is governed by its Terms of Service.

Registry

Official MCP Registry name: xyz.obolpay/jp-verify. Source: https://github.com/Hiroshi-Ichiyanagi/jp-verify-mcp

Available Tools

4 tools
find_japanese_company_by_nameFind a Japanese company by nameA
Read-only

Find candidate Corporate Numbers (法人番号) for a Japanese company name (kanji, kana, romaji or the company's registered English name) with JP-Verify's deterministic matching (rule-based exact keys, not fuzzy search). Candidates carry prefecture and city to tell same-name companies apart; a name match is not proof of identity, so confirm the candidate, then call verify_japanese_company. Corporations only. One metered lookup; an empty candidate list is a valid answer.

Inputs: name (required), limit.

get_major_shareholdersMajor shareholders of a Japanese companyA
Read-only

Major shareholders (「大株主の状況」, about the ten largest holders) that a Japanese company published in its annual or semi-annual securities report on EDINET, from JP-Verify, by Corporate Number. Holders are named only when they are organisations; other holders are reported without names, normally as an aggregate (count and combined ratio). A company that files no such report gets status no_public_disclosure: a statement of why nothing is published, not a claim that it has no shareholders. Facts as filed at the filing's basis date; not an ownership or control determination. One metered lookup. If JP-Verify has not enabled this route yet, the tool says so.

Inputs: corporate_number (required), as_of.

verify_japanese_companies_batchVerify many Japanese companiesA
Read-only

The same check as verify_japanese_company for many numbers in one call: up to 100 per call on the key-less sandbox and Starter keys, 500 on Growth, 1,000 on Reseller. Malformed or mistyped numbers come back under invalid and are not charged; each well-formed number is one metered lookup. Large batches give large outputs. Source: the National Tax Agency's published data as served by JP-Verify (attribution kept). Not tax advice.

Inputs: numbers (required).

verify_japanese_companyVerify a Japanese companyA
Read-only

Check a Japanese business in JP-Verify by its qualified-invoice registration number (T + 13 digits) or its 13-digit Corporate Number (法人番号). Returns the invoice-registration status (registered, expired, revoked or not_registered) with its dates, the Corporate Number, and for companies the Japanese name and address with an English rendering (name_en_source 'official-en' = filed by the company; 'generated' = machine romanisation, not authoritative). Sole proprietors: number, status and dates only. Source: the National Tax Agency's published data as served by JP-Verify; JP-Verify's attribution and data_as_of fields are kept as sent. Not tax advice. One metered lookup; a malformed or mistyped number is rejected without a call.

Inputs: number (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: single verification, batch verification, shareholder lookup, and name-to-number resolution. The single-vs-batch pair is explicitly differentiated by input cardinality and pricing limits, so there is no realistic misselection.

    Naming Consistency5/5

    All names use consistent snake_case with a verb_noun structure (verify_..., get_..., find_...). The only deviation is pluralization in verify_japanese_companies_batch, which is natural and readable rather than inconsistent.

    Tool Count5/5

    Four focused tools fit a narrow verification domain well; each earns its place with no redundant surface. The single/batch split is justified by the metered per-lookup pricing model.

    Completeness4/5

    The surface covers the core lifecycle: resolve a name to a number, verify registration/invoice status, batch-verify, and retrieve shareholders. Minor gaps remain (no richer company profile or historical status-change endpoint), but the primary workflows have no dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying the Japanese corporate registry from METI's gBizINFO for company profiles, government procurement, subsidies, patents, certifications, financials, and workplace disclosures using corporate numbers or names.
      95 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to look up verified investor relations page URLs and earnings release (kessan tanshin) URLs for 3,821 Japanese listed companies by securities code, company name, former or brand name, and to fetch selected company attributes. Also supports retrieving monthly change data, checking credit balance and expiry, and inspecting available field definitions.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to identify Japanese companies by name, look up corporate numbers, addresses, and qualified invoice registration status, and batch-match company lists using read-only tools.
      4
      60 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server lets users resolve Japanese company names, verify corporate numbers and qualified-invoice registrations, fetch company profiles, normalize Japanese addresses, and answer Japanese holiday and business-day questions.
      297 npm
      MIT