JPVerify MCP server
com.jpverify/jpverifyjpverify.comstreamable-httpv0.7.2Scanned
Japan company, T-number, invoice issuer and address checks for AI agents, paid per call via x402.
9 tools: 6 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 9
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the JPVerify MCP server can do
The JPVerify MCP server is published by jpverify.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (6 tools: jpverify_guide, jpverify_balance, jp_company_verify, jp_invoice_registration_verify and 2 more), but cannot delete data. 3 tools only read.
9 tools bring in text other people can write (jpverify_guide, jpverify_balance, jp_company_verify and 6 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 0.7.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 6Claude Code: ask
jp_address_normalizeNormalize a Japanese address into a canonical hierarchy (prefecture to room) with the confirmed match level and an English rendering from Japan Post romanized data.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Normalize a Japanese address into a canonical hierarchy (prefecture to room) with the confirmed match level and an English rendering from Japan Post romanized data. 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: Normalized prefecture/city/town/chome/block/lot/house components, an English address from Japan Post romanization, 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. / 日本の住所を正規化し、都道府県から部屋番号までの階層・照合レベルと、日本郵便のローマ字データによる英語表記を返します。事業所の個別郵便番号(例: 100-8310)と地番(番地)住所にも対応します。 用途: 入力に郵便番号があってもなくても、日本住所を正規化・標準化したい場合。 返却: 都道府県・市区町村・町名・丁目・番地・号などの正規化項目、解析信頼度、照合階層、地理コード根拠を返します。郵便番号を入力した場合のみ郵便番号根拠を返し、未入力の郵便番号は推定しません。 料金: 成功した呼び出し1回あたり $0.005 USDC(Base上のx402決済)。
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Normalize Japanese address
jp_company_verifyVerify a Japanese company by its registered (Japanese) name or 13-digit corporate number (法人番号) against the NTA registry; an address is comparison evidence only.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Verify a Japanese company by its registered (Japanese) name or 13-digit corporate number (法人番号) against the NTA registry; an address is comparison evidence only. Returns the Japanese legal name plus a sourced English name and address. For an English name, use jp_company_resolve first. 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. / 登記上の会社名(日本語)または法人番号を国税庁の法人番号公表データと照合します。住所は比較用の根拠です。 用途: 日本企業または法人番号を検索・照合したい場合。 返却: 法人番号、登記上の法人名(legal_name_ja)・住所、英語名(国税庁公式・EDINET・読みのローマ字)と英語住所(公式または日本郵便ローマ字)とその出典、活動状態、一致根拠を返します。 料金: 成功した呼び出し1回あたり $0.01 USDC(Base上のx402決済)。
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Verify Japanese company
jp_invoice_issuer_checkCheck a T-number against the issuer name on the invoice, the address (optional), the invoice date (optional: registered on that date, not cancelled or expired) and your supplier ma…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check a T-number against the issuer name on the invoice, 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決済)。
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Check invoice issuer
jp_invoice_registration_verifyVerify 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.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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決済)。
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Verify T-number (qualified invoice)
jpverify_balanceFree.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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を返します。
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: API key credit balance (free)
jpverify_guideFree.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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決済方法を返します。質問を渡すと最適なツールと入力例を返します。
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: JPVerify guide (free)
Only reads 3Show 3 read-only tools
jp_address_validateValidate a Japanese address with parser, postal and geocoder evidence and return exact/partial/ambiguous/conflict/unverified.Reads text others writeNo findings
Why it is in this group
- The name "jp_address_validate" says "validate": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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決済)。
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Validate Japanese address
jp_company_resolveFind the Japanese legal entity from an English or brand name (e.g.Reads text others writeNo findings
Why it is in this group
- The name "jp_company_resolve" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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決済)。
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Resolve Japanese entity from English name or identifier
jp_supplier_resolveOne coverage-aware supplier check combining company, qualified-invoice and address evidence.Reads text others writeNo findings
Why it is in this group
- The name "jp_supplier_resolve" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.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決済)。
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Resolve Japanese supplier
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write9
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.jpverify.com/mcp: tools/list returned 9 tools to an anonymous client, including jpverify_guide (write), jpverify_balance (write), jp_company_verify (write), jp_invoice_registration_verify (write), jp_invoice_issuer_check (write) and 1 more
Posture changes
- Nov 14, 2026
- Tools that change things, listed without credentials: 9 to 6
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 6.View diff
- Tools that change things, listed without credentials: 9 to 6
Tools2 changed.~2 changedView diff
- Changed:jp_address_normalizeChanges thingsdescription
- Changed:jp_company_resolveOnly readsdescription
Tools2 added, 1 removed, 3 changed.+2 added−1 removed~3 changedView diff
- Added:jp_company_resolveOnly reads
- Added:jpverify_balanceChanges things
- Removed:jp_entity_resolve
- Changed:jp_address_validateOnly readsinputSchema
- Changed:jp_company_verifyChanges thingsdescription
- Changed:jp_supplier_resolveOnly readsinputSchema
Tools1 added, 5 removed, 5 changed.+1 added−5 removed~5 changedView diff
- Added:jp_entity_resolveOnly reads
- Removed:jp_business_card_extract
- Removed:jp_counterparty_check
- Removed:jp_invoice_extract
- Removed:jp_invoice_extract_and_verify
- Removed:jp_receipt_extract
- Changed:jp_address_normalizeChanges thingsdescription
- Changed:jp_company_verifyChanges thingsdescriptioninputSchema
- Changed:jp_invoice_issuer_checkChanges thingsdescriptioninputSchema
- Changed:jp_invoice_registration_verifyChanges thingsdescription
- Changed:jp_supplier_resolveOnly readsdescriptioninputSchema
Tools7 changed.~7 changedView diff
- Changed:jp_address_normalizeChanges thingsinputSchema
- Changed:jp_address_validateOnly readsinputSchema
- Changed:jp_business_card_extractOnly readsdescriptioninputSchema
- Changed:jp_company_verifyChanges thingsinputSchema
- Changed:jp_counterparty_checkChanges thingsinputSchema
- Changed:jp_invoice_issuer_checkChanges thingsinputSchema
- Changed:jp_supplier_resolveOnly readsinputSchema
Install
Pinned to version 0.7.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http jpverify https://api.jpverify.com/mcpclaude mcp add --transport http jpverify https://api.jpverify.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__jpverify__jp_address_validate",
"mcp__jpverify__jp_supplier_resolve",
"mcp__jpverify__jp_company_resolve"
],
"ask": [
"mcp__jpverify__jpverify_guide",
"mcp__jpverify__jpverify_balance",
"mcp__jpverify__jp_company_verify",
"mcp__jpverify__jp_invoice_registration_verify",
"mcp__jpverify__jp_invoice_issuer_check",
"mcp__jpverify__jp_address_normalize"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jpverify. Review it before you use it.
Capability tags behind 9 rules
- mcp__jpverify__jpverify_guide untrusted-input
- mcp__jpverify__jpverify_balance untrusted-input
- mcp__jpverify__jp_company_verify untrusted-input
- mcp__jpverify__jp_invoice_registration_verify untrusted-input
- mcp__jpverify__jp_invoice_issuer_check untrusted-input
- mcp__jpverify__jp_address_normalize untrusted-input
- mcp__jpverify__jp_address_validate untrusted-input
- mcp__jpverify__jp_supplier_resolve untrusted-input
- mcp__jpverify__jp_company_resolve untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.jpverify/jpverify/verify?hash=05a8389f04033750a0e2bd5c773c930eb07fe54ff0f0ab17f6ad5c41633c2904" | jq -e '.changed == false'Pinned hash 05a8389f0403, from Nov 10, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.jpverify/jpverify/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.jpverify/jpverify)Source: MCP Registry · repository. Synced Nov 10, 2026, 05:17 UTC.
JPVerify MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the JPVerify MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the JPVerify MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the JPVerify MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the JPVerify MCP server have?
- 9 tools: 6 write, 3 read. jpverify_guide, jpverify_balance, jp_company_verify, jp_invoice_registration_verify, jp_invoice_issuer_check, jp_address_normalize, jp_address_validate, jp_supplier_resolve and 1 more.
Does the JPVerify MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the JPVerify MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the JPVerify MCP server changed its tools?
- Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.