HojinCheck MCP
Provides an MCP server and REST API to verify Japanese corporate entities, qualified invoice issuer registrations, and addresses against Japanese government open data sources. It supports tools for resolving company profiles, normalizing addresses, and calculating business days, with responses embedding data source and timestamp information.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://hojincheck.com/mcpWhat its tools do
6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to hojincheck.com ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Resolve and verify Japanese corporate numbers
- Check qualified invoice issuer (tax) registration status
- Normalize Japanese addresses to town/aza level
- Calculate Japanese business days and holidays
Source and maintenance
Protocol and capabilities
- Server
- hojincheck 0.1.0
- MCP protocol negotiated in check
- 2025-11-25
- Tools
- 6 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- Not advertised
{
"tools": {
"listChanged": true
}
}Tools
6 advertised
resolve_company — 法人名から法人番号を解決
法人名(表記ゆれ・かな/カナ対応)から法人番号の候補と確度(0〜1+根拠ラベル)を返します。データ源: 国税庁法人番号システムWeb-API。
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "法人名((株)等の略記・全半角・かな/カナ・旧字体の表記ゆれ可)"
},
"limit": {
"type": "integer",
"default": 10,
"maximum": 50,
"minimum": 1,
"description": "返却する候補数の上限(既定10)"
},
"address": {
"type": "string",
"pattern": "^\\d{2}(\\d{3})?$",
"description": "所在地で絞り込み: 都道府県コード2桁(JIS X 0401)または+市区町村コード3桁の計5桁"
},
"include_closed": {
"type": "boolean",
"default": true,
"description": "閉鎖法人を候補に含める(既定true)"
}
},
"additionalProperties": false
}verify_company — 法人番号の実在検証
法人番号(13桁・チェックディジット検証つき)から実在・商号・本店所在地・法人種別・閉鎖ステータスを返します。include_history=trueで商号変更等の履歴も返します。データ源: 国税庁法人番号システムWeb-API。
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"corporate_number"
],
"properties": {
"include_history": {
"type": "boolean",
"default": false,
"description": "商号変更等の履歴を含める(既定false)"
},
"corporate_number": {
"type": "string",
"maxLength": 30,
"minLength": 1,
"description": "法人番号13桁(全角・ハイフン・空白は吸収)"
}
},
"additionalProperties": false
}verify_invoice_number — 適格請求書発行事業者登録番号の検証
適格請求書発行事業者の登録番号(T+13桁)から登録有無・登録年月日・取消/失効を返します。on_dateで基準日時点の有効性判定、include_history=trueで公表履歴も返します。入力は登録番号のみ(氏名等による検索は提供しません)。データ源: 国税庁適格請求書発行事業者公表システムWeb-API。
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"registration_number"
],
"properties": {
"on_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "基準日 YYYY-MM-DD(指定時はその日時点で登録が有効だったかを as_of で返す)"
},
"include_history": {
"type": "boolean",
"default": false,
"description": "公表履歴(新規登録・変更・取消・失効)を含める(既定false)"
},
"registration_number": {
"type": "string",
"maxLength": 30,
"minLength": 1,
"description": "適格請求書発行事業者登録番号(T+13桁。Tなし13桁・全角・ハイフン空白は吸収)"
}
},
"additionalProperties": false
}get_company_profile — 法人プロファイル取得(gBizINFO)
法人番号(13桁・チェックディジット検証つき)からgBizINFOの法人プロファイル(所在地・代表者・資本金・従業員数等)を、項目別の出典・最終取得日メタとあわせて返します。データ源: Gビズインフォ REST API v2(経済産業省)。
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"corporate_number"
],
"properties": {
"corporate_number": {
"type": "string",
"maxLength": 30,
"minLength": 1,
"description": "法人番号13桁(全角・ハイフン・空白は吸収。チェックディジット検証あり)"
}
},
"additionalProperties": false
}normalize_address — 日本住所の正規化・要素分解・郵便番号照合
日本の住所を正規化し、都道府県/市区町村/町字(大字・町名+丁目)に分解して町字ID(アドレス・ベース・レジストリ)を解決し、郵便番号と照合します(不一致は不一致として明示)。【v1の粒度と限界】分解は町字(大字・丁目)まで。街区符号・住居番号・地番・小字・京都の通り名は解析対象外で、未解析部分は残余文字列としてそのまま返します(推測補完なし)。データ源: アドレス・ベース・レジストリ町字マスター(デジタル庁)+日本郵便郵便番号データ(ローカルマスター駆動・政府API停止の影響なし)。
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "日本の住所文字列(郵便番号含み可。全半角・漢数字/算用数字・旧字体の表記ゆれ可)"
},
"postal_code": {
"type": "string",
"pattern": "^\\d{3}-?\\d{4}$",
"description": "郵便番号を別引数で渡す場合に指定(住所文字列内の記載より優先して照合)"
}
},
"additionalProperties": false
}jp_calendar — 日本の祝日・営業日計算
日本の祝日判定と営業日計算(内閣府「国民の祝日」CSV準拠)。営業日=土日・祝日以外。year_end_as_holiday=trueで12/29〜1/3も非営業日扱い。
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"op"
],
"properties": {
"op": {
"enum": [
"is_business_day",
"next_business_day",
"prev_business_day",
"add_business_days",
"list_holidays"
],
"type": "string",
"description": "操作種別"
},
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "期間終了日(list_holidaysで必須)"
},
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "基準日 YYYY-MM-DD(list_holidays以外で必須)"
},
"days": {
"type": "integer",
"maximum": 1000,
"minimum": -1000,
"description": "加算する営業日数(add_business_daysで必須。負数=遡り、0=基準日をそのまま返す)"
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "期間開始日(list_holidaysで必須)"
},
"year_end_as_holiday": {
"type": "boolean",
"default": false,
"description": "12/29〜1/3を非営業日として扱う(官公庁・銀行休業の慣行。既定false=祝日法と土日のみ)"
}
},
"additionalProperties": false
}Prompts
Not advertised
Resources
Not advertised
90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-07: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 208 ms
- 95th percentile latency
- 208 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 208 ms · metadata changed · 6 tool(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http hojincheck-mcp https://hojincheck.com/mcpCodex
codex mcp add hojincheck-mcp --url https://hojincheck.com/mcpCursor
{
"mcpServers": {
"hojincheck-mcp": {
"url": "https://hojincheck.com/mcp"
}
}
}Cline
{
"mcpServers": {
"hojincheck-mcp": {
"type": "streamableHttp",
"url": "https://hojincheck.com/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"hojincheck-mcp": {
"type": "http",
"url": "https://hojincheck.com/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http hojincheck-mcp https://hojincheck.com/mcpClaude Desktop
https://hojincheck.com/mcpWindsurf
{
"mcpServers": {
"hojincheck-mcp": {
"serverUrl": "https://hojincheck.com/mcp"
}
}
}Let your agent find its tools
Find servers like HojinCheck MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other data and analytics servers
Do you run HojinCheck MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.