Remote MCP · Endpoint
HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) MCP server
No. HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://hojincheck.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.hojincheck/hojincheck
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 434 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Verify Japanese companies, invoice-issuer registrations and addresses against government open data.
- Website
- https://hojincheck.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 434 ms |
| 1 day ago | Handshake completed | 56 ms |
| 3 days ago | Handshake completed | 209 ms |
| 3 days ago | Handshake completed | 235 ms |
| 4 days ago | Handshake completed | 213 ms |
| 5 days ago | Handshake completed | 195 ms |
| 7 days ago | Handshake completed | 158 ms |
| 10 days ago | Handshake completed | 160 ms |
| 12 days ago | Handshake completed | 221 ms |
| 15 days ago | Handshake completed | 179 ms |
| 17 days ago | Handshake completed | 476 ms |
| 19 days ago | Handshake completed | 276 ms |
| 21 days ago | Handshake completed | 194 ms |
| 23 days ago | Handshake completed | 198 ms |
| 25 days ago | Handshake completed | 30 ms |
| 26 days ago | Handshake completed | 320 ms |
| 28 days ago | Handshake completed | 97 ms |
| 29 days ago | Handshake completed | 159 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with HojinCheck — Japanese corporate verification API (hojin = 法人/corporate entity) and makes no claim about it beyond what these checks measured.