# io.github.CloudCorpRecords/jpverify (oci · ghcr.io/cloudcorprecords/jpverify)

Verify Japanese companies: corporate numbers, invoice registrations, profiles and addresses.

- Trust score: 45/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/jpverify`: 69/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-jpverify/reneturcios-jpverify.md), [page](https://verifymcp.io/servers/cloudcorprecords-jpverify/reneturcios-jpverify)
- oci · `ghcr.io/cloudcorprecords/jpverify`: 45/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-jpverify/ghcr-io-cloudcorprecords-jpverify.md), [page](https://verifymcp.io/servers/cloudcorprecords-jpverify/ghcr-io-cloudcorprecords-jpverify)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/jpverify`
- 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-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **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 11 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 1191 tokens (~198/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/jpverify MCP server?

io.github.CloudCorpRecords/jpverify runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/jpverify:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-jpverify -- docker run --rm -i ghcr.io/cloudcorprecords/jpverify:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-jpverify": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/jpverify:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-jpverify": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/jpverify:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-jpverify -- docker run --rm -i ghcr.io/cloudcorprecords/jpverify:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-jpverify": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/jpverify:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-jpverify:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/jpverify:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-jpverify": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/jpverify:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-jpverify": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/jpverify:0.1.0",
        "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-21 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

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

### 2026-11-17 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 39)

First indexed and scored.

## MCP tools (6)

### `resolve_company` (~193 tokens)

法人名から法人番号を解決

法人名（表記ゆれ・かな/カナ対応）から法人番号の候補と確度（0〜1＋根拠ラベル）を返します。データ源: 国税庁法人番号システムWeb-API。

Input parameters:

- `address` (string): 所在地で絞り込み: 都道府県コード2桁（JIS X 0401）または+市区町村コード3桁の計5桁
- `include_closed` (boolean): 閉鎖法人を候補に含める（既定true）
- `limit` (integer): 返却する候補数の上限（既定10）
- `name` (string, required): 法人名（(株)等の略記・全半角・かな/カナ・旧字体の表記ゆれ可）

### `verify_company` (~133 tokens)

法人番号の実在検証

法人番号（13桁・チェックディジット検証つき）から実在・商号・本店所在地・法人種別・閉鎖ステータスを返します。include_history=trueで商号変更等の履歴も返します。データ源: 国税庁法人番号システムWeb-API。

Input parameters:

- `corporate_number` (string, required): 法人番号13桁（全角・ハイフン・空白は吸収）
- `include_history` (boolean): 商号変更等の履歴を含める（既定false）

### `verify_invoice_number` (~230 tokens)

適格請求書発行事業者登録番号の検証

適格請求書発行事業者の登録番号（T+13桁）から登録有無・登録年月日・取消/失効を返します。on_dateで基準日時点の有効性判定、include_history=trueで公表履歴も返します。入力は登録番号のみ（氏名等による検索は提供しません）。データ源: 国税庁適格請求書発行事業者公表システムWeb-API。

Input parameters:

- `include_history` (boolean): 公表履歴（新規登録・変更・取消・失効）を含める（既定false）
- `on_date` (string): 基準日 YYYY-MM-DD（指定時はその日時点で登録が有効だったかを as_of で返す）
- `registration_number` (string, required): 適格請求書発行事業者登録番号（T+13桁。Tなし13桁・全角・ハイフン空白は吸収）

### `get_company_profile` (~129 tokens)

法人プロファイル取得（gBizINFO）

法人番号（13桁・チェックディジット検証つき）からgBizINFOの法人プロファイル（所在地・代表者・資本金・従業員数等）を、項目別の出典・最終取得日メタとあわせて返します。データ源: Gビズインフォ REST API v2（経済産業省）。

Input parameters:

- `corporate_number` (string, required): 法人番号13桁（全角・ハイフン・空白は吸収。チェックディジット検証あり）

### `normalize_address` (~279 tokens)

日本住所の正規化・要素分解・郵便番号照合

日本の住所を正規化し、都道府県／市区町村／町字（大字・町名＋丁目）に分解して町字ID（アドレス・ベース・レジストリ）を解決し、郵便番号と照合します（不一致は不一致として明示）。【v1の粒度と限界】分解は町字（大字・丁目）まで。街区符号・住居番号・地番・小字・京都の通り名は解析対象外で、未解析部分は残余文字列としてそのまま返します（推測補完なし）。データ源: アドレス・ベース・レジストリ町字マスター（デジタル庁）＋日本郵便郵便番号データ（ローカルマスター駆動・政府API停止の影響なし）。

Input parameters:

- `address` (string, required): 日本の住所文字列（郵便番号含み可。全半角・漢数字/算用数字・旧字体の表記ゆれ可）
- `postal_code` (string): 郵便番号を別引数で渡す場合に指定（住所文字列内の記載より優先して照合）

### `jp_calendar` (~227 tokens)

日本の祝日・営業日計算

日本の祝日判定と営業日計算（内閣府「国民の祝日」CSV準拠）。営業日=土日・祝日以外。year_end_as_holiday=trueで12/29〜1/3も非営業日扱い。

Input parameters:

- `date` (string): 基準日 YYYY-MM-DD（list_holidays以外で必須）
- `days` (integer): 加算する営業日数（add_business_daysで必須。負数=遡り、0=基準日をそのまま返す）
- `from` (string): 期間開始日（list_holidaysで必須）
- `op` (string, required): 操作種別
- `to` (string): 期間終了日（list_holidaysで必須）
- `year_end_as_holiday` (boolean): 12/29〜1/3を非営業日として扱う（官公庁・銀行休業の慣行。既定false=祝日法と土日のみ）

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-jpverify/ghcr-io-cloudcorprecords-jpverify#diagnostics

## Score history

- 2026-11-21: 45
- 2026-11-20: 44
- 2026-11-19: 44
- 2026-11-18: 43
- 2026-11-17: 43
- 2026-11-16: 42
- 2026-11-15: 42
- 2026-11-14: 41
- 2026-11-13: 41
- 2026-11-12: 40
- 2026-11-11: 40
- 2026-11-10: 39

## Common questions

### What is the io.github.CloudCorpRecords/jpverify MCP server?

io.github.CloudCorpRecords/jpverify is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/jpverify. Verify Japanese companies: corporate numbers, invoice registrations, profiles and addresses. This page covers its container image (ghcr.io/cloudcorprecords/jpverify).

### Is the io.github.CloudCorpRecords/jpverify MCP server safe to use?

io.github.CloudCorpRecords/jpverify scores 45 out of 100 on VerifyMCP. 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 io.github.CloudCorpRecords/jpverify MCP server expose?

io.github.CloudCorpRecords/jpverify exposes 6 tools: resolve_company, verify_company, verify_invoice_number, get_company_profile, normalize_address, jp_calendar. Their descriptions and schemas cost roughly 1,191 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/jpverify MCP server still maintained?

io.github.CloudCorpRecords/jpverify is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.CloudCorpRecords/jpverify MCP server under?

io.github.CloudCorpRecords/jpverify declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/jpverify MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/jpverify, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/jpverify: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/jpverify
- Repository: https://github.com/CloudCorpRecords/jpverify
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-jpverify/ghcr-io-cloudcorprecords-jpverify.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-jpverify/ghcr-io-cloudcorprecords-jpverify/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-jpverify/ghcr-io-cloudcorprecords-jpverify.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-jpverify/ghcr-io-cloudcorprecords-jpverify
