# LivinIsto — home watch (remote · www.livinisto.sk)

Watches Slovak home listings for a buyer. Takes no contact; active only after e-mail opt-in.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.livinisto.sk`: 72/100 (this document), [markdown](https://verifymcp.io/servers/sk-livinisto-intents/mcp-zamery.md), [page](https://verifymcp.io/servers/sk-livinisto-intents/mcp-zamery)

## Channel facts

- Endpoint: `https://www.livinisto.sk/mcp/zamery`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (intent_withdraw_intent).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1303 tokens (~260/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (80% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the LivinIsto — home watch MCP server?

LivinIsto — home watch is a hosted endpoint at https://www.livinisto.sk/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.

### Claude

```bash
claude mcp add --transport http sk-livinisto-intents 'https://www.livinisto.sk/mcp/zamery'
```

### Cursor

```json
{
  "mcpServers": {
    "sk-livinisto-intents": {
      "url": "https://www.livinisto.sk/mcp/zamery"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sk-livinisto-intents": {
      "type": "http",
      "url": "https://www.livinisto.sk/mcp/zamery"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sk-livinisto-intents]
url = "https://www.livinisto.sk/mcp/zamery"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sk-livinisto-intents": {
      "type": "remote",
      "url": "https://www.livinisto.sk/mcp/zamery",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sk-livinisto-intents --url 'https://www.livinisto.sk/mcp/zamery' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sk-livinisto-intents:
    url: "https://www.livinisto.sk/mcp/zamery"
```

### Netclaw

```json
{
  "McpServers": {
    "sk-livinisto-intents": {
      "Transport": "http",
      "Url": "https://www.livinisto.sk/mcp/zamery"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sk-livinisto-intents -t streamable-http -u 'https://www.livinisto.sk/mcp/zamery'
```

### Other

```json
{
  "mcpServers": {
    "sk-livinisto-intents": {
      "type": "http",
      "url": "https://www.livinisto.sk/mcp/zamery"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 72, +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.

### 2026-11-01 (score 71, +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.

### 2026-10-30 (score 70, +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.

### 2026-10-28 (score 69, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Tool coverage: 100% → 80%
- [functional regression] Schema quality: 1022 → 1303
- [functional] New tool “intent_search_offers”

### 2026-10-26 (score 68, +1)

- [cosmetic] “intent_publish_intent” added an optional parameter “lang”

### 2026-10-23 (score 67, +1)

- [security] 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

### 2026-10-22 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-21 (score 66)

First indexed and scored.

## MCP tools (5)

### `intent_publish_intent` (~462 tokens)

Watch new property listings for the user (needs the user's confirmation)

Use this when the user asks LivinIsto to keep watching Slovak property listings (flats, houses, cottages, plots; for sale or rent) for them over time (e.g. "let me know until March about a 2-room flat in Žilina under 150 000 €"). This does NOT start watching by itself and takes no e-mail address or other personal data: it returns a consentUrl on www.livinisto.sk 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 properties are e-mailed to the user and can also be read with intent_list_matches using the returned intentCode — keep it in the conversation. hiddenLimitEur is optional: the most the user would pay (for a rental, per month), 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 Slovak market (its own listings and public listings from Slovak property portals), so they cover only properties listed on LivinIsto (Slovakia only, EUR) and may be incomplete.

Input parameters:

- `buyBy` (string): Date (YYYY-MM-DD) by which the user wants to buy or rent; watching stops after it.
- `hiddenLimitEur` (integer): Optional private maximum price in EUR (for a rental, per month); 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. "balkón, výťah".
- `statement` (string, required): What the property MUST be, as one short Slovak phrase, e.g. "2-izbový byt Žilina do 150 000 €" or "prenájom 1-izbový byt Bratislava do 700 €".

Output parameters:

- `buyBy` (string|null)
- `consentExpiresAt` (string): ISO time after which the unconfirmed draft is deleted.
- `consentUrl` (string): Page on www.livinisto.sk where the USER confirms the intent with their own e-mail. Show it unchanged.
- `hasHiddenLimit` (boolean): Whether a hidden limit was stored. Its value is never returned.
- `intentCode` (string): Secret code of this intent; use it with intent_get_intent, intent_list_matches and intent_withdraw_intent.
- `niceToHave` (string|null)
- `notUnderstood` (array): Words of the statement that are NOT watched for as a filter. Tell the person.
- `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…
- `understood` (array): What LivinIsto will watch for, read from the statement (in Slovak). Tell the person before they confirm.

### `intent_get_intent` (~82 tokens)

Get the state of a property watch

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.

Input parameters:

- `intentCode` (string, required): The intentCode returned by intent_publish_intent.

Output parameters:

- `activeSince` (string|null)
- `buyBy` (string|null)
- `found` (boolean)
- `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).

### `intent_list_matches` (~191 tokens)

List properties found for a property watch

Use this when the user asks what LivinIsto has found for an intent created with intent_publish_intent. These are the same properties 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 price and LivinIsto price verdict (per m², against comparable properties nearby) 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 properties listed on LivinIsto and may be incomplete; a property may already be sold or rented.

Input parameters:

- `intentCode` (string, required): The intentCode returned by intent_publish_intent.
- `since` (string): Only matches found after this ISO time.

Output parameters:

- `found` (boolean)
- `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…

### `intent_withdraw_intent` (~69 tokens)

Stop a property watch

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.

Input parameters:

- `intentCode` (string, required): The intentCode returned by intent_publish_intent.

Output parameters:

- `found` (boolean)
- `status` (string)

### `intent_search_offers` (~248 tokens)

Search properties LivinIsto offers today

Use this when the user wants to find a flat, house, cottage or plot for sale or rent in Slovakia now. Pass what they are looking for as one short phrase (Slovak works best), e.g. "2-izbový byt Bratislava do 200000 €". Returns up to 20 properties from LivinIsto's offer in LivinIsto's own order, each with a link to the property on www.livinisto.sk, 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 Slovak market and may be incomplete; no seller or agent contact is returned.

Input parameters:

- `limit` (integer): At most this many properties (default 10; LivinIsto returns at most 10).
- `statement` (string, required): What the user is looking for, e.g. "dom Žilina do 250000 €".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sk-livinisto-intents/mcp-zamery#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-10-23: 67
- 2026-10-22: 66
- 2026-10-21: 66

## Common questions

### What is the LivinIsto — home watch MCP server?

LivinIsto — home watch is an MCP server listed in the public MCP registry as sk.livinisto/intents. Watches Slovak home listings for a buyer. Takes no contact; active only after e-mail opt-in. This page covers its hosted endpoint (https://www.livinisto.sk/mcp/zamery).

### Is the LivinIsto — home watch MCP server safe to use?

LivinIsto — 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 — home watch MCP server expose?

LivinIsto — 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,052 tokens of context every time the server is loaded.

### Does the LivinIsto — home watch MCP server require authentication?

No. We connected to LivinIsto — home watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LivinIsto — home watch MCP server still maintained?

LivinIsto — 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.

## Links

- Remote endpoint: https://www.livinisto.sk/mcp/zamery
- Website: https://www.livinisto.sk/
- Changelog RSS feed: https://verifymcp.io/servers/sk-livinisto-intents/mcp-zamery.xml
- Changelog JSON feed: https://verifymcp.io/servers/sk-livinisto-intents/mcp-zamery.json
- HTML version of this page: https://verifymcp.io/servers/sk-livinisto-intents/mcp-zamery