Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Jpverify is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
222
downloads a day
local
runs on your machine
6
tools declared
What it does
Verify Japanese companies: corporate numbers, invoice registrations, profiles and addresses.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user cloudcorprecords-jpverify-mcp '--' npx -y @reneturcios/jpverify mcp
# 2 — ask your agent for something these tools do
# resolve_company, verify_company, verify_invoice_number and 3 more
Jpverify costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 425 servers
CloudCorpRecords425 servers
28 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Jpverify as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user cloudcorprecords-jpverify-mcp '--' npx -y @reneturcios/jpverify mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
法人名（表記ゆれ・かな/カナ対応）から法人番号の候補と確度（0〜1＋根拠ラベル）を返します。データ源: 国税庁法人番号システムWeb-API。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | 法人名（(株)等の略記・全半角・かな/カナ・旧字体の表記ゆれ可） |
| address | string | no | 所在地で絞り込み: 都道府県コード2桁（JIS X 0401）または+市区町村コード3桁の計5桁 |
| include_closed | boolean | no | 閉鎖法人を候補に含める（既定true） |
| limit | integer | no | 返却する候補数の上限（既定10） |
法人番号（13桁・チェックディジット検証つき）から実在・商号・本店所在地・法人種別・閉鎖ステータスを返します。include_history=trueで商号変更等の履歴も返します。データ源: 国税庁法人番号システムWeb-API。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| corporate_number | string | yes | 法人番号13桁（全角・ハイフン・空白は吸収） |
| include_history | boolean | no | 商号変更等の履歴を含める（既定false） |
適格請求書発行事業者の登録番号（T+13桁）から登録有無・登録年月日・取消/失効を返します。on_dateで基準日時点の有効性判定、include_history=trueで公表履歴も返します。入力は登録番号のみ（氏名等による検索は提供しません）。データ源: 国税庁適格請求書発行事業者公表システムWeb-API。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| registration_number | string | yes | 適格請求書発行事業者登録番号（T+13桁。Tなし13桁・全角・ハイフン空白は吸収） |
| on_date | string | no | 基準日 YYYY-MM-DD（指定時はその日時点で登録が有効だったかを as_of で返す） |
| include_history | boolean | no | 公表履歴（新規登録・変更・取消・失効）を含める（既定false） |
法人番号（13桁・チェックディジット検証つき）からgBizINFOの法人プロファイル（所在地・代表者・資本金・従業員数等）を、項目別の出典・最終取得日メタとあわせて返します。データ源: Gビズインフォ REST API v2（経済産業省）。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| corporate_number | string | yes | 法人番号13桁（全角・ハイフン・空白は吸収。チェックディジット検証あり） |
日本の住所を正規化し、都道府県／市区町村／町字（大字・町名＋丁目）に分解して町字ID（アドレス・ベース・レジストリ）を解決し、郵便番号と照合します（不一致は不一致として明示）。【v1の粒度と限界】分解は町字（大字・丁目）まで。街区符号・住居番号・地番・小字・京都の通り名は解析対象外で、未解析部分は残余文字列としてそのまま返します（推測補完なし）。データ源: アドレス・ベース・レジストリ町字マスター（デジタル庁）＋日本郵便郵便番号データ（ローカルマスター駆動・政府API停止の影響なし）。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | 日本の住所文字列（郵便番号含み可。全半角・漢数字/算用数字・旧字体の表記ゆれ可） |
| postal_code | string | no | 郵便番号を別引数で渡す場合に指定（住所文字列内の記載より優先して照合） |
日本の祝日判定と営業日計算（内閣府「国民の祝日」CSV準拠）。営業日=土日・祝日以外。year_end_as_holiday=trueで12/29〜1/3も非営業日扱い。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| op | string | yes | 操作種別 |
| date | string | no | 基準日 YYYY-MM-DD（list_holidays以外で必須） |
| days | integer | no | 加算する営業日数（add_business_daysで必須。負数=遡り、0=基準日をそのまま返す） |
| from | string | no | 期間開始日（list_holidaysで必須） |
| to | string | no | 期間終了日（list_holidaysで必須） |
| year_end_as_holiday | boolean | no | 12/29〜1/3を非営業日として扱う（官公庁・銀行休業の慣行。既定false=祝日法と土日のみ） |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Jpverify or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.0 · scanned 10 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest0121fe364bb7091e9f4ef904d14886a5796e0bdbfd57ac0b75098c4471c034f0
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest0121fe364bb7091e
Scanned2026-11-10
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Jpverify can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.