Is the Hojincheck MCP server down?

mcp-registry/com.hojincheck/hojincheck · v0.1.0

healthy
Last checked 2026-10-25 18:54 UTC · handshake 116ms

As of 2026-10-25 18:54 UTC, the Hojincheck MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,753
outages (90d)
0
tools
6

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

Install Hojincheck MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http hojincheck-mcp-server https://hojincheck.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "hojincheck-mcp-server": {
      "type": "http",
      "url": "https://hojincheck.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 6 tool(s); ~1,113 tokens of tool definitions.
Scores higher than 45% of 15,725 MCP servers Glimind has audited.
Its tool list costs an agent ~1,113 tokens per session — lighter than 75% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_company_profile, jp_calendar, normalize_address, resolve_company, verify_company and 1 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.hojincheck%2Fhojincheck/fixes

get_company_profile 1 change 
{
  "name": "get_company_profile",
  "description": "法人番号（13桁・チェックディジット検証つき）からgBizINFOの法人プロファイル（所在地・代表者・資本金・従業員数等）を、項目別の出典・最終取得日メタとあわせて返します。データ源: Gビズインフォ REST API v2（経済産業省）。",
  "inputSchema": {
    "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
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "法人プロファイル取得（gBizINFO）"
}
normalize_address 1 change 
{
  "name": "normalize_address",
  "description": "日本の住所を正規化し、都道府県／市区町村／町字（大字・町名＋丁目）に分解して町字ID（アドレス・ベース・レジストリ）を解決し、郵便番号と照合します（不一致は不一致として明示）。【v1の粒度と限界】分解は町字（大字・丁目）まで。街区符号・住居番号・地番・小字・京都の通り名は解析対象外で、未解析部分は残余文字列としてそのまま返します（推測補完なし）。データ源: アドレス・ベース・レジストリ町字マスター（デジタル庁）＋日本郵便郵便番号データ（ローカルマスター駆動・政府API停止の影響なし）。",
  "inputSchema": {
    "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
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "日本住所の正規化・要素分解・郵便番号照合"
}
resolve_company 1 change 
{
  "name": "resolve_company",
  "description": "法人名（表記ゆれ・かな/カナ対応）から法人番号の候補と確度（0〜1＋根拠ラベル）を返します。データ源: 国税庁法人番号システムWeb-API。",
  "inputSchema": {
    "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
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "法人名から法人番号を解決"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.hojincheck/hojincheck"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.hojincheck/hojincheck"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.hojincheck%2Fhojincheck.svg)](https://glimind.com/server/mcp-registry%2Fcom.hojincheck%2Fhojincheck?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fcom.hojincheck%2Fhojincheck?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.hojincheck%2Fhojincheck.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.hojincheck%2Fhojincheck.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.hojincheck%2Fhojincheck?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:de92392a6f12b35a…, first seen 2026-10-17, included at leaf 13661 of 67,966. Version history · verify what your client received.

Tools (6)

Compare: most reliable data servers · most reliable calendar servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Hojincheck MCP server down right now?

As of 2026-10-25 18:54 UTC, the Hojincheck MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Hojincheck MCP server provide?

Hojincheck MCP server advertises 6 tools, including get_company_profile, jp_calendar, normalize_address, resolve_company, verify_company.

How do I install Hojincheck MCP server?

Point your MCP client at this streamable-http endpoint: https://hojincheck.com/mcp

Is the Hojincheck MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Hojincheck MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve