# InfoGrunt (remote · infogrunt.pl)

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

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

## Components

- remote · `infogrunt.pl`: 75/100 (this document), [markdown](https://verifymcp.io/servers/pl-infogrunt-dzialki/infogrunt.md), [page](https://verifymcp.io/servers/pl-infogrunt-dzialki/infogrunt)

## Channel facts

- Endpoint: `https://infogrunt.pl/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.2`

## 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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 648 tokens (~92/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% 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.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http pl-infogrunt-dzialki 'https://infogrunt.pl/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "pl-infogrunt-dzialki": {
      "url": "https://infogrunt.pl/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pl-infogrunt-dzialki": {
      "type": "http",
      "url": "https://infogrunt.pl/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pl-infogrunt-dzialki]
url = "https://infogrunt.pl/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pl-infogrunt-dzialki": {
      "type": "remote",
      "url": "https://infogrunt.pl/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pl-infogrunt-dzialki --url 'https://infogrunt.pl/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pl-infogrunt-dzialki:
    url: "https://infogrunt.pl/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "pl-infogrunt-dzialki": {
      "Transport": "http",
      "Url": "https://infogrunt.pl/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pl-infogrunt-dzialki -t streamable-http -u 'https://infogrunt.pl/mcp'
```

### Other

```json
{
  "mcpServers": {
    "pl-infogrunt-dzialki": {
      "type": "http",
      "url": "https://infogrunt.pl/mcp"
    }
  }
}
```

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 75, +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-11-01 (score 74, +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.

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

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

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

### 2026-10-25 (score 70, +2)

- [security] 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
- [functional regression] Schema quality: 67 → 92
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: fair → good
- [functional] Server version: 0.2.1 → 0.2.2
- [cosmetic] 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ść

### 2026-10-24 (score 68)

First indexed and scored.

## MCP tools (7)

### `search_location` (~64 tokens)

Znajdź adres lub miejscowość

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.

Input parameters:

- `query` (string, required)

### `find_parcel` (~66 tokens)

Znajdź działkę po numerze

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.

Input parameters:

- `parcel_id` (string, required)

### `find_parcel_at_point` (~60 tokens)

Znajdź działkę w tym miejscu

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.

Input parameters:

- `lat` (number, required)
- `lng` (number, required)

### `get_parcel_overview` (~76 tokens)

Sprawdź działkę

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.

Input parameters:

- `parcel_id` (string, required)

### `get_parcel_section` (~76 tokens)

Szczegóły jednego tematu działki

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.

Input parameters:

- `parcel_id` (string, required)
- `section` (string, required)

### `get_municipality_market` (~74 tokens)

Ceny działek w gminie

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.

Input parameters:

- `teryt` (string, required)

### `get_market_pulse` (~60 tokens)

Ceny działek w regionie

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.

Input parameters:

- `region` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pl-infogrunt-dzialki/infogrunt#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70
- 2026-10-24: 68

## 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 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://infogrunt.pl/mcp
- Website: https://infogrunt.pl/asystenci-ai
- Changelog RSS feed: https://verifymcp.io/servers/pl-infogrunt-dzialki/infogrunt.xml
- Changelog JSON feed: https://verifymcp.io/servers/pl-infogrunt-dzialki/infogrunt.json
- HTML version of this page: https://verifymcp.io/servers/pl-infogrunt-dzialki/infogrunt