Skip to main content
Glama
chrischall

booli-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to booli-mcp

No user-submitted related servers found.

    Related Servers

    • Booli MCP Server

      matt1as
      F
      license
      B
      quality
      Not graded
      maintenance
      Enables AI assistants to search and analyze Swedish real estate data from Booli.se using natural language queries. Supports property searches with comprehensive filtering options and location discovery through GraphQL API integration.
      3
      1
      -

    • blocket-mcp

      Thunberg087
      F
      license
      A
      quality
      C
      maintenance
      Enables searching and retrieving listings from Sweden's Blocket marketplace, including cars, boats, motorcycles, and general items, without requiring an API key.
      6
      -

    • naver-land-mcp

      kimju1416
      A
      license
      A
      quality
      C
      maintenance
      Enables searching Korean apartment listings, market prices, and recent transactions via Naver Real Estate through natural language.
      6
      MIT

    • Zillow MCP Server

      sap156
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides real-time access to Zillow real estate data, enabling property search, details, Zestimates, market trends, and mortgage calculations via natural language.
      9 npm
      50
      MIT

    • Idealista7 MCP Server

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Enables access to Idealista API for searching and retrieving property listings across Spain, Portugal, and Italy. Supports various property types including homes, apartments, garages, commercial properties, offices, and land with detailed filtering options.
      14
      3
      MIT
    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.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct role: diagnostics (healthcheck), ID lookup (get_listing), area resolution (search_areas), active search (search_listings), sold search (search_sold), and aggregates (market_stats). The sold-search vs market-stats boundary could be adjacent, but descriptions explicitly clarify that one returns listings and the other returns aggregate statistics.

    Naming Consistency4/5

    All tools use a predictable booli_ prefix and snake_case. Most follow a verb_noun pattern (get_listing, search_areas, search_listings, search_sold), with minor deviations like healthcheck and market_stats that are still readable and idiomatic.

    Tool Count5/5

    Six tools is well-scoped for a read-only property data API: one diagnostic, one area resolver, two search endpoints, one detail endpoint, and one aggregate stats endpoint. Each earns its place without redundancy.

    Completeness4/5

    The surface covers the core read-only lifecycle: area lookup, active/sold search, listing detail, and market aggregates. Minor gaps exist (e.g., no bulk listing fetch or comparable-listing helper), but agents can work around them by composing existing tools.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources