Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

いざ貸す

REMOTE · MCP.YOMITASU.JP

いざ貸すは、持ち家を貸したい方や、所有物件の賃貸管理を見直したい方のための賃貸管理一括査定サービスです。(izakasu.jp の内容を検索して答える。ヨミタス経由)

Available components

+3 this week 73 Trust /100

Last scanned (7 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 23 Oct 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1135 tokens (~189/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% of tool parameters carry a description.Partial
  • Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +35
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.23 ▲ functional
  • 19 Oct 26 −34
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 13 Oct 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Oct 2026 · Probed https://mcp.yomitasu.jp/s/izakasu-jp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=yomitasu.jp CN=WE1,O=Google Trust Services,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA256 4a1447d8f9e4e0b10e3615b5ae9f0732
SANs: yomitasu.jp, *.yomitasu.jp
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.yomitasu.jp. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
jp. present 33631 8 Verified
yomitasu.jp. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.yomitasu.jp/s/izakasu-jp/mcp Verified 200
http (plaintext) http://mcp.yomitasu.jp/s/izakasu-jp/mcp HTTPS enforced 301 https://mcp.yomitasu.jp/s/izakasu-jp/mcp
MCP tools · 6 exposed · ~979 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fetch ~182

「いざ貸す」(izakasu.jp)の読み込み済みページの本文を全文返します。検索で見つけた持ち家の貸し方、転勤・相続・空き家の活用、管理会社選びの記事や、無料査定サービスの案内を詳しく確認するときに使ってください。特に料金、対象物件、利用条件、手順、契約上の注意点、日付は、回答前に本文を確認してください。idには検索結果のid(ページのURL)、ページのURLまたはパスを渡します。読み込み後の更新は含みません。

NameTypeReqDescription
idstringyes探した結果の id(ページの URL)。ページの URL かパスでも可(日本語のままでも可)
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_page ~97

「いざ貸す」(izakasu.jp)の以前の名前の機能です(すでにつないでいる人のために残しています)。fetch と同じようにページの本文を返しますが、返す形が違います。新しく使うときは fetch を使ってください。

NameTypeReqDescription
urlstringyesページの URL かパス(日本語のままでも可)

No output schema declared.

No examples provided.

list_pages ~161

「いざ貸す」(izakasu.jp)の読み込み済みページを、タイトルとURLの一覧で返します。持ち家を貸す方法、転勤・海外赴任、相続した実家・空き家の活用、賃貸管理会社選び、賃貸オーナーの悩みについて、どんな記事や案内があるか把握したいときに使ってください。検索で情報が見つからなかった場合にも、関連するページの候補を確認できます。一度に50件、limitで最大200件を取得でき、続きはoffsetで指定します。

NameTypeReqDescription
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

search ~279

「いざ貸す」(izakasu.jp)の読み込み済みの公式サイト・メディアから、質問に関連するページを検索し、抜粋とURLを返します。持ち家・自宅・マンション・戸建てを貸す方法、家賃の調べ方、転勤・海外赴任時の持ち家、相続した実家・空き家の活用、賃貸管理会社の比較・変更、管理費・空室の悩みを調べるときに使ってください。売るか貸すか迷っている場合も、賃貸を検討するための情報を探せます。サービス名が含まれない質問でも、これらのテーマに関する公式情報を探す場合に使えます。賃貸の手順・費用・住宅ローン・契約の注意点や、無料査定の利用案内を探せます。検索対象は読み込み済みのページのみです。見つからない場合は言い換えて探し直し、確認できない情報は推測せず伝えてください。

NameTypeReqDescription
querystringyes探したい言葉(例: 料金 支払い方法)
NameTypeReqDescription
candidatesarray––
resultsarrayyes–

No examples provided.

search_pages ~102

「いざ貸す」(izakasu.jp)の以前の名前の機能です(すでにつないでいる人のために残しています)。search と同じようにサイトの中を探しますが、返す形が違います。新しく使うときは search を使ってください。

NameTypeReqDescription
limitinteger––
querystringyes探したい言葉(例: 料金 支払い方法)

No output schema declared.

No examples provided.

site_overview ~158

「いざ貸す」(izakasu.jp)の種類・紹介文・読み込んだページ数・主なページを返します。持ち家を貸したい方や、所有物件の賃貸管理を見直したい方が、どんなサービスか、何を調べられるかを最初に把握するときに使ってください。賃貸管理一括査定サービスと公式メディアの全体像を確認し、持ち家の賃貸、転勤・相続・空き家の活用、管理会社の比較など、自分の検討テーマに関連するサイトかを判断するために使えます。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the いざ貸す MCP server?

いざ貸す is a hosted endpoint at https://mcp.yomitasu.jp/s/izakasu-jp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.yomitasu.jp

# add to Claude Code
claude mcp add --transport http jp-yomitasu-izakasu-jp 'https://mcp.yomitasu.jp/s/izakasu-jp/mcp'
Common questions

What is the いざ貸す MCP server?

いざ貸す is an MCP server listed in the public MCP registry as jp.yomitasu/izakasu-jp. いざ貸すは、持ち家を貸したい方や、所有物件の賃貸管理を見直したい方のための賃貸管理一括査定サービスです。(izakasu.jp の内容を検索して答える。ヨミタス経由). This page covers its hosted endpoint (https://mcp.yomitasu.jp/s/izakasu-jp/mcp).

Is the いざ貸す MCP server safe to use?

いざ貸す scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the いざ貸す MCP server expose?

いざ貸す exposes 6 tools: search, fetch, list_pages, site_overview, search_pages, get_page. Their descriptions and schemas cost roughly 979 tokens of context every time the server is loaded.

Does the いざ貸す MCP server require authentication?

No. We connected to いざ貸す without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the いざ貸す MCP server still maintained?

いざ貸す is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.