Remote MCP · Endpoint

いざ貸す MCP server

No. いざ貸す answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://mcp.yomitasu.jp/s/izakasu-jp/mcp

The last check completed an MCP handshake.

Registry name
jp.yomitasu/izakasu-jp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
846 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
いざ貸すは、持ち家を貸したい方や、所有物件の賃貸管理を見直したい方のための賃貸管理一括査定サービスです。(izakasu.jp の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of いざ貸す
CheckedResultHandshake
43 minutes agoHandshake completed846 ms
8 days agoHandshake completed738 ms
9 days agoHandshake completed6.07 s
11 days agoHandshake completed678 ms
12 days agoHandshake completed647 ms
13 days agoHandshake completed665 ms
14 days agoHandshake completed631 ms
14 days agoHandshake completed631 ms
16 days agoHandshake completed636 ms
19 days agoHandshake completed690 ms
21 days agoHandshake completed620 ms
24 days agoHandshake completed662 ms
26 days agoHandshake completed665 ms
28 days agoHandshake completed658 ms

The last 14 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 いざ貸す and makes no claim about it beyond what these checks measured.