Remote MCP · Endpoint

不動産情報検索・分析 MCP MCP server

No. 不動産情報検索・分析 MCP answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://mcp.n-3.ai/mcp?tools=kkj-search

The last check completed an MCP handshake.

Registry name
io.github.n-3inc/kkj
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
48 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
中小企業庁が公開している公共調達情報を検索するためのサービスです。
Listing
From the official MCP registry (active).
Recent checks of 不動産情報検索・分析 MCP
CheckedResultHandshake
1 day agoHandshake completed48 ms
4 days agoHandshake completed483 ms
5 days agoHandshake completed368 ms
7 days agoHandshake completed62 ms
8 days agoHandshake completed495 ms
9 days agoHandshake completed351 ms
12 days agoHandshake completed338 ms
13 days agoHandshake completed331 ms
15 days agoHandshake completed330 ms
16 days agoHandshake completed44 ms
18 days agoHandshake completed52 ms
19 days agoHandshake completed698 ms
20 days agoHandshake completed32 ms
20 days agoHandshake completed478 ms
21 days agoHandshake completed38 ms
22 days agoHandshake completed39 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

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 不動産情報検索・分析 MCP and makes no claim about it beyond what these checks measured.