JP-Verify
PYPI · JP-VERIFY-MCP
Verify Japanese companies: invoice T-numbers, Corporate Numbers, English names, shareholders
Available components
Last scanned (1 day ago)
Scores higher than 78% of PyPI servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 28 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 857 tokens (~214/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/jp-verify-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_japanese_company_by_name Find a Japanese company by name ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of candidates: 1-25 on the key-less sandbox and Starter keys, up to 100 on Growth and Reseller keys. |
| name | string | yes | A company name, e.g. トヨタ自動車株式会社 or Toyota Jidosha. |
No output schema declared.
No examples provided.
get_major_shareholders Major shareholders of a Japanese company ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | Optional date YYYY-MM-DD: use the latest filing submitted on or before this date. The holdings are as of that filing's own basis date. |
| corporate_number | string | yes | The company's 13-digit Corporate Number (法人番号); a T-number is also accepted. |
No output schema declared.
No examples provided.
verify_japanese_companies_batch Verify many Japanese companies ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | yes | T-numbers and/or 13-digit Corporate Numbers. |
No output schema declared.
No examples provided.
verify_japanese_company Verify a Japanese company ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | A T-number such as T1180301018771, or a 13-digit Corporate Number. Spaces, hyphens and full-width characters are accepted. |
No output schema declared.
No examples provided.
How do I install the JP-Verify MCP server?
JP-Verify runs locally as a PyPI package, launched with uvx jp-verify-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · jp-verify-mcp
claude mcp add xyz-obolpay-jp-verify -- uvx jp-verify-mcp
What is the JP-Verify MCP server?
JP-Verify is an MCP server listed in the public MCP registry as xyz.obolpay/jp-verify. Verify Japanese companies: invoice T-numbers, Corporate Numbers, English names, shareholders. This page covers its PyPI package (jp-verify-mcp).
Is the JP-Verify MCP server safe to use?
JP-Verify scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 JP-Verify MCP server expose?
JP-Verify exposes 4 tools: verify_japanese_company, verify_japanese_companies_batch, get_major_shareholders, find_japanese_company_by_name. Their descriptions and schemas cost roughly 714 tokens of context every time the server is loaded.
Is the JP-Verify MCP server still maintained?
JP-Verify is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the JP-Verify MCP server under?
JP-Verify declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.