Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/jpverify

NPM · @RENETURCIOS/JPVERIFY · 2 COMPONENTS

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

0 this week 69 Trust /100

Last scanned (19 hours ago)

Scores higher than 39% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 10 Nov 26 69

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@reneturcios/jpverify@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 npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,191 tokens

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 →

Tool Tokens
get_company_profile ~129

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

NameTypeReqDescription
corporate_numberstringyes法人番号13桁(全角・ハイフン・空白は吸収。チェックディジット検証あり)

No output schema declared.

No examples provided.

jp_calendar ~227

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

NameTypeReqDescription
datestring–基準日 YYYY-MM-DD(list_holidays以外で必須)
daysinteger–加算する営業日数(add_business_daysで必須。負数=遡り、0=基準日をそのまま返す)
fromstring–期間開始日(list_holidaysで必須)
opstringyes操作種別
tostring–期間終了日(list_holidaysで必須)
year_end_as_holidayboolean–12/29〜1/3を非営業日として扱う(官公庁・銀行休業の慣行。既定false=祝日法と土日のみ)

No output schema declared.

No examples provided.

normalize_address ~279

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

NameTypeReqDescription
addressstringyes日本の住所文字列(郵便番号含み可。全半角・漢数字/算用数字・旧字体の表記ゆれ可)
postal_codestring–郵便番号を別引数で渡す場合に指定(住所文字列内の記載より優先して照合)

No output schema declared.

No examples provided.

resolve_company ~193

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

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

No output schema declared.

No examples provided.

verify_company ~133

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

NameTypeReqDescription
corporate_numberstringyes法人番号13桁(全角・ハイフン・空白は吸収)
include_historyboolean–商号変更等の履歴を含める(既定false)

No output schema declared.

No examples provided.

verify_invoice_number ~230

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

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

No output schema declared.

No examples provided.

Install

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

io.github.CloudCorpRecords/jpverify runs locally as an npm package, launched with npx -y @reneturcios/jpverify mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/jpverify

# add to Claude Code
claude mcp add cloudcorprecords-jpverify -- npx -y @reneturcios/jpverify mcp
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 npm package (@reneturcios/jpverify).

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

io.github.CloudCorpRecords/jpverify scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 15 checks on io.github.CloudCorpRecords/jpverify, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/jpverify: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.