mcpbeat Sign in

JPVerify MCP Server

answering

JPVerify is answering right now. Last checked 6 min ago. It exposes 15 tools. Last commit 7 Nov 2026.

Japan company, T-number, address and invoice/receipt/card OCR checks, paid per call via x402.

Uptime history 23 hours of history
23 hours agonow
100.0%
Uptime 24h
85 of 85 checks
15
Tools
read from the server
879 ms
Response time
average over 24h
0
Stars
last commit 7 Nov 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 November 2026. No other catalogue keeps this.

7 Nov 3 tools appeared jp_entity_resolve, jp_invoice_issuer_match, jp_invoice_issuer_match_extract
7 Nov the owner changed

Nothing serious here today

Today is the operative word: we check JPVerify every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add jpverify --transport http https://api.jpverify.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.jpverify.com/mcp
~/.codex/config.toml
[mcp_servers.jpverify]
url = "https://api.jpverify.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "jpverify": {
      "url": "https://api.jpverify.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "jpverify": {
      "type": "http",
      "url": "https://api.jpverify.com/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

invoice
jp_invoice_extract
OCR a Japanese billing invoice (text, HTTPS file URL, or small Base64) with local date, tax, arithmetic and T-number checks; no registry lookup. Use when: You need Japanese billing-invoice OCR and deterministic quality checks without registry lookup. Returns: OCR-derived invoice fields plus format, arithmetic, tax, completeness, and review status. Price: $0.01 USDC per successful call, paid with x402 on Base. / 日本語請求書をOCRし、日付・税額・金額・T番号をローカル検証します(法人照合なし)。 用途: 日本語の請求書をOCRし、法人照合なしで日付・金額・税額・T番号を検証したい場合。 返却: OCR請求書項目に加え、形式・金額計算・税額・必須項目・確認状態を返します。 料金: 成功した呼び出し1回あたり $0.01 USDC(Base上のx402決済)。
jp_invoice_extract_and_verify
OCR a Japanese billing invoice, validate it locally, and resolve the issuer against NTA registries. Use when: You need invoice OCR and issuer name/address comparison or completion using NTA public data. Returns: OCR values, registry values, resolved issuer values, validation, and an explicit review signal. Price: $0.05 USDC per successful call, paid with x402 on Base. / 日本語請求書をOCR・ローカル検証し、発行者を国税庁データと照合します。 用途: 請求書OCRに加えて、国税庁公開データで発行者名・住所・T番号を照合・補完したい場合。 返却: OCR値、登記値、採用した発行者値、検証結果、明示的な確認シグナルを返します。 料金: 成功した呼び出し1回あたり $0.05 USDC(Base上のx402決済)。
jp_invoice_issuer_check
Verify a T-number and compare the issuer name and address with Japan's NTA registries. Use when: You have extracted issuer fields and need T-number, company-name, and address comparison. Returns: OCR issuer fields, NTA registry fields, comparison results, and resolved values; phone is not registry-compared. Price: $0.03 USDC per successful call, paid with x402 on Base. / T番号を検証し、発行者名・住所を国税庁データと比較します。 用途: 抽出済みの発行者情報について、T番号・会社名・住所を照合したい場合。 返却: OCR発行者情報、国税庁登記情報、比較結果、採用値を返します。電話番号は登記比較しません。 料金: 成功した呼び出し1回あたり $0.03 USDC(Base上のx402決済)。
jp_invoice_issuer_match
Compare structured invoice fields with supplier master identifiers. Use when: Match structured invoice fields against supplier master data. Returns: Issuer decision and separate document, expected and registry evidence. Price: $0.05 USDC per successful call, paid with x402 on Base. / 請求書の項目を仕入先マスターの識別番号と照合します。 用途: 構造化済みの請求書と仕入先マスターを照合したい場合。 返却: 発行者の判定と請求書・仕入先マスター・登録情報を返します。 料金: 成功した呼び出し1回あたり $0.05 USDC(Base上のx402決済)。
jp_invoice_issuer_match_extract
Read an invoice and match the issuer to supplier master identifiers. Use when: Read an invoice document before matching it against supplier master data. Returns: Issuer decision and separate document, expected and registry evidence. Price: $0.10 USDC per successful call, paid with x402 on Base. / 請求書を読み取り、発行者を仕入先マスターの識別番号と照合します。 用途: 請求書を読み取って仕入先マスターと照合したい場合。 返却: 発行者の判定と請求書・仕入先マスター・登録情報を返します。 料金: 成功した呼び出し1回あたり $0.10 USDC(Base上のx402決済)。
jp_invoice_registration_verify
Verify a Japanese qualified-invoice registration number (T + 13 digits) against the NTA invoice registry. 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決済)。
address
jp_address_normalize
Normalize a Japanese address into a canonical hierarchy with an English rendering. Use when: You need Japanese address normalization or standardization, whether or not the input contains a postal code. Returns: Normalized prefecture/city/town/chome/block/lot/house components, parser confidence, match hierarchy, geocoder evidence, and postal-code evidence when a postal code is supplied. It does not infer a missing postal code. Price: $0.005 USDC per successful call, paid with x402 on Base. / 日本の住所を正規化し、階層と英語表記を返します。 用途: 入力に郵便番号があってもなくても、日本住所を正規化・標準化したい場合。 返却: 都道府県・市区町村・町名・丁目・番地・号などの正規化項目、解析信頼度、照合階層、地理コード根拠を返します。郵便番号を入力した場合のみ郵便番号根拠を返し、未入力の郵便番号は推定しません。 料金: 成功した呼び出し1回あたり $0.005 USDC(Base上のx402決済)。
jp_address_validate
Validate a Japanese address with parser, postal and geocoder evidence and return exact/partial/ambiguous/conflict/unverified. 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決済)。
business
jp_business_card_extract
Read a Japanese business card (front/back HTTPS image URL or small Base64); enrich=true adds a registry pre-check of the organization. [enrich=false, $0.03 USDC] Use when: You need only the person, role, department, company, phone, email, or address printed on a Japanese business card. Returns: Card-printed contact fields only; no corporate-number or NTA issuer verification. [enrich=true, $0.10 USDC] Use when: You need business-card OCR plus Japanese corporate-number and qualified-invoice enrichment. Returns: Separate card OCR values and registry-resolved company values; registry pre-check, not full KYB. Paid per successful call with x402 on Base. / 日本語の名刺を読み取ります。enrich=trueで組織の法人照合も行います。 [enrich=false、$0.03 USDC] 用途: 日本語の名刺に印刷された氏名、役職、部署、会社名、電話、メール、住所だけが必要な場合。 返却: 名刺に印刷された連絡先のみ。法人番号や国税庁発行者照合は含みません。 [enrich=true、$0.10 USDC] 用途: 名刺OCRに加えて、日本の法人番号・適格請求書登録情報で企業を照合したい場合。 返却: 名刺OCR値と登記照合済み企業値を分離して返します。完全なKYBではありません。 成功した呼び出しのみx402(Base)で課金します。
company
jp_company_verify
Verify a Japanese company by name, 13-digit corporate number (法人番号), or address against the NTA registry. Use when: You need a Japanese company or corporate-number lookup. Returns: Corporate number, registered legal name/address, active or closed status, and match evidence. Price: $0.005 USDC per successful call, paid with x402 on Base. / 会社名・法人番号・住所を国税庁の法人番号公表データと照合します。 用途: 日本企業または法人番号を検索・照合したい場合。 返却: 法人番号、登記上の法人名・住所、活動状態、一致根拠を返します。 料金: 成功した呼び出し1回あたり $0.005 USDC(Base上のx402決済)。
counterparty
jp_counterparty_check
Check a known EU VAT ID and/or Peppol participant: VAT validity, name match, and Peppol discoverability. Use when: You need separate EU VAT validity, returned-name entity matching, and Peppol participant discoverability evidence. Returns: Projected VIES and Peppol evidence only; VIES is known-ID validation and member-state outages are insufficient coverage. Price: $0.05 USDC per successful call, paid with x402 on Base. / 既知のEU VAT IDやPeppol参加者IDの有効性・名称一致・到達性を確認します。 用途: EU VAT有効性、返却名による法人一致、Peppol参加者到達性を分けて確認する場合。 返却: VIESとPeppolの加工済み根拠のみを返します。VIESは既知IDの検証であり、加盟国停止は対象範囲不足です。 料金: 成功した呼び出し1回あたり $0.05 USDC(Base上のx402決済)。
entity
jp_entity_resolve
Find the Japanese legal entity from an English name, postal code, T-number, corporate number, LEI or securities code; results in English. Use when: You hold an English or romanized Japanese company name, postal code, 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. Price: $0.50 USDC per successful call, paid with x402 on Base. / 英語名・郵便番号・T番号・法人番号・LEI・証券コードから日本の法人を特定します。 用途: 英語名・ローマ字・郵便番号・T番号・法人番号・LEI・証券コードから日本の法人を特定したい場合。 返却: 判定、正式な日本語商号、読み、出典付き英語名、契約当事者名、状態、適格請求書登録を返します。 料金: 成功した呼び出し1回あたり $0.50 USDC(Base上のx402決済)。
jpverify
jpverify_guide
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決済方法を返します。質問を渡すと最適なツールと入力例を返します。
receipt
jp_receipt_extract
OCR a Japanese receipt with local amount, tax and T-number checks; detected T-numbers are verified with the NTA registry. Use when: You need Japanese receipt or 領収書 OCR with local tax, amount, T-number, and format checks. Returns: Structured receipt fields, deterministic validation, field status, and review signals. Price: $0.03 USDC per successful call, paid with x402 on Base. / 日本語領収書をOCRし、金額・税額・T番号を検証します。 用途: 日本語の領収書・レシートをOCRし、金額・税額・T番号・形式を検証したい場合。 返却: 構造化された領収書項目、決定論的検証、項目状態、確認シグナルを返します。 料金: 成功した呼び出し1回あたり $0.03 USDC(Base上のx402決済)。
supplier
jp_supplier_resolve
One coverage-aware supplier check combining company, qualified-invoice and address evidence. 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.01 USDC per successful call, paid with x402 on Base. / 会社・適格請求書・住所の根拠をまとめて仕入先を確認します。 用途: 会社、適格請求書、住所の根拠を組み合わせ、必要に応じて内部機能フラグでgBizINFO活動根拠も付加した、対象範囲を明示した仕入先確認を行う場合。 返却: 個別の根拠チェック、ソース版、resolved/ambiguous/not-found/insufficient-coverage状態を返します。任意のgBizINFOはこのレスポンス内の加工済み補助根拠であり、単独ソースや原レスポンスの再販ではありません。法的判断やKYB判定ではありません。 料金: 成功した呼び出し1回あたり $0.01 USDC(Base上のx402決済)。

