LivinIsto CZ — home watch
REMOTE · WWW.LIVINISTO.CZ
Watches Czech home listings for a buyer. Takes no contact; active only after e-mail opt-in.
Available components
Last scanned (6 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (intent_withdraw_intent). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1284 tokens (~256/item across 5 items; 5 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (80% 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 30 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.
- 28 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 100% → 80% ▼ functional
- Schema quality: 1003 → 1284 ▼ functional
- New tool “intent_search_offers” functional
- 26 Oct 26 +1
- “intent_publish_intent” added an optional parameter “lang” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 23 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “intent_list_matches” rewrote its description, which is the text the model reads security
- Tool “intent_publish_intent” rewrote its description, which is the text the model reads security
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 66
First indexed and scored.
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 5 Nov 2026 · Probed https://www.livinisto.cz/mcp/zamery
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=livinisto.cz | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d0bb9703a127309c1337b50040b04f51 |
| SANs: livinisto.cz, *.livinisto.cz | ||||||
| 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 www.livinisto.cz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cz. | DS published | 20237 | 13 | Verified |
| livinisto.cz. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-ODFiNDI1NTktNDZlMy00ZTFkLWI5MzMtOWM0ZTUxZDFkN2Ew' 'strict-dynamic'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://*.sdn.cz https://*.bazos.cz https://*.bezrealitky.cz; font-src 'self'; connect-src 'self'; manifest-src 'self'; worker-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.livinisto.cz/mcp/zamery | Verified | 200 | |
| http (plaintext) | http://www.livinisto.cz/mcp/zamery | HTTPS enforced | 301 | https://www.livinisto.cz/mcp/zamery |
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 →
intent_get_intent Get the state of a property watch ~82
Use this to check whether an intent created with intent_publish_intent is already confirmed by the user and active, waiting, expired or withdrawn. Requires the intentCode; returns the statement and dates only — never the user's e-mail, the hidden limit or any other personal data.
| Name | Type | Req | Description |
|---|---|---|---|
| intentCode | string | yes | The intentCode returned by intent_publish_intent. |
| Name | Type | Req | Description |
|---|---|---|---|
| activeSince | string|null | – | – |
| buyBy | string|null | – | – |
| found | boolean | yes | – |
| hasHiddenLimit | boolean | – | – |
| niceToHave | string|null | – | – |
| statement | string | – | – |
| status | string | – | awaiting_consent = the user has not confirmed on the LivinIsto page yet; awaiting_email_confirmation = the user filled in the page and must click the link in the e-mail; active = LivinIsto is watchin… |
| validUntil | string | – | Date (YYYY-MM-DD) until which the intent is watched (before confirmation: until the draft is deleted). |
No examples provided.
intent_list_matches List homes found for a property watch ~182
Use this when the user asks what LivinIsto has found for an intent created with intent_publish_intent. These are the same homes LivinIsto e-mails to the user; this server cannot send messages into the conversation by itself. Requires the intentCode; optional since (ISO time) returns only newer matches. Returns at most 20 newest matches with the asking price and LivinIsto price verdict at the time of the match and a link. Before the user confirms the intent there are no matches. Matches come from listings LivinIsto aggregates from the market, so they cover only homes listed on LivinIsto and may be incomplete; a home may already be sold or rented.
| Name | Type | Req | Description |
|---|---|---|---|
| intentCode | string | yes | The intentCode returned by intent_publish_intent. |
| since | string | – | Only matches found after this ISO time. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| matches | array | – | – |
| more | boolean | – | More matches exist than returned; call again with since. |
| status | string | – | awaiting_consent = the user has not confirmed on the LivinIsto page yet; awaiting_email_confirmation = the user filled in the page and must click the link in the e-mail; active = LivinIsto is watchin… |
No examples provided.
intent_publish_intent Watch new Czech property listings for the user (needs the user's confirmation) ~458
Use this when the user asks LivinIsto to keep watching Czech property listings (flats, houses, cottages, building plots; sale or rent) for them over time (e.g. "let me know until March about a 2+kk flat in Brno under 5 million CZK"). This does NOT start watching by itself and takes no e-mail address or other personal data: it returns a consentUrl on www.livinisto.cz that the user must open themselves, enter their own e-mail there and confirm by clicking the link LivinIsto e-mails them. Never ask the user for their e-mail in the conversation and never open the link for them. An unconfirmed draft is deleted after 24 hours. Matching homes are e-mailed to the user and can also be read with intent_list_matches using the returned intentCode — keep it in the conversation. hiddenLimitCzk is optional: the most the user would pay in CZK (monthly for rent), stored encrypted and never shown to sellers or returned by any tool; pass it only if the user said it. Matches come from listings LivinIsto aggregates from the Czech market (its own listings and public listings from Czech property portals), so they cover only homes listed on LivinIsto (Czech Republic, prices in CZK) and may be incomplete; no commercial property and nothing abroad.
| Name | Type | Req | Description |
|---|---|---|---|
| buyBy | string | – | Date (YYYY-MM-DD) by which the user wants to buy or rent; watching stops after it. |
| hiddenLimitCzk | integer | – | Optional private maximum price in CZK (monthly for rent); encrypted on receipt and never returned by any tool. |
| lang | string | – | Optional language of the replies (texts only; codes, URLs and statuses never change). By default the language of the statement. |
| niceToHave | string | – | Wishes that are not required (never filters), e.g. "balkon, výtah". |
| statement | string | yes | What the home MUST be, as one short Czech phrase, e.g. "byt 2+kk Brno do 5 milionů" or "pronájem 1+kk Praha do 18000". |
| Name | Type | Req | Description |
|---|---|---|---|
| buyBy | string|null | yes | – |
| consentExpiresAt | string | yes | ISO time after which the unconfirmed draft is deleted. |
| consentUrl | string | yes | Page on www.livinisto.cz where the USER confirms the intent with their own e-mail. Show it unchanged. |
| hasHiddenLimit | boolean | yes | Whether a hidden limit was stored. Its value is never returned. |
| intentCode | string | yes | Secret code of this intent; use it with intent_get_intent, intent_list_matches and intent_withdraw_intent. |
| niceToHave | string|null | yes | – |
| notUnderstood | array | yes | Words of the statement that are NOT watched for as a filter. Tell the person. |
| statement | string | yes | – |
| status | string | yes | awaiting_consent = the user has not confirmed on the LivinIsto page yet; awaiting_email_confirmation = the user filled in the page and must click the link in the e-mail; active = LivinIsto is watchin… |
| understood | array | yes | What LivinIsto will watch for, read from the statement (in Czech). Tell the person before they confirm. |
No examples provided.
intent_search_offers Search homes LivinIsto offers today ~248
Use this when the user wants to find a flat, house, cottage or plot for sale or rent in the Czech Republic now. Pass what they are looking for as one short phrase (Czech works best), e.g. "byt 2+kk Brno do 6 milionů". Returns up to 20 homes from LivinIsto's offer in LivinIsto's own order, each with a link to the home on www.livinisto.cz, plus what was understood, which words were not applied and what had to be relaxed. For rent the price is per month. When suggestIntent is true (nothing or little found, or part of the phrase was dropped), offer the user intent_publish_intent with the same statement so LivinIsto keeps watching. Results come from listings LivinIsto aggregates from the Czech market and may be incomplete; no seller or agent contact is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | At most this many homes (default 10; LivinIsto returns at most 10). |
| statement | string | yes | What the user is looking for, e.g. "dům Plzeň do 8 milionů". |
No output schema declared.
No examples provided.
intent_withdraw_intent Stop a property watch ~69
Use this when the user wants LivinIsto to stop watching for an intent created with intent_publish_intent. Takes effect immediately; nothing more is e-mailed for it. Requires the intentCode.
| Name | Type | Req | Description |
|---|---|---|---|
| intentCode | string | yes | The intentCode returned by intent_publish_intent. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| status | string | – | – |
No examples provided.
How do I install the LivinIsto CZ — home watch MCP server?
LivinIsto CZ — home watch is a hosted endpoint at https://www.livinisto.cz/mcp/zamery, 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 · www.livinisto.cz
claude mcp add --transport http cz-livinisto-intents 'https://www.livinisto.cz/mcp/zamery'
What is the LivinIsto CZ — home watch MCP server?
LivinIsto CZ — home watch is an MCP server listed in the public MCP registry as cz.livinisto/intents. Watches Czech home listings for a buyer. Takes no contact; active only after e-mail opt-in. This page covers its hosted endpoint (https://www.livinisto.cz/mcp/zamery).
Is the LivinIsto CZ — home watch MCP server safe to use?
LivinIsto CZ — home watch scores 72 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 LivinIsto CZ — home watch MCP server expose?
LivinIsto CZ — home watch exposes 5 tools: intent_publish_intent, intent_get_intent, intent_list_matches, intent_withdraw_intent, intent_search_offers. Their descriptions and schemas cost roughly 1,039 tokens of context every time the server is loaded.
Does the LivinIsto CZ — home watch MCP server require authentication?
No. We connected to LivinIsto CZ — home watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LivinIsto CZ — home watch MCP server still maintained?
LivinIsto CZ — home watch is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the LivinIsto CZ — home watch MCP server?
VerifyMCP ran 13 checks on LivinIsto CZ — home watch, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.