Skip to main content
Glama
cenogram

cenogram-mcp-server

Official
by cenogram
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to cenogram-mcp-server

No user-submitted related servers found.

    Related Servers

    • rcs-mcp

      lakafior
      A
      license
      A
      quality
      C
      maintenance
      Enables searching Polish administrative areas and retrieving real estate transaction data from the official registry via geoportal.gov.pl.
      3
      GPL 3.0
    • Normi — French Real Estate Data (DVF) by NormiHQ

      Normi — French Real Estateofficial

      NormiHQ
      A
      license
      Not graded
      quality
      C
      maintenance
      Access 17M+ geocoded French property transactions (DVF), 22M+ DPE energy ratings, and 20M+ building records via MCP or REST API. Search transactions, market stats, comparables, price trends, rental yield, flip detection, and more.
      MIT

    • Rejestr.io MCP Server

      KolegaLiterat
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Poland's largest business registry database, enabling company search, beneficiary checks, and financial document retrieval via natural language.
      1
      -

    • atlas-przetargow-mcp-py

      dam2452
      F
      license
      A
      quality
      C
      maintenance
      Enables searching and analyzing Polish public procurement tenders from BZP and TED, including filtering, tender details and timelines, offers and contract values, buyer/contractor profiles, CPV code lookup, and regional statistics, with optional AI-summary endpoints.
      12
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 23 tools

    Disambiguation4/5

    Tools are mostly well-distinguished by their target resource and action: parcel search vs. transaction search vs. statistics vs. per-transaction enrichment layers are all clear. A few pairs (search_by_area vs. search_by_polygon, and search_parcels vs. resolve_parcel) have overlapping boundaries, but the descriptions explain when to use each.

    Naming Consistency4/5

    The set follows a consistent verb-first convention: search_* for discovery, get_* for retrieval, and a few standalone verbs like resolve/compare/estimate. Minor deviations such as search_by_area/search_by_polygon versus search_parcels/search_transactions, and get_building_breakdown instead of get_transaction_buildings, are slight but not confusing.

    Tool Count3/5

    23 tools is a large surface, and the calibration guidance marks 16-25 tools as heavy. The count is justified by the number of enrichment layers for transactions, but the set sits in the upper range where it becomes harder for an agent to weigh all options efficiently.

    Completeness5/5

    The surface is very complete for a real-estate data server: parcel discovery/resolution/full reports, transaction search by name/radius/polygon, price statistics and distribution, market overview, comparison, valuation, demographics, infrastructure signals, and eight per-transaction breakdowns. There are no obvious dead ends: search result IDs feed the detail tools, and parcel IDs feed both transaction and parcel-report tools.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources