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.

Cenogram - Polish Real Estate Prices & Parcel Data

NPM · @CENOGRAM/MCP-SERVER · 2 COMPONENTS · SCANNED SEP 27

Polish real estate for AI: 8M+ deed transaction prices (RCN) + per-parcel context by cadastral ID

0 this week 44 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects undici 5.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 117 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to cenogram/mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the Cenogram - Polish Real Estate Prices & Parcel Data MCP server?

Cenogram - Polish Real Estate Prices & Parcel Data runs locally as an npm package, launched with npx -y @cenogram/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @cenogram/mcp-server

# add to Claude Code
claude mcp add pl-cenogram-mcp-server -- npx -y @cenogram/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "pl-cenogram-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cenogram/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pl-cenogram-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cenogram/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add pl-cenogram-mcp-server -- npx -y @cenogram/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pl-cenogram-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cenogram/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add pl-cenogram-mcp-server --command npx --arg -y --arg @cenogram/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  pl-cenogram-mcp-server:
    command: "npx"
    args: ["-y", "@cenogram/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pl-cenogram-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@cenogram/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add pl-cenogram-mcp-server -t stdio -c npx -a -y @cenogram/mcp-server
// mcp.json
{
  "mcpServers": {
    "pl-cenogram-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cenogram/mcp-server"
      ]
    }
  }
}
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.

  • 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
  • 19 Sept 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 18 Sept 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 14 Sept 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 13 Sept 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 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
  • 11 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
  • 8 Aug 26 0
    • Security disclosure: fail → pass ▲ functional
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 27 Sept 2026 · Analysed npm/@cenogram/mcp-server@0.6.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo cenogram/mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/cenogram/mcp-server/.github/workflows/publish.yml@refs/tags/v0.6.0
Rekor log index 2323996085
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:9b54199e98594311026225da9313bcd33fad3275f1ae9e44dee08289d34fc8275603aa64a5c80a65f4b3b3a7bd831f5951cc9c705dd2d12ff172840d4

Background: How many MCP packages publish verified provenance →

Vulnerabilities 12 findings
ID CVE Severity Vector Fix available
GHSA-2mjp-6q6p-2qxm CVE-2026-1525 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-35p6-xmwp-9g52 CVE-2026-6733 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-4992-7rv2-5pvq CVE-2026-1527 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N yes
GHSA-8xcm-r25x-g524 CVE-2026-16728 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-g8m3-5g58-fq7m CVE-2026-11525 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-g9mf-h72j-4rw9 CVE-2026-22036 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-m8rv-5g2x-5cg5 CVE-2026-15157 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-p88m-4jfj-68fv CVE-2026-9679 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-v3r7-h72x-cjcm CVE-2026-16729 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-v9p9-hfj2-hcw8 CVE-2026-2229 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vrm6-8vpv-qv8q CVE-2026-1526 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vxpw-j846-p89q CVE-2026-12151 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 117 packages
Packages resolved 117
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the Cenogram - Polish Real Estate Prices & Parcel Data MCP server?

Cenogram - Polish Real Estate Prices & Parcel Data is an MCP server listed in the public MCP registry as pl.cenogram/mcp-server. Polish real estate for AI: 8M+ deed transaction prices (RCN) + per-parcel context by cadastral ID. This page covers its npm package (@cenogram/mcp-server).

Is the Cenogram - Polish Real Estate Prices & Parcel Data MCP server safe to use?

Cenogram - Polish Real Estate Prices & Parcel Data scores 44 out of 100 on VerifyMCP. We recorded 12 known advisories against it as of 27 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.

Is the Cenogram - Polish Real Estate Prices & Parcel Data MCP server still maintained?

Cenogram - Polish Real Estate Prices & Parcel Data is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Cenogram - Polish Real Estate Prices & Parcel Data MCP server under?

Cenogram - Polish Real Estate Prices & Parcel Data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.