JPVerify MCP
[mcptry]
[JPVerify]
Remote MCP server for Japanese business identity checks and Japanese document OCR: NTA corporate-number and qualified-invoice (T-number) verification, address normalization and validation, invoice / receipt / business-card OCR, supplier resolution, and EU VAT / Peppol counterparty checks.
- Endpoint (Streamable HTTP):
https://api.jpverify.com/mcp — no account, no API key
- Official MCP Registry:
com.jpverify/jpverify
- Payment: x402 — USDC on Base mainnet (
eip155:8453), per successful call
- Website: https://www.jpverify.com · Contact: [email protected]
This repository holds documentation and connection examples only. The service itself is operated by DSテクニック at the endpoint above.
日本語
Connect
Claude Code:
Generic mcp.json (Cursor, Claude Desktop with remote support, and other MCP clients):
initialize, tools/list and the jpverify_guide tool are free, so you can inspect every tool and its input schema before paying for anything.
Tools
All tools are read-only (readOnlyHint: true). Registry results are a public-data pre-check, not KYB, AML, sanctions screening, or legal or tax advice.
How payment works
- Call a paid tool without payment. The result is an x402
PaymentRequired object (isError: true, structuredContent.accepts[] with the exact USDC amount, payTo and network).
- Sign the payment with an x402 client and call the same tool again with the payload in
params._meta["x402/payment"].
- The tool runs; payment is settled only after a successful result. The settlement receipt is returned in
_meta["x402/payment-response"].
Invalid input is rejected before any payment is requested, and failed calls are not charged. MCP clients without an x402 wallet can still use jpverify_guide and the HTTP API documentation.
Example tool call:
Other entry points
- A2A agent (v0.3): AgentCard
https://api.jpverify.com/.well-known/agent-card.json, JSON-RPC https://api.jpverify.com/a2a (message/send, tasks/get), payments via the a2a-x402 extension
- HTTP API: OpenAPI
https://api.jpverify.com/openapi.json, x402 catalog https://api.jpverify.com/.well-known/x402.json, agent guide https://api.jpverify.com/skill.md
- Batch verification, async batch jobs, JP PINT validation, FSA regulated-entity checks and EDINET filings are available over the HTTP API only.
Complementary checks
JPVerify confirms who a Japanese counterparty is (corporate number, T-number, address). It does not screen sanctions lists. If your onboarding flow also needs sanctions screening, run it as a separate step on the resolved name:
- Use the official English or romanized name from the corporate-number record. Most sanctions lists are matched on Latin-script names and aliases, so Japanese script often finds nothing even when an entry exists.
- Check official sources such as OFAC Sanctions List Search, or a screening tool. One that runs on the same x402 rail (USDC on Base) is AgentReader's
/sanctions-batch, which checks OFAC, UK, UN and EU lists and has a free preview.
Third-party services are listed for convenience only. JPVerify is not affiliated with them and does not endorse or verify their results. Confirm any potential match with the issuing authority.
日本語
日本企業の照合と日本語書類OCRのためのリモートMCPサーバーです。国税庁の法人番号・適格請求書(T番号)照合、住所の正規化・検証、請求書・領収書・名刺OCR、仕入先確認、EU VAT/Peppolの取引先確認に対応します。
- エンドポイント(Streamable HTTP):
https://api.jpverify.com/mcp(アカウント・APIキー不要)
- 決済: x402(Base上のUSDC)。成功した呼び出しのみ課金
initialize、tools/list、jpverify_guide は無料です。
不正な入力は支払い前に拒否され、失敗した呼び出しは課金されません。照合結果は公開データに基づく事前確認であり、KYB、AML、制裁リスト審査、法務・税務上の助言ではありません。
制裁リスト審査が必要な場合は、法人番号データの英語表記またはローマ字表記の名称を使い、別の手順として実施してください(多くの制裁リストはラテン文字の名称で照合されます)。審査先の例は英語版の Complementary checks を参照してください。第三者サービスは参考として掲載しており、JPVerifyとの提携や推奨を意味するものではありません。
License
Documentation and example configuration in this repository: MIT. The JPVerify service is subject to its Terms of Service and Privacy Policy.