# JPVerify (remote · api.jpverify.com)

Japan company, T-number, invoice issuer and address checks for AI agents, paid per call via x402.

- Trust score: 65/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.jpverify.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-jpverify-jpverify/api.md), [page](https://verifymcp.io/servers/com-jpverify-jpverify/api)

## Channel facts

- Endpoint: `https://api.jpverify.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.7.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4758 tokens (~528/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability check failed: schema churn in the 15 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the JPVerify MCP server?

JPVerify is a hosted endpoint at https://api.jpverify.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-jpverify-jpverify 'https://api.jpverify.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-jpverify-jpverify": {
      "url": "https://api.jpverify.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-jpverify-jpverify": {
      "type": "http",
      "url": "https://api.jpverify.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-jpverify-jpverify]
url = "https://api.jpverify.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-jpverify-jpverify": {
      "type": "remote",
      "url": "https://api.jpverify.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-jpverify-jpverify --url 'https://api.jpverify.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-jpverify-jpverify:
    url: "https://api.jpverify.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-jpverify-jpverify": {
      "Transport": "http",
      "Url": "https://api.jpverify.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-jpverify-jpverify -t streamable-http -u 'https://api.jpverify.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-jpverify-jpverify": {
      "type": "http",
      "url": "https://api.jpverify.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 4 to 7.

### 2026-11-18 (score 64, 0)

- [security] Tool “jp_address_normalize” rewrote its description, which is the text the model reads
- [security] Tool “jp_address_validate” rewrote its description, which is the text the model reads
- [security] Tool “jp_company_verify” rewrote its description, which is the text the model reads
- [security] Tool “jp_supplier_resolve” rewrote its description, which is the text the model reads
- [cosmetic] “jp_address_normalize” reworded the description of “address”
- [cosmetic] “jp_address_validate” reworded the description of “address”
- [cosmetic] “jp_company_verify” reworded the description of “address”
- [cosmetic] “jp_company_verify” reworded the description of “name”
- [cosmetic] “jp_supplier_resolve” reworded the description of “name”

### 2026-11-16 (score 64, 0)

- [security] Tool “jp_invoice_issuer_check” rewrote its description, which is the text the model reads
- [cosmetic] “jp_invoice_issuer_check” reworded the description of “supplier_name”

### 2026-11-10 (score 64, 0)

- [security] Tool “jp_address_normalize” rewrote its description, which is the text the model reads
- [security] Tool “jp_company_resolve” rewrote its description, which is the text the model reads

### 2026-11-09 (score 64, 0)

- [security regression] A breaking change shipped without a version bump: still 0.5.0
- [security regression] Tool “jp_entity_resolve” was removed
- [security regression] Tool “jp_business_card_extract” was removed
- [security regression] Tool “jp_invoice_extract” was removed
- [security regression] Tool “jp_invoice_extract_and_verify” was removed
- [security regression] Tool “jp_invoice_issuer_match” was removed
- [security regression] Tool “jp_invoice_issuer_match_extract” was removed
- [security regression] Tool “jp_receipt_extract” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “jp_company_verify” rewrote its description, which is the text the model reads
- [security] Tool “jp_invoice_issuer_check” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 7150 → 4292
- [functional improvement] Schema quality: 7150 → 4168
- [functional] New tool “jp_company_resolve”
- [functional] New tool “jpverify_balance”
- [cosmetic] “jp_invoice_issuer_check” added an optional parameter “expected_corporate_number”
- [cosmetic] “jp_invoice_issuer_check” added an optional parameter “expected_registration_number”
- [cosmetic] “jp_invoice_issuer_check” added an optional parameter “invoice_date”
- [cosmetic] “jp_address_validate” reworded the description of “geocode_evidence”
- [cosmetic] “jp_address_validate” reworded the description of “parsed”
- [cosmetic] “jp_address_validate” reworded the description of “postal_evidence”
- [cosmetic] “jp_company_verify” reworded the description of “address”
- [cosmetic] “jp_company_verify” reworded the description of “name”
- [cosmetic] “jp_invoice_issuer_check” reworded the description of “address”
- [cosmetic] “jp_invoice_issuer_check” reworded the description of “supplier_name”
- [cosmetic] “jp_supplier_resolve” reworded the description of “name”

### 2026-11-08 (score 64, 0)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 0.5.0
- [security regression] Tool “jp_counterparty_check” was removed
- [security] Tool “jp_address_normalize” rewrote its description, which is the text the model reads
- [security] Tool “jp_company_verify” rewrote its description, which is the text the model reads
- [security] Tool “jp_invoice_extract” rewrote its description, which is the text the model reads
- [security] Tool “jp_invoice_extract_and_verify” rewrote its description, which is the text the model reads
- [security] Tool “jp_invoice_registration_verify” rewrote its description, which is the text the model reads
- [security] Tool “jp_supplier_resolve” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 5810 → 7150
- [functional] New tool “jp_entity_resolve”
- [functional] New tool “jp_invoice_issuer_match”
- [functional] New tool “jp_invoice_issuer_match_extract”
- [cosmetic] “jp_supplier_resolve” reworded the description of “country_code”

### 2026-11-07 (score 64, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “jp_business_card_extract” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 379 → 484
- [functional regression] Schema quality: 379 → 480
- [functional improvement] Tool coverage: 51% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [cosmetic] “jp_address_normalize” reworded the description of “address”
- [cosmetic] “jp_address_normalize” reworded the description of “response_language”
- [cosmetic] “jp_address_validate” reworded the description of “address”
- [cosmetic] “jp_address_validate” reworded the description of “geocode_evidence”
- [cosmetic] “jp_address_validate” reworded the description of “parsed”
- [cosmetic] “jp_address_validate” reworded the description of “postal_evidence”
- [cosmetic] “jp_address_validate” reworded the description of “required_level”
- [cosmetic] “jp_address_validate” reworded the description of “strict”
- [cosmetic] “jp_business_card_extract” reworded the description of “back_image_url”
- [cosmetic] “jp_business_card_extract” reworded the description of “front_image_url”
- [cosmetic] “jp_business_card_extract” reworded the description of “max_pages”
- [cosmetic] “jp_company_verify” reworded the description of “address”
- [cosmetic] “jp_company_verify” reworded the description of “corporate_number”
- [cosmetic] “jp_company_verify” reworded the description of “name”
- [cosmetic] “jp_company_verify” reworded the description of “response_language”
- [cosmetic] “jp_counterparty_check” reworded the description of “country_code”
- [cosmetic] “jp_counterparty_check” reworded the description of “name”
- [cosmetic] “jp_counterparty_check” reworded the description of “participant_id”
- [cosmetic] “jp_counterparty_check” reworded the description of “response_language”
- [cosmetic] “jp_counterparty_check” reworded the description of “vat_id”
- [cosmetic] “jp_invoice_issuer_check” reworded the description of “address”
- [cosmetic] “jp_invoice_issuer_check” reworded the description of “registration_number”
- [cosmetic] “jp_invoice_issuer_check” reworded the description of “response_language”
- [cosmetic] “jp_invoice_issuer_check” reworded the description of “supplier_name”
- [cosmetic] “jp_supplier_resolve” reworded the description of “address”
- [cosmetic] “jp_supplier_resolve” reworded the description of “corporate_number”
- [cosmetic] “jp_supplier_resolve” reworded the description of “country_code”
- [cosmetic] “jp_supplier_resolve” reworded the description of “identifiers”
- [cosmetic] “jp_supplier_resolve” reworded the description of “name”
- [cosmetic] “jp_supplier_resolve” reworded the description of “registration_number”
- [cosmetic] “jp_supplier_resolve” reworded the description of “response_language”
- [cosmetic] “jp_supplier_resolve” reworded the description of “t_number”

### 2026-11-06 (score 61)

First indexed and scored.

## MCP tools (9)

### `jpverify_guide` (~127 tokens)

JPVerify guide (free)

Free. Returns the JPVerify tool catalog with prices, use_when guidance and example inputs, plus how x402 payment works; pass a natural-language question to get the single recommended tool and suggested input. / 無料。JPVerifyのツール一覧（料金・用途・入力例）とx402決済方法を返します。質問を渡すと最適なツールと入力例を返します。

Input parameters:

- `question` (string): Optional task description, e.g. 'Is T1013301046627 a valid invoice number?' / 任意の質問。

### `jpverify_balance` (~101 tokens)

API key credit balance (free)

Free. Returns the prepaid credit balance (free and paid parts) of the account whose API key this MCP connection uses, plus the top-up URL. Use when: before a large batch, or after an insufficient_credits error. Connections without an API key (x402) have no balance. / 無料。このMCP接続のAPIキーのアカウント残高（無料分・購入分）とチャージURLを返します。

### `jp_company_verify` (~541 tokens)

Verify Japanese company

Verify a Japanese company by its registered name — Japanese, registered English (NTA, EDINET, GLEIF) or romanized — or 13-digit corporate number (法人番号) against the NTA registry; an address (Japanese or romanized) is comparison evidence only. Returns the Japanese legal name plus a sourced English name and address. For a brand, trade or short name, use jp_company_resolve. Use when: You need a Japanese company or corporate-number lookup. Returns: Corporate number, registered Japanese legal name (legal_name_ja) and address, English name (NTA official, EDINET, or romanized reading) and English address (official or Japan Post romanization) with their sources, active or closed status, and match evidence. Price: $0.01 USDC per successful call, paid with x402 on Base. / 登記名（日本語・登録英文名・ローマ字）または法人番号を国税庁の法人番号公表データと照合します。住所（日本語・ローマ字）は比較用の根拠です。ブランド名・通称は jp_company_resolve を使用してください。 用途: 日本企業または法人番号を検索・照合したい場合。 返却: 法人番号、登記上の法人名（legal_name_ja）・住所、英語名（国税庁公式・EDINET・読みのローマ字）と英語住所（公式または日本郵便ローマ字）とその出典、活動状態、一致根拠を返します。 料金: 成功した呼び出し1回あたり $0.01 USDC（Base上のx402決済）。

Input parameters:

- `address`: Optional address in Japan, Japanese or romanized, compared with the registered address; it cannot identify a company alone. / 任意の所在地（日本語・ローマ字）。登記住所と比較。
- `corporate_number`: 13-digit Japanese corporate number (法人番号), digits only. / 13桁の法人番号（数字のみ）。
- `name`: Registered company name: Japanese (任天堂株式会社), registered English (Nintendo Co., Ltd.) or romanized. For brand or short names use companies/resolve. / 登記名（日本語・登録英文名・ローマ字）。
- `response_language` (string): Response presentation language: ja, en, or both. / レスポンス表示言語: ja（日本語）、en（英語）、both（両方）。

### `jp_invoice_registration_verify` (~354 tokens)

Verify T-number (qualified invoice)

Verify a Japanese qualified-invoice registration number (T + 13 digits) against the NTA invoice registry; returns the registered name with a sourced English name and address. Use when: You already have a Japanese T+13-digit qualified-invoice registration number. Returns: NTA registration status, corporate number, registered name, and relevant dates. Price: $0.01 USDC per successful call, paid with x402 on Base. / 適格請求書発行事業者登録番号（T+13桁）を国税庁データと照合します。 用途: 日本のT+13桁インボイス登録番号が既にある場合。 返却: 国税庁の登録状態、法人番号、登録名、関連日付を返します。 料金: 成功した呼び出し1回あたり $0.01 USDC（Base上のx402決済）。

Input parameters:

- `registration_number` (string, required): T plus 13 digits; spaces, hyphens, and lowercase t are normalized. Shape-invalid input is rejected before payment; checksum-invalid or registry-not-found values are paid business results. / Tに続く13桁の数…
- `response_language` (string): Response presentation language: ja, en, or both. / レスポンス表示言語: ja（日本語）、en（英語）、both（両方）。

### `jp_invoice_issuer_check` (~822 tokens)

Check invoice issuer

Check a T-number against the issuer name on the invoice (Japanese or English), the address (optional), the invoice date (optional: registered on that date, not cancelled or expired) and your supplier master number (optional: expected_registration_number or expected_corporate_number), using Japan's NTA registries. JPVerify does not read invoice files. Use when: You have a T-number and the issuer name from an invoice (address and invoice date optional) and need to know whether they belong together and the issuer was registered on the invoice date. Returns: Registry fields, issuer name and address comparison, registration on the invoice date, supplier master comparison, and one status per check in check_results. Price: $0.05 USDC per successful call, paid with x402 on Base. / T番号を請求書の発行者名（日本語・英語）・住所（任意）・日付（任意。その日に登録済みで取消・失効前か）・仕入先マスターの番号（任意）と国税庁データで照合します。ファイルの読み取りは行いません。 用途: 請求書のT番号と発行者名（住所・日付は任意）が一致するか、請求書の日付時点で登録済みかを確認したい場合。 返却: 国税庁の登録情報、発行者名・住所の比較結果、請求書日付時点の登録状況、確認項目ごとの結果を返します。 料金: 成功した呼び出し1回あたり $0.05 USDC（Base上のx402決済）。

Input parameters:

- `address`: Optional issuer address as printed on the invoice, compared with the registry address. / 請求書に記載された発行者住所（任意）。登記住所と比較します。
- `expected_corporate_number`: Optional 13-digit corporate number of this supplier from your own supplier master data; compared with the corporate number registered for the T-number. / 仕入先マスターに登録済みの法人番号（任意）。T番号の登録上の法人番号と比較します。
- `expected_registration_number`: Optional T-number of this supplier from your own supplier master data (not from the invoice). A different invoice T-number means the invoice may come from another company. / 仕入先マスターに登録済みのT番号（任意。請求書の値…
- `invoice_date`: Optional invoice (transaction) date, YYYY-MM-DD: checks that the issuer was registered on that date and not yet cancelled or expired. / 請求書の取引年月日（任意）。その日に登録済みで、取消・失効前かを確認します。
- `registration_number` (string, required): Qualified-invoice registration number: T followed by 13 digits, e.g. T1013301046627. / 適格請求書発行事業者登録番号（T＋13桁）。
- `response_language` (string): Response presentation language: ja, en, or both. / レスポンス表示言語: ja（日本語）、en（英語）、both（両方）。
- `supplier_name`: Issuer name as printed on the invoice, in Japanese or English. Japanese is compared with the registered name of the T-number; English with the official English name (NTA, EDINET, GLEIF) or the romani…

### `jp_address_normalize` (~530 tokens)

Normalize Japanese address

Standard form of a Japanese address, given in Japanese or romanized: canonical hierarchy (prefecture to room), completed town, postal-master consistency and an English rendering from Japan Post romanized data. No coordinates and no final decision (use jp_address_validate). Accepts business-specific postal codes (e.g. 100-8310) and parcel (番地) addresses. Use when: You need Japanese address normalization or standardization, whether or not the input contains a postal code. Returns: Standard written form: normalized components, a unique truncated town completed, an English address from Japan Post romanization, and postal-master consistency and candidates. It does not infer a missing postal code, return coordinates (geocode) or give a final decision (validate). Price: $0.005 USDC per successful call, paid with x402 on Base. / 日本語・ローマ字の日本住所を標準表記にします。都道府県から部屋番号までの階層、町名補完、郵便データとの整合、日本郵便ローマ字の英語表記。座標と最終判定は返しません（判定は jp_address_validate）。事業所の個別郵便番号（例: 100-8310）と地番（番地）住所にも対応します。 用途: 入力に郵便番号があってもなくても、日本住所を正規化・標準化したい場合。 返却: 標準表記：正規化した構成要素、一意な町名の補完、日本郵便ローマ字の英語住所、郵便データとの整合と候補。未入力の郵便番号は推定せず、座標（geocode）と最終判定（validate）は返しません。 料金: 成功した呼び出し1回あたり $0.005 USDC（Base上のx402決済）。

Input parameters:

- `address` (string, required): Postal address in Japan, in Japanese or romanized (1-9-1 Marunouchi, Chiyoda-ku, Tokyo). Not a blockchain wallet address. Postal code optional. / 日本国内の住所（日本語・ローマ字）。ウォレット不可。郵便番号は任意。
- `response_language` (string): Response presentation language: ja, en, or both. / レスポンス表示言語: ja（日本語）、en（英語）、both（両方）。

### `jp_address_validate` (~606 tokens)

Validate Japanese address

Decide whether a Japanese address (Japanese or romanized) holds at the level you need, from parser, postal and geocoder evidence: exact/partial/ambiguous/conflict/unverified with reasons. Use when: You need one evidence-based Japanese address quality decision combining parsed address, postal evidence, and geocoder evidence. Returns: Exact, partial, ambiguous, conflict, or unverified status with accepted hierarchy, confidence signals, validation scope, and reasons. Price: $0.005 USDC per successful call, paid with x402 on Base. / 日本住所（日本語・ローマ字）が必要な階層で成立するかを、解析・郵便番号・ジオコーディングの根拠から判定します。 用途: 解析住所、郵便番号根拠、ジオコーダー根拠を統一ルールで判定したい場合。 返却: 完全一致、部分一致、候補不一意、矛盾、未検証の状態に加え、採用階層、信頼度、判定範囲、理由を返します。 料金: 成功した呼び出し1回あたり $0.005 USDC（Base上のx402決済）。

Input parameters:

- `address`: Postal address in Japan, in Japanese or romanized (1-9-1 Marunouchi, Chiyoda-ku, Tokyo). Not a blockchain wallet address. Give address or parsed. / 日本国内の住所（日本語・ローマ字）。ウォレット不可。addressかparsedの一方。
- `geocode_evidence`: Optional prior output from /v1/jp/addresses/geocode; candidates and statuses are advisory and recomputed locally. / 任意のgeocode出力。候補とstatusは補助情報で、ローカルで再計算されます。
- `parsed`: Output from /v1/jp/addresses/parse or normalize containing at least one non-empty address component. / parseまたはnormalizeの出力。空でない住所構成要素を1つ以上含めます。
- `postal_evidence`: Optional prior output from /v1/jp/postal-codes/lookup; status/confidence are recomputed and not trusted. / 任意のpostal-lookup出力。statusとconfidenceは再計算され、無条件には信頼されません。
- `required_level`: Required hierarchy level; Jageocoder 5/6=oaza/aza, 7=block, 8=building/house node. / 必須階層。Jageocoderの5/6=大字・字、7=街区、8=建物・号ノード。
- `strict` (boolean): Require all supplied evidence to agree. / 入力された根拠の完全一致を要求。

### `jp_supplier_resolve` (~721 tokens)

Resolve Japanese supplier

Supplier onboarding decision combining company, qualified-invoice and address evidence (registered names in Japanese or English), with cross-checks no single lookup makes: corporate-number agreement, company versus invoice registration state, FSA licences held. Use when: You need one coverage-aware supplier check combining company, qualified-invoice, and address evidence; optionally includes projected gBizINFO activity evidence when the internal feature flag is enabled. Returns: Independent evidence checks, source versions, and a resolved/ambiguous/not-found/insufficient-coverage status; optional gBizINFO is projected enrichment inside this response, not a standalone source or raw-response resale. Not a legal or KYB determination. Price: $0.10 USDC per successful call, paid with x402 on Base. / 会社・適格請求書・住所の根拠（登記名は日本語・英語）をまとめて仕入先を判定し、法人番号の一致、会社と登録番号の状態の整合、金融庁の免許を横断確認します。 用途: 会社、適格請求書、住所の根拠を組み合わせ、必要に応じて内部機能フラグでgBizINFO活動根拠も付加した、対象範囲を明示した仕入先確認を行う場合。 返却: 個別の根拠チェック、ソース版、resolved/ambiguous/not-found/insufficient-coverage状態を返します。任意のgBizINFOはこのレスポンス内の加工済み補助根拠であり、単独ソースや原レスポンスの再販ではありません。法的判断やKYB判定ではありません。 料金: 成功した呼び出し1回あたり $0.10 USDC（Base上のx402決済）。

Input parameters:

- `address`: Supplier address, used as supporting evidence. / 仕入先住所（補助根拠）。
- `corporate_number`: 13-digit Japanese corporate number (法人番号), digits only. / 13桁の法人番号（数字のみ）。
- `country_code` (string): Supplier country. Only JP is supported (GB was retired on 2026-11-08). / 仕入先の国。JPのみ対応（GBは2026-11-08に終了）。
- `identifiers`: Optional extra identifiers; allowed keys: corporate_number, registration_number, t_number, company_number, lei. / 追加識別子（任意）。使用可能なキー：corporate_number、registration_number、t_number、company_number、lei。
- `name`: Registered company name: Japanese (任天堂株式会社), registered English (Nintendo Co., Ltd.) or romanized. For brand or short names use companies/resolve. / 登記名（日本語・登録英文名・ローマ字）。
- `registration_number`: Supplier qualified-invoice registration number (T + 13 digits). / 仕入先の適格請求書登録番号（T＋13桁）。
- `response_language` (string): Response presentation language: ja, en, or both. / レスポンス表示言語: ja（日本語）、en（英語）、both（両方）。
- `t_number`: Alias of registration_number (T + 13 digits). / registration_numberの別名（T＋13桁）。

### `jp_company_resolve` (~803 tokens)

Resolve Japanese entity from English name or identifier

Find the Japanese legal entity from an English or brand name (e.g. au -> KDDI), English address, website or e-mail domain, T-number, corporate number, LEI or securities code; results in English. Brand matches are candidates, never a confirmation. Use when: You hold an English, brand or romanized Japanese company name, an English address or postal code, a website or e-mail domain, a T-number, corporate number, LEI or securities code and need the Japanese legal entity, in English. Returns: Decision (matched / likely_match / candidates), legally binding Japanese name, kana, English name with source, contract party name, status and qualified-invoice registration. Brand names (au, MOS Burger) find the owner as candidates; listing, Wikidata prominence and gBizINFO employee counts only order candidates. Price: $0.25 USDC per successful call, paid with x402 on Base. / 英語名・ブランド名（例: au→KDDI）・英語住所・ドメイン・T番号・法人番号・LEI・証券コードから日本の法人を特定します。ブランド名の一致は候補であり、確定ではありません。 用途: 英語名・ブランド名・ローマ字・英語住所・郵便番号・Webサイト／メールのドメイン・T番号・法人番号・LEI・証券コードから日本の法人を特定したい場合。 返却: 判定、正式な日本語商号、読み、出典付き英語名、契約当事者名、状態、適格請求書登録を返します。ブランド名（au、MOS Burger）からは所有企業を候補として返し、上場・Wikidataの知名度・Gビズインフォの従業員数は候補の並び順だけに使います。 料金: 成功した呼び出し1回あたり $0.25 USDC（Base上のx402決済）。

Input parameters:

- `address`: Address in English or Japanese, e.g. 1-10-1 Higashikotari, Nagaokakyo-shi, Kyoto. Postal code, prefecture, municipality and town are compared with each candidate's registered address. / 住所（英語・日本語）。郵便…
- `corporate_number`: 13-digit corporate number (法人番号); the check digit is verified.
- `duns`: D-U-N-S number; echoed only and never verified.
- `email`: A contact e-mail at the company; only its domain is used, and free webmail domains are ignored. The address itself is not stored. / 企業のメールアドレス（ドメインのみ使用）。
- `lei`: Legal Entity Identifier (20 characters).
- `max_candidates` (integer): Maximum candidates returned for a name search.
- `name`: English, romanized or Japanese company name. / 会社名（英語・ローマ字・日本語）。
- `postal_code`: Japanese postal code, e.g. 100-0005. / 郵便番号。
- `prefecture`: Prefecture in English or Japanese, e.g. Tokyo, Osaka-fu, 京都府. / 都道府県。
- `securities_code`: Japanese securities code, e.g. 6981. / 証券コード。
- `t_number`: Qualified invoice registration number, T + 13 digits (登録番号); the check digit is verified.
- `website`: Company website, e.g. https://www.example.co.jp; its domain is compared with the official websites we know (Wikidata). / 企業のWebサイト。

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-jpverify-jpverify/api#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 64
- 2026-11-16: 64
- 2026-11-15: 64
- 2026-11-14: 64
- 2026-11-13: 64
- 2026-11-12: 64
- 2026-11-11: 64
- 2026-11-10: 64
- 2026-11-09: 64
- 2026-11-08: 64
- 2026-11-07: 64
- 2026-11-06: 61

## Common questions

### What is the JPVerify MCP server?

JPVerify is an MCP server listed in the public MCP registry as com.jpverify/jpverify. Japan company, T-number, invoice issuer and address checks for AI agents, paid per call via x402. This page covers its hosted endpoint (https://api.jpverify.com/mcp).

### Is the JPVerify MCP server safe to use?

JPVerify scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the JPVerify MCP server expose?

JPVerify exposes 9 tools: jpverify_guide, jpverify_balance, jp_company_verify, jp_invoice_registration_verify, jp_invoice_issuer_check, and 4 more. Their descriptions and schemas cost roughly 4,605 tokens of context every time the server is loaded.

### Does the JPVerify MCP server require authentication?

No. We connected to JPVerify without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the JPVerify MCP server still maintained?

JPVerify is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the JPVerify MCP server?

VerifyMCP ran 12 checks on JPVerify, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about JPVerify: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.jpverify.com/mcp
- Repository: https://github.com/japanverify/jpverify-mcp
- Website: https://www.jpverify.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-jpverify-jpverify/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-jpverify-jpverify/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-jpverify-jpverify/api.json
- HTML version of this page: https://verifymcp.io/servers/com-jpverify-jpverify/api
