Skip to main content
Glama
srnux

proptech-inquiry

by srnux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to proptech-inquiry

No user-submitted related servers found.

    Related Servers

    • one-roof

      vedzilla
      A
      license
      A
      quality
      B
      maintenance
      Unified UK property search across major portals with deduplication and open-data enrichment, enabling natural-language queries for listings, sold prices, EPC, crime, schools, and market stats.
      10
      MIT

    • Scout MCP

      Flikah
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to look up real estate agents, search MLS listings, submit buyer/seller leads, and access proprietary seller-intent signals in SC and GA.
      MIT

    • Property MCP Server

      digitsouler
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to operate property management systems via natural language, covering repair orders, owner info, payments, notices, and inspections. Features a full agentic workflow with human-in-the-loop and observability.
      MIT

    • Realty In Ca1 MCP Server

      BACH-AI-Tools
      A
      license
      B
      quality
      D
      maintenance
      Enables users to access the Realty In Ca1 API to search for residential and commercial property listings, view detailed property information, and retrieve neighborhood demographics or statistics. It supports filtering by geographic location, price range, building type, and other real estate characteristics.
      MIT
    • Repliers MCP Server by Repliers-io

      Repliers MCP Serverofficial

      Repliers-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI assistants access to real-time MLS data via the Repliers API, enabling natural language property search, market statistics, and listing details.
      334 npm
      16
      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.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct action: search by criteria, retrieve one record, or escalate to a human. The descriptions explicitly define boundaries (search_listings says do not use it for a specific listing; get_listing says answer only from the record), so misselection is unlikely.

    Naming Consistency5/5

    All three names follow a clear verb_noun pattern (search_listings, get_listing, hand_off_to_human) with consistent snake_case.

    Tool Count4/5

    Three tools is lean for the narrow inquiry-handling scope, and each earns its place, though it sits near the lower bound where coverage could feel thin for edge cases.

    Completeness4/5

    The read-plus-escalate lifecycle is well covered: criteria search, full record retrieval, and human handoff for bookings, negotiation, legal, and unanswerable questions. Only listing management/creation is absent, which is outside an inquiry agent's stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources