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.

GROO reality

REMOTE · WWW.GROO.CZ

Nabídka nemovitostí GROO reality — byty, domy a pozemky v Praze a okolí. Jen pro čtení, bez klíče.

Available components

0 this week 80 Trust /100

Last scanned (18 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 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 Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1056 tokens (~88/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 24 Aug 26 0

    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 21 Nov 2026 · Probed https://www.groo.cz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.groo.cz CN=YE2,O=Let's Encrypt,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA384 5fcc57c78b3441bff0cc1907d6fb5b74ff8
SANs: www.groo.cz
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC bogus

Validation of www.groo.cz. — Bogus

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cz. DS published 20237 13 Verified
groo.cz. DS published 10303 14 Verified
www.groo.cz. Bogus address RRset signature failed verification
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 frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=(), usb=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.groo.cz/mcp Verified 200
http (plaintext) http://www.groo.cz/mcp HTTPS enforced 308 https://www.groo.cz/mcp
MCP tools · 12 exposed · ~913 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
aktuality ~50

Články z webu — dění v kanceláři a na realitním trhu.

NameTypeReqDescription
limitnumber–Kolik nejnovějších vrátit (výchozí 5).

No output schema declared.

No examples provided.

ciselniky ~40

Povolené hodnoty filtru: typy, kategorie i s dispozicemi a obce, ve kterých nabídky opravdu jsou.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

detail_aktuality ~41

Celý text jednoho článku, ne jen perex.

NameTypeReqDescription
idstringyesČíslo článku ze seznamu aktuality.

No output schema declared.

No examples provided.

detail_nabidky ~62

Vrátí podrobnosti jedné nabídky: popis, parametry, adresu, fotky a kontakt na makléřku.

NameTypeReqDescription
idstringyesČíslo nabídky, např. "groo1516".

No output schema declared.

No examples provided.

detail_projektu ~45

Developerský projekt i se seznamem jednotek, které se v něm prodávají.

NameTypeReqDescription
idstringyesČíslo projektu ze seznamu projekty.

No output schema declared.

No examples provided.

hledej_nemovitosti ~382

Vyhledá nemovitosti v aktuální nabídce GROO reality. Všechny filtry jsou nepovinné a dají se kombinovat. Vrací i celkový počet nálezů.

NameTypeReqDescription
cena_donumber–Horní hranice ceny v Kč. Dvě věci, které je potřeba vědět: porovnává se s cenou bez ohledu na prodej či pronájem (u „do 7 000 000" projdou i všechny pronájmy — kombinuj s parametrem typ), a projdou t…
dispozicestring–Štítky oddělené čárkou, např. "2+kk,3+1" nebo "kanceláře".
dotazstring–Fulltext přes obec, ulici, popis i číslo nabídky. Hledá se od začátku slova a čeština se neskloňuje, takže zadávej KMEN, ne tvar z věty: „lodži" najde lodžie i lodžií, kdežto „lodžie" jen část z nich.
kategoriestring––
limitnumber–Kolik nabídek vrátit (výchozí 20, nejvíc 50).
obecstring–Obec ze seznamu v nástroji ciselniky.
typstring–Prodej či pronájem
vymera_odnumber–Dolní hranice výměry v m².

No output schema declared.

No examples provided.

kontakt ~20

Telefon, e-mail a adresa realitní kanceláře.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

poptavky ~70

Nemovitosti, které GROO reality aktivně poptává pro své klienty. Použij, když někdo prodává nebo se ptá, jestli má o jeho nemovitost někdo zájem — je to opačný směr než hledej_nemovitosti.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

projekty ~41

Projekty ze sekce Doporučujeme — novostavby a rekonstrukce, u kterých kancelář prodává více jednotek najednou.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reference ~39

Co o spolupráci napsali klienti. Hodí se, když se někdo ptá na zkušenosti nebo spolehlivost kanceláře.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

stranka ~79

Text jedné stránky webu v markdownu. Použij, když se někdo ptá na to, jak kancelář pracuje, co dělá při prodeji nebo co nabízí za služby.

NameTypeReqDescription
uristringyesAdresa stránky jako na webu, např. „sluzby/prodej" nebo „kontakt".

No output schema declared.

No examples provided.

stranky ~44

Seznam stránek webu — služby kanceláře, právní informace, o makléřce. Obsah konkrétní stránky vrátí nástroj stranka.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the GROO reality MCP server?

GROO reality is a hosted endpoint at https://www.groo.cz/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 · www.groo.cz

# add to Claude Code
claude mcp add --transport http cz-groo-reality 'https://www.groo.cz/mcp'
Common questions

What is the GROO reality MCP server?

GROO reality is an MCP server listed in the public MCP registry as cz.groo/reality. Nabídka nemovitostí GROO reality, byty, domy a pozemky v Praze a okolí. Jen pro čtení, bez klíče. This page covers its hosted endpoint (https://www.groo.cz/mcp).

Is the GROO reality MCP server safe to use?

GROO reality scores 80 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 GROO reality MCP server expose?

GROO reality exposes 12 tools: hledej_nemovitosti, detail_nabidky, ciselniky, poptavky, projekty, and 7 more. Their descriptions and schemas cost roughly 913 tokens of context every time the server is loaded.

Does the GROO reality MCP server require authentication?

No. We connected to GROO reality without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the GROO reality MCP server still maintained?

GROO reality is still listed as active in the MCP registry. We last reached this channel on 21 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 GROO reality MCP server?

VerifyMCP ran 12 checks on GROO reality, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about GROO reality: Authorization. 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.