_ registry / mcp streamable-http · checked 1h ago

livinisto-cz

https://www.livinisto.cz

Registry code: 3d683544c4916e85

api record

LivinIsto is a Czech property listings portal: agencies and sellers publish their own listings on LivinIsto directly, and it also indexes public listings from Czech property portals with a link to the original ad. Homes only (flats, houses, cottages, building plots), sale and rent. Prices in CZK. Use search_properties with one short Czech phrase of concrete criteria. If `notUnderstood` is not empty, tell the user those words were NOT applied; if `matchedInText` is not empty, say those words were only matched in the listing text. Never present such results as an exact match. If `relaxed` is…

endpoint
https://www.livinisto.cz/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is livinisto-cz live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is livinisto-cz free to use?
Yes — the hub reached it with no key and no payment.
What tools does livinisto-cz have?
3 tools: get_price_per_m2, get_property_details, search_properties.
Is livinisto-cz safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
258ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_price_per_m2 unknown 1h ago

    Use this when the user asks how much homes cost per square metre in a Czech town or city part, or whether a price per m² is reasonable. Returns the median ASKING price per m² of the municipality (monthly for rent) from LivinIsto's monthly index, with the sample size and month; with a layout (2+kk, 3+1…) also the median of today's comparable listings. No median below 8 listings. These are prices sellers ask, not sale prices; location, condition and floor move the price, so present it as a guide. An unknown place returns found: false — never a national figure. Do not use it to value a specific property's condition, for commercial property or for places outside the Czech Republic.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "location"
      ],
      "properties": {
        "layout": {
          "type": "string",
          "pattern": "^\\s*[1-6]\\s*\\+\\s*(kk|KK|1)\\s*$",
          "description": "Czech layout such as 2+kk or 3+1 (optional)."
        },
        "location": {
          "type": "string",
          "maxLength": 100,
          "minLength": 2,
          "description": "Municipality or city part in Czech, e.g. Brno, Kolín, Praha 5, Smíchov."
        },
        "transaction": {
          "enum": [
            "prodej",
            "pronajem"
          ],
          "type": "string",
          "description": "prodej (sale, default) or pronajem (rent; figures are monthly)."
        },
        "propertyType": {
          "enum": [
            "byt",
            "dum",
            "chata",
            "pozemek",
            "apartman"
          ],
          "type": "string",
          "description": "byt (flat, default), dum (house), chata (cottage), pozemek (building plot), apartman."
        }
      }
    }
    arguments 39 lines
  • get_property_details unknown 1h ago

    Use this when the user asks for more about one specific home returned by search_properties (floor, condition, construction, ownership, energy class, balcony, lift, parking, price history). Requires the property id from search_properties; do not guess ids. Returns the facts LivinIsto shows on the listing page and its price verdict; it does not return the name, phone or e-mail of the agent or seller, the listing description or the source URL — for contact the user opens the listing's url. If the listing is no longer in the offer, found is false.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "propertyId"
      ],
      "properties": {
        "propertyId": {
          "type": "string",
          "maxLength": 40,
          "minLength": 8,
          "description": "The id of a property from search_properties results."
        }
      }
    }
    arguments 15 lines
  • search_properties unknown 1h ago

    Use this when the user wants to find a home for sale or rent in the Czech Republic — a flat, house, cottage or building plot — by layout (2+kk, 3+1…), town, district or city part, price, floor area or features. Covers listings agencies and sellers published on LivinIsto directly and public listings from Czech property portals. Pass the criteria as ONE short phrase in Czech (Slovak also works), with numbers as the user said them. Examples that are fully understood: "byt 2+kk Praha do 6 milionů", "pronájem 1+1 Brno do 15000", "rodinný dům Plzeň do 8 milionů", "pozemek Kolín". Leave out filler words (hledám, prosím, pěkný); words that are not a recognised filter are either matched in the listing text (matchedInText) or not applied (notUnderstood). At most 6 such unrecognised words are matched in the text; any beyond that are returned in notUnderstood. Returns up to 10 homes, what was understood, which criteria were relaxed when nothing matched exactly, which words were not applied, and a link to all results. Limits: only homes currently listed on LivinIsto (Czech Republic, prices in CZK, rents monthly); no commercial property, garages, holiday stays or property abroad; the offer changes daily, so a home may already be gone.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 300,
          "minLength": 2,
          "description": "Concrete criteria in Czech, e.g. \"byt 3+kk Brno do 7 milionů\" or \"pronájem 2+1 Ostrava\"."
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3d683544c4916e85.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3d683544c4916e85/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3d683544c4916e85/badge.svg)](https://brick.blue/agent/3d683544c4916e85?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.