Skip to main content
Glama
lambda-house

korter-mcp

by lambda-house

Related Servers

Alternatives to korter-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables searching and browsing ss.ge real estate listings with filters, counters, full card details, and geo/city data via MCP tools.
      6
      33 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables querying livo.ge real estate listings through MCP, including search, listing details, geo lookups, reference dictionaries, and new development projects.
      7
      10 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables comparison of residential candidate areas by land price, station walking time, and public transit commute, with PMTiles-powered interactive maps. Provides MCP tools for listing layers, retrieving land prices, computing commutes, finding and comparing areas, and building area maps.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Taiwan real-estate actual-price transaction data through MCP tools, including transaction search, market statistics, area listing, and data status, using a local SQLite database.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Irish classifieds, providing tools to search Daft.ie property listings and Adverts.ie marketplace ads, retrieve details, and optionally manage authenticated accounts. Supports both stdio and HTTP transports.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Provides South Korean real estate transaction price lookup (sales and rent) for apartments, row houses, single-family homes, and officetels via MCP tools using public data from data.go.kr.
      8
      17 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target distinct resources or actions: search_projects vs search_secondary cover different markets, get_project vs price_history differ in scope, and track/untrack/refresh have clear boundaries. Minor potential confusion between diff_report/price_history/secondary_trends (all change-oriented) and between refresh and the track/untrack sweep tools, but descriptions clarify.

    Naming Consistency3/5

    Names use consistent snake_case, but conventions are mixed: some are verb_noun (get_project, list_districts, search_projects), others are bare verbs/nouns (track, refresh, consent), and others are noun phrases (diff_report, price_history, my_data). Readable, but not a predictable single pattern.

    Tool Count4/5

    At 15 tools, the set is at the upper end of the ideal range but each tool maps to a concrete capability (search, track, refresh, history, secondary market, consent/privacy, skills). It is slightly heavy due to auxiliary tools (get_skill, consent, my_data, list_users) but not bloated or mismatched for the domain.

    Completeness4/5

    Core lifecycle for the domain is covered: source tracking (track/untrack/list_tracked), manual refresh, project search and detail, history/diff, secondary search and trends, plus consent and user data. Minor gaps exist, such as no explicit bulk source management or a per-source metadata view, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues