Remote MCP · Endpoint

不動産競売 構造化データハブ — Japan real-estate auctions MCP server

Yes, as of 2 hours ago: the check failed for an unclassified reason.

DownLast checked 2 hours ago

Server URL

https://keibai-hub.com/mcp-auctions

The last check failed: the check failed for an unclassified reason.

Registry name
io.github.keibai-hub/keibai-hub-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
44.4% from 18 checks
Described by its publisher as
Japanese court-run real-estate auctions (BIT). 5 tools, ~1,480 active listings. CC BY 4.0.
Repository
https://github.com/keibai-hub/keibai-hub-mcp
Listing
From the official MCP registry (active).
Recent checks of 不動産競売 構造化データハブ — Japan real-estate auctions
CheckedResultHandshake
2 hours agoFailed - the check failed for an unclassified reason—
1 day agoFailed - the check failed for an unclassified reason—
3 days agoFailed - the check failed for an unclassified reason—
3 days agoFailed - the check failed for an unclassified reason—
4 days agoFailed - the check failed for an unclassified reason—
5 days agoFailed - the check failed for an unclassified reason—
7 days agoFailed - the check failed for an unclassified reason—
10 days agoFailed - the check failed for an unclassified reason—
12 days agoFailed - the check failed for an unclassified reason—
15 days agoFailed - the check failed for an unclassified reason—
17 days agoHandshake completed331 ms
19 days agoHandshake completed108 ms
21 days agoHandshake completed284 ms
23 days agoHandshake completed353 ms
25 days agoHandshake completed410 ms
26 days agoHandshake completed73 ms
28 days agoHandshake completed327 ms
29 days agoHandshake completed98 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 19 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with 不動産競売 構造化データハブ — Japan real-estate auctions and makes no claim about it beyond what these checks measured.