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.

otthon & üzlet

REMOTE · MCP.OTTHONESUZLET.HU

Hungarian home and shop listings with sealed-offer auctions: search, details, seller drafts.

65 Trust /100

Last scanned (1 hour ago)

Scores higher than 45% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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 Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2100 tokens (~262/item across 8 items; 7 tools + 1 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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 55% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 4 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “ingatlan_search_listings” rewrote its description, which is the text the model reads security
    • Schema quality: 213 → 262 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • “ingatlan_search_listings” added an optional parameter “filters” cosmetic
    • “ingatlan_search_listings” reworded the description of “building” cosmetic
    • “ingatlan_search_listings” reworded the description of “text” cosmetic
  • 3 Nov 26 65

    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 5 Nov 2026 · Probed https://mcp.otthonesuzlet.hu

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.otthonesuzlet.hu CN=YR1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 RSA 2048 SHA256-RSA 678e9ea457f06461d646616f5628378b5e0
SANs: mcp.otthonesuzlet.hu
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.otthonesuzlet.hu. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
hu. present 46162 8 Verified
otthonesuzlet.hu. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self' https://reservoprix.storage.googleapis.com https://storage.googleapis.com; script-src 'self' 'nonce-3Z5PxEr2tWEZnKQY' https://reservoprix.lm.r.appspot.com https://accounts.google.com https://www.googletagmanager.com https://reservoprix.storage.googleapis.com https://storage.googleapis.com https://spocont.com https://hiranytu.hu https://aktualis.info https://hungarian.news https://booboooking.com https://ekkor.hu https://karfelmero.hu https://cdn.jsdelivr.net https://maps.googleapis.com https://maps.gstatic.com; style-src 'self' 'unsafe-inline' https://fonts.gstatic.com https://fonts.googleapis.com https://reservoprix.storage.googleapis.com https://spocont.com https://hiranytu.hu https://aktualis.info https://hungarian.news https://booboooking.com https://ekkor.hu https://karfelmero.hu https://reservoprix.lm.r.appspot.com; img-src 'self' data: https://reservoprix.storage.googleapis.com https://storage.googleapis.com https://lh3.googleusercontent.com https://maps.googleapis.com https://maps.g
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.otthonesuzlet.hu Verified 200
http (plaintext) http://mcp.otthonesuzlet.hu HTTPS enforced 301 https://mcp.otthonesuzlet.hu/
MCP tools · 7 exposed · ~1,251 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
ingatlan_discard_draft ~44

Discard one of the seller's drafts, for good. Ask the seller first. Needs the seller's sign-in.

NameTypeReqDescription
draft_idstringyes–

No output schema declared.

No examples provided.

ingatlan_draft_fields ~102

What a listing draft asks — the kinds and building types, the general fields and every property fact with its type, options, bounds and when it applies. Call it before asking the seller; narrow it with kind, building and deal. Needs the seller's sign-in.

NameTypeReqDescription
buildingstring––
dealstring–"sale", "rent" or "both": a rent asks its own terms.
kindstring––

No output schema declared.

No examples provided.

ingatlan_get_listing ~91

One listing's public page: facts, asking prices and deadline, the neighbourhood (nearest stop, school, shop…), the floor plan by level, photo links, and how to make an offer (on the page, after a Google sign-in). An ended listing says so.

NameTypeReqDescription
codestringyesThe listing's code, or its https://otthonesuzlet.hu/<code> link.

No output schema declared.

No examples provided.

ingatlan_how_to_post ~42

Where and how a seller posts a listing (a link they open and sign in to), and the kinds, building types and nearby filters there are.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ingatlan_list_drafts ~41

The seller's drafts: id, title, last saved, and the activate_url the seller opens to post it. Needs the seller's sign-in.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ingatlan_save_draft ~243

Save the seller's listing as a DRAFT — never live: the seller opens its activate_url, adds the photos and the map pin, accepts the terms and posts it. Checked by the posting form's rules; if something is missing or wrong, nothing is saved and the message says what to ask. At most 3 drafts; give draft_id to update one. Prices are whole amounts: a sale in millions with at most one decimal (42900000), a rent a month in whole thousands. Needs the seller's sign-in.

NameTypeReqDescription
addressstring––
buildingstring–Required for a home.
currencystring––
deadlinestring–Last day for offers, YYYY-MM-DD.
descriptionstring––
draft_idstring–Update this draft instead of making a new one.
factsobject–By key, as ingatlan_draft_fields lists them.
kindstringyes–
latnumber––
lngnumber––
rentobject––
saleobject––
titlestringyes–

No output schema declared.

No examples provided.

ingatlan_search_listings ~688

Search the live listings of otthon & üzlet (otthonesuzlet.hu), Hungarian homes and shops for sale or rent with sealed offers. Returns a page of listings (code, url, title, address, asking prices, deadline, a short summary) and the same search's catalogue_url. A search needs three conditions: a place (in text), a kind of property (filters.building, kind "shop", or typed) and one more condition. Until it has them the answer is a guide, not listings: { valid: false, missing, how, choices } — choices are the filter values there are for the place typed, with counts. Ask the user the questions in ask_user (never guess a missing condition), then search again.

NameTypeReqDescription
buildingstring–A home's building type (one; for several use filters.building).
dealstring–For sale or for rent. With "rent" the price range is the monthly rent.
filtersobject–The site's chips, each a list of values: building (the kind of property: house, semi-detached, small-condo, large-condo, housing-estate, shop), rooms, newness, condition, heating, extras.
kindstring–"home" or "shop".
max_priceinteger–Highest asking price, a whole amount in HUF.
min_priceinteger–Lowest asking price, a whole amount in HUF (e.g. 40000000; a rent e.g. 150000).
nearobject–Things within a distance, e.g. { "transit-stop": 400, "school": 800 }. Distances: 200, 400, 800, 1500, 3000, 5000, 10000 m. nightclub (300 m), railway (300 m), major-road (300 m), cemetery (300 m), i…
pageinteger––
page_sizeinteger–At most 20; 10 by default.
sortstring–Closing soonest first by default (relevance, the site's "Legjobb egyezés", keeps that order here).
textstringyesRequired: a place, up to 5 — any of them: a settlement ("Győr"), a city part of one settlement only ("Kelenföld", "Zugló"), or "Settlement-Part" with a hyphen for a part several settlements have ("Gy…

No output schema declared.

No examples provided.

Install

How do I install the otthon & üzlet MCP server?

otthon & üzlet is a hosted endpoint at https://mcp.otthonesuzlet.hu/, 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.otthonesuzlet.hu

# add to Claude Code
claude mcp add --transport http com-spocont-otthonesuzlet 'https://mcp.otthonesuzlet.hu/'
Common questions

What is the otthon & üzlet MCP server?

otthon & üzlet is an MCP server listed in the public MCP registry as com.spocont/otthonesuzlet. Hungarian home and shop listings with sealed-offer auctions: search, details, seller drafts. This page covers its hosted endpoint (https://mcp.otthonesuzlet.hu).

Is the otthon & üzlet MCP server safe to use?

otthon & üzlet scores 65 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 otthon & üzlet MCP server expose?

otthon & üzlet exposes 7 tools: ingatlan_search_listings, ingatlan_get_listing, ingatlan_how_to_post, ingatlan_draft_fields, ingatlan_save_draft, and 2 more. Their descriptions and schemas cost roughly 1,251 tokens of context every time the server is loaded.

Does the otthon & üzlet MCP server require authentication?

No. We connected to otthon & üzlet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the otthon & üzlet MCP server still maintained?

otthon & üzlet 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.