Skip to main content
Glama
Sign In
RE Data Refinery MCP Server

RE Data Refinery MCP Server

by areshms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to RE Data Refinery MCP Server

No user-submitted related servers found.

    Related Servers

    • Homesage.ai MCP

      ZR2021DC
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to access real estate data on 160M+ US properties, including valuations, comparable sales, rent estimates, rehab costs, owner records, and area searches.
      MIT

    • MCP Real Estate Intelligence

      Abhishekpendyala06
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive real estate market intelligence, property valuation, and investment analysis for AI agents. Unifies data from multiple sources like Zillow, Redfin, and public records into a single MCP interface.
      MIT

    • proptoit

      PhillipG96
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query and analyze self-hosted real-estate public-records data through 20 read-only MCP tools, including property search, foreclosure and distress signals, comps, market context, and optional license-gated deal scoring.
      MIT

    • Bounty-api

      vncent786
      F
      license
      A
      quality
      C
      maintenance
      Verified Singapore property, tax, affordability, salary, and location data for AI agents. 17 MCP tools, x402 micropayments, source provenance on every response. Singapore live now, more markets coming. Categories: Finance, Real Estate, Data, Singapore, x402, Payments, Government Data
      17
      -
    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

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct concerns: status/health, payment, property search/list, and specific property data lookups. The only mild overlap is between refinery_search_properties and refinery_list_properties, but their different input modes and purposes make them reasonably distinguishable.

    Naming Consistency4/5

    All tools share the refinery_ prefix and use snake_case, which creates a clear family identity. However, the status-style tools use bare nouns (health, cache_stats, credits, payment_status) while data tools use verb_noun forms, so the pattern is not perfectly uniform.

    Tool Count5/5

    Ten tools is well-scoped for a property data refinery server: a few operational/status endpoints, general search/list capabilities, and individual data detail lookups. Each tool has a clear role without the surface feeling bloated or thin.

    Completeness5/5

    The tool set covers the full read-side property workflow: discover properties by search or listing, retrieve full details, and access price history, tax history, and schools. It also includes operational endpoints for health, cache stats, credits, and payment configuration, so there are no obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Resources