Endpoints

URLTransportStateLatencyChecked
https://api.jpverify.com/mcp streamable-http answering 856 ms 6 min ago

Alternatives to JPVerify

same job, measured the same way
Denpyo MCP
by vladic-corp

Japanese invoice/receipt OCR + tax registration-number (T-number) verification, via x402.

54 installs/wk local only
x402 Micropayments MCP
by kwizzlesurp10-ctrl

Pay-per-call US city property compliance and Base tx checks, paid in USDC on Base via x402.

21 tools answering
x402 Research
by kevinm222

Pay-per-call x402 crypto research and Base address/approval risk checks. Testnet by default.

158 installs/wk local only
D
DeskCalc Verify
by deskcalc

A human checks and confirms in DeskCalc the figures an AI read from invoices, receipts, statements.

local only
JP-Verify
by obolpay

Verify Japanese companies: invoice T-numbers, Corporate Numbers, English names, shareholders

113 installs/wk local only
E
Extract
by mart402

Web extraction, OCR (Japanese-strong), invoice and company data for AI agents. x402, no API key.

35 tools answering
P
Parser
by wrapper-agency-parsedoc

Parse receipts & invoices into structured JSON. Pay per call in USDC (x402 on Base), no API key.

47 installs/wk local only
Quay
by quay21

Pay-per-call TRON fee, payment, and address checks. Agents pay USDT or USDC.

4 tools answering

JPVerify — questions

Answers built from our own checks of this server.

What can JPVerify do?
It exposes 15 tools, read directly from the server on our last check. Among them: jp_address_normalize, jp_address_validate, jp_business_card_extract, jp_company_verify, jp_counterparty_check, jp_entity_resolve and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is JPVerify mostly used for?
Its tools cluster around invoice and address. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is JPVerify working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 85 of 85 checks got a reply (100.0%), average response time 879 ms. The bar chart above shows every period we have measured.
How do I connect JPVerify?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does JPVerify need an API key?
No. JPVerify completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is JPVerify?
It answers our handshake in 879 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is JPVerify open source?
The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at api.jpverify.com, which runs on its operator's own terms.