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.

InfoGrunt

REMOTE · INFOGRUNT.PL

Check a land plot in Poland: zoning plan, flood risk, utilities, local land prices. No account.

Available components

+3 this week 75 Trust /100

Last scanned (23 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Maps and Location

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 Security80
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 648 tokens (~92/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% 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
  • 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 8 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 +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.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +2
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_parcel” rewrote its description, which is the text the model reads security
    • Tool “find_parcel_at_point” rewrote its description, which is the text the model reads security
    • Tool “get_market_pulse” rewrote its description, which is the text the model reads security
    • Tool “get_municipality_market” rewrote its description, which is the text the model reads security
    • Tool “get_parcel_overview” rewrote its description, which is the text the model reads security
    • Tool “get_parcel_section” rewrote its description, which is the text the model reads security
    • Tool “search_location” rewrote its description, which is the text the model reads security
    • Schema quality: 67 → 92 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: fair → good functional
    • Server version: 0.2.1 → 0.2.2 functional
    • Tool “find_parcel” changed its title: Znajdź działkę po ID → Znajdź działkę po numerze cosmetic
    • Tool “find_parcel_at_point” changed its title: Znajdź działkę w punkcie → Znajdź działkę w tym miejscu cosmetic
    • Tool “get_market_pulse” changed its title: Sprawdź puls rynku → Ceny działek w regionie cosmetic
    • Tool “get_municipality_market” changed its title: Sprawdź rynek gminy → Ceny działek w gminie cosmetic
    • Tool “get_parcel_section” changed its title: Pobierz sekcję raportu → Szczegóły jednego tematu działki cosmetic
    • Tool “search_location” changed its title: Wyszukaj lokalizację → Znajdź adres lub miejscowość cosmetic
  • 24 Oct 26 68

    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 4 Nov 2026 · Probed https://infogrunt.pl/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.infogrunt.pl CN=YE2,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA384 69a0d2dbaad47af5eba68419873d19eb7dd
SANs: *.infogrunt.pl, infogrunt.pl
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 insecure

Validation of infogrunt.pl. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
pl. present 2782 8 Verified
infogrunt.pl. 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
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(self), microphone=(), camera=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://infogrunt.pl/mcp Verified 200
http (plaintext) http://infogrunt.pl/mcp HTTPS enforced 301 https://infogrunt.pl/mcp
MCP tools · 7 exposed · ~476 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
find_parcel ~66

Znajdź działkę po pełnym numerze ewidencyjnym, np. 101710_2.0007.1504/6: gmina, obręb, położenie i link do strony działki.

NameTypeReqDescription
parcel_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

find_parcel_at_point ~60

Która działka leży w tym miejscu? Dla punktu na mapie Polski podaje numer działki, gminę i link do strony działki.

NameTypeReqDescription
latnumberyes–
lngnumberyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_market_pulse ~60

Jak zmieniają się ceny działek budowlanych w całej Polsce albo w jednym województwie: ostatni tydzień, miesiąc i rok, z linkiem do mapy cen.

NameTypeReqDescription
regionstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_municipality_market ~74

Ile kosztują działki w gminie? Mediana cen z prawdziwych transakcji, liczba sprzedaży, okres i pewność wyniku. Gminę wskazuje 6-cyfrowy kod z wyszukiwania adresu.

NameTypeReqDescription
terytstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_parcel_overview ~76

Sprawdź działkę: plan miejscowy, warunki zabudowy, powódź, media, dojazd, ochrona przyrody, osuwiska i ceny w okolicy. Pokazuje, co wiadomo o działce, i link do pełnego raportu.

NameTypeReqDescription
parcel_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_parcel_section ~76

Szczegóły jednego tematu dla działki, np. plan miejscowy, powódź, media, dojazd albo ceny transakcji w okolicy. Ze źródłem, datą i linkiem do strony działki.

NameTypeReqDescription
parcel_idstringyes–
sectionstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

search_location ~64

Znajdź adres, ulicę albo miejscowość w Polsce, np. Polna 5, Wieliczka. Pokazuje miejsce na mapie działek, gminę i link do mapy na InfoGrunt.pl.

NameTypeReqDescription
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the InfoGrunt MCP server?

InfoGrunt is a hosted endpoint at https://infogrunt.pl/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 · infogrunt.pl

# add to Claude Code
claude mcp add --transport http pl-infogrunt-dzialki 'https://infogrunt.pl/mcp'
Common questions

What is the InfoGrunt MCP server?

InfoGrunt is an MCP server listed in the public MCP registry as pl.infogrunt/dzialki. Check a land plot in Poland: zoning plan, flood risk, utilities, local land prices. No account. This page covers its hosted endpoint (https://infogrunt.pl/mcp).

Is the InfoGrunt MCP server safe to use?

InfoGrunt scores 75 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 InfoGrunt MCP server expose?

InfoGrunt exposes 7 tools: search_location, find_parcel, find_parcel_at_point, get_parcel_overview, get_parcel_section, and 2 more. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.

Does the InfoGrunt MCP server require authentication?

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

Is the InfoGrunt MCP server still maintained?

InfoGrunt is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.