Skip to content

HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server

com.hojincheck/hojincheckhojincheck.comstreamable-httpv0.1.0Scanned

Verify Japanese companies, invoice-issuer registrations and addresses against government open data.

6 tools: 1 do something that can't be undone, 3 change things and 2 only read.

Tools: 0 delete, 1 irreversible, 3 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server can do

The HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server is published by hojincheck.com, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (jp_calendar) and create or change data (3 tools: verify_company, verify_invoice_number and normalize_address), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (resolve_company); 1 tool can send data out of your system (jp_calendar).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Can't be undone 1Claude Code: ask
  • jp_calendar日本の祝日判定と営業日計算(内閣府「国民の祝日」CSV準拠)。営業日=土日・祝日以外。year_end_as_holiday=trueで12/29〜1/3も非営業日扱い。Can send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    日本の祝日判定と営業日計算(内閣府「国民の祝日」CSV準拠)。営業日=土日・祝日以外。year_end_as_holiday=trueで12/29〜1/3も非営業日扱い。
Changes things 3Claude Code: ask
  • normalize_address日本の住所を正規化し、都道府県/市区町村/町字(大字・町名+丁目)に分解して町字ID(アドレス・ベース・レジストリ)を解決し、郵便番号と照合します(不一致は不一致として明示)。【v1の粒度と限界】分解は町字(大字・丁目)まで。街区符号・住居番号・地番・小字・京都の通り名は解析対象外で、未解析部分は残余文字列としてそのまま返します(推測補完なし)。データ源: …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    日本の住所を正規化し、都道府県/市区町村/町字(大字・町名+丁目)に分解して町字ID(アドレス・ベース・レジストリ)を解決し、郵便番号と照合します(不一致は不一致として明示)。【v1の粒度と限界】分解は町字(大字・丁目)まで。街区符号・住居番号・地番・小字・京都の通り名は解析対象外で、未解析部分は残余文字列としてそのまま返します(推測補完なし)。データ源: アドレス・ベース・レジストリ町字マスター(デジタル庁)+日本郵便郵便番号データ(ローカルマスター駆動・政府API停止の影響なし)。
  • verify_company法人番号(13桁・チェックディジット検証つき)から実在・商号・本店所在地・法人種別・閉鎖ステータスを返します。include_history=trueで商号変更等の履歴も返します。データ源: 国税庁法人番号システムWeb-API。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    法人番号(13桁・チェックディジット検証つき)から実在・商号・本店所在地・法人種別・閉鎖ステータスを返します。include_history=trueで商号変更等の履歴も返します。データ源: 国税庁法人番号システムWeb-API。
  • verify_invoice_number適格請求書発行事業者の登録番号(T+13桁)から登録有無・登録年月日・取消/失効を返します。on_dateで基準日時点の有効性判定、include_history=trueで公表履歴も返します。入力は登録番号のみ(氏名等による検索は提供しません)。データ源: 国税庁適格請求書発行事業者公表システムWeb-API。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    適格請求書発行事業者の登録番号(T+13桁)から登録有無・登録年月日・取消/失効を返します。on_dateで基準日時点の有効性判定、include_history=trueで公表履歴も返します。入力は登録番号のみ(氏名等による検索は提供しません)。データ源: 国税庁適格請求書発行事業者公表システムWeb-API。
Only reads 2Show 2 read-only tools
  • get_company_profile法人番号(13桁・チェックディジット検証つき)からgBizINFOの法人プロファイル(所在地・代表者・資本金・従業員数等)を、項目別の出典・最終取得日メタとあわせて返します。データ源: Gビズインフォ REST API v2(経済産業省)。No findings

    Why it is in this group

    • The name "get_company_profile" says "get": a word for reading.
    Description, as the server wrote it
    法人番号(13桁・チェックディジット検証つき)からgBizINFOの法人プロファイル(所在地・代表者・資本金・従業員数等)を、項目別の出典・最終取得日メタとあわせて返します。データ源: Gビズインフォ REST API v2(経済産業省)。
  • resolve_company法人名(表記ゆれ・かな/カナ対応)から法人番号の候補と確度(0〜1+根拠ラベル)を返します。データ源: 国税庁法人番号システムWeb-API。Reads text others writeNo findings

    Why it is in this group

    • The name "resolve_company" says "resolve": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    法人名(表記ゆれ・かな/カナ対応)から法人番号の候補と確度(0〜1+根拠ラベル)を返します。データ源: 国税庁法人番号システムWeb-API。

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:40 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://hojincheck.com/mcp: tools/list returned 6 tools to an anonymous client, including jp_calendar (irreversible), verify_company (write), verify_invoice_number (write), normalize_address (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http hojincheck https://hojincheck.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http hojincheck https://hojincheck.com/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hojincheck__resolve_company",
      "mcp__hojincheck__get_company_profile"
    ],
    "ask": [
      "mcp__hojincheck__verify_company",
      "mcp__hojincheck__verify_invoice_number",
      "mcp__hojincheck__normalize_address",
      "mcp__hojincheck__jp_calendar"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hojincheck. Review it before you use it.

Capability tags behind 2 rules
  • mcp__hojincheck__resolve_company untrusted-input
  • mcp__hojincheck__jp_calendar outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.hojincheck/hojincheck/verify?hash=04d6e45a411601baf3ce3982cd9b017cbbaf866a269ae025ef93152829bfc96a" | jq -e '.changed == false'

Pinned hash 04d6e45a4116, from Nov 13, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.hojincheck/hojincheck/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.hojincheck/hojincheck
[![Anlyon Radar](https://radar.anlyon.com/badge/com.hojincheck/hojincheck.svg)](https://radar.anlyon.com/servers/com.hojincheck/hojincheck)

Source: MCP Registry. Synced Oct 21, 2026, 17:56 UTC.

HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: jp_calendar.

What tools does the HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server have?

6 tools: 1 irreversible, 3 write, 2 read. jp_calendar, verify_company, verify_invoice_number, normalize_address, resolve_company and get_company_profile.

Does the HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): jp_calendar.

Has the HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.