# JP-Verify (pypi · jp-verify-mcp)

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

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

## Components

- pypi · `jp-verify-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/xyz-obolpay-jp-verify/jp-verify-mcp.md), [page](https://verifymcp.io/servers/xyz-obolpay-jp-verify/jp-verify-mcp)

## Channel facts

- Registry: `pypi`
- Package: `jp-verify-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. 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-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 28 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 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.

### Claude

```bash
claude mcp add xyz-obolpay-jp-verify -- uvx jp-verify-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-obolpay-jp-verify": {
      "command": "uvx",
      "args": [
        "jp-verify-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-obolpay-jp-verify": {
      "command": "uvx",
      "args": [
        "jp-verify-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add xyz-obolpay-jp-verify -- uvx jp-verify-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-obolpay-jp-verify": {
      "type": "local",
      "command": [
        "uvx",
        "jp-verify-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-obolpay-jp-verify --command uvx --arg jp-verify-mcp
```

### Hermes

```yaml
mcp_servers:
  xyz-obolpay-jp-verify:
    command: "uvx"
    args: ["jp-verify-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-obolpay-jp-verify": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "jp-verify-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-obolpay-jp-verify -t stdio -c uvx -a jp-verify-mcp
```

### Other

```json
{
  "mcpServers": {
    "xyz-obolpay-jp-verify": {
      "command": "uvx",
      "args": [
        "jp-verify-mcp"
      ]
    }
  }
}
```

## 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-04 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 64, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-01 (score 78, +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.

### 2026-10-30 (score 77, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-29 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-28 (score 76, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-25 (score 60, −14)

- [security regression] Malware scan: pass → unverified

### 2026-10-23 (score 74, +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.

## MCP tools (4)

### `verify_japanese_company` (~204 tokens)

Verify a Japanese company

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.

Input parameters:

- `number` (string, required): A T-number such as T1180301018771, or a 13-digit Corporate Number. Spaces, hyphens and full-width characters are accepted.

### `verify_japanese_companies_batch` (~130 tokens)

Verify many Japanese companies

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.

Input parameters:

- `numbers` (array, required): T-numbers and/or 13-digit Corporate Numbers.

### `get_major_shareholders` (~210 tokens)

Major shareholders of a Japanese company

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.

Input parameters:

- `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, required): The company's 13-digit Corporate Number (法人番号); a T-number is also accepted.

### `find_japanese_company_by_name` (~170 tokens)

Find a Japanese company by name

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.

Input parameters:

- `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, required): A company name, e.g. トヨタ自動車株式会社 or Toyota Jidosha.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/xyz-obolpay-jp-verify/jp-verify-mcp#diagnostics

## Score history

- 2026-11-04: 79
- 2026-11-03: 64
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 61
- 2026-10-28: 76
- 2026-10-27: 60
- 2026-10-26: 60
- 2026-10-25: 60
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 58
- 2026-10-20: 69
- 2026-10-19: 54
- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 54
- 2026-10-15: 54
- 2026-10-14: 54
- 2026-10-13: 39
- 2026-10-12: 24
- 2026-10-08: 24

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/jp-verify-mcp/
- Socket report: https://socket.dev/pypi/package/jp-verify-mcp
- Repository: https://github.com/Hiroshi-Ichiyanagi/jp-verify-mcp
- Website: https://jp-verify.obolpay.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-obolpay-jp-verify/jp-verify-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-obolpay-jp-verify/jp-verify-mcp.json
- HTML version of this page: https://verifymcp.io/servers/xyz-obolpay-jp-verify/jp-verify-mcp