Skip to main content
Glama
chrischall

onehome-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to onehome-mcp

No user-submitted related servers found.

    Related Servers

    • compass-mcp

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Compass real-estate access as an MCP server for Claude — search listings, fetch property details, photo galleries, price history, and run affordability/mortgage math, all via natural language.
      18
      328 npm
      MIT

    • armls-spark-mcp-server

      mowaffak-alameen
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to query ARMLS Spark/FlexMLS real estate data including active listings, comparable sales, market statistics, and open houses via MCP tools.
      -

    • Zillow MCP Server

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

    • homes-mcp

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Provides real estate data from homes.com via a browser session, enabling property search, details, history, and affordability calculations through natural language.
      21
      120 npm
      MIT

    • redfin-mcp

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Enables natural language access to Redfin real estate data, including property search, details, photos, market reports, price history, climate risk, and saved homes/searches, by routing requests through your own signed-in browser session.
      22
      581 npm
      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

    A3.9/5.0

    Scored across 21 tools

    Disambiguation3/5

    Several tool clusters overlap: onehome_search_suggestions, onehome_get_by_address, and onehome_resolve_addresses all perform address/MLS lookup, while onehome_get_property, onehome_bulk_get, and onehome_compare_properties all fetch listing records, and onehome_get_saved_search duplicates onehome_get_saved_search_with_listings. The very detailed descriptions and cross-references (single vs bulk vs compare, cross-feed vs scoped) help, but boundaries are not crisp enough for instant selection.

    Naming Consistency4/5

    Nearly every tool follows a predictable onehome_verb_noun snake_case pattern (onehome_search_properties, onehome_get_property, onehome_set_active_session). Minor deviations exist where the verb trails (onehome_bulk_get) or is absent (onehome_graphql, onehome_healthcheck), but overall the convention is consistent and readable.

    Tool Count3/5

    At 21 tools the set is on the heavy side, with several tools that exist mainly as convenience combos or aliases of others (get_saved_search_with_listings, bulk_get, resolve_addresses vs get_by_address). Each is justifiable for the broad domain (search, fetch, sessions, location data, calculators), but the surface feels somewhat over-expanded for a consumer-share viewer.

    Completeness4/5

    Coverage is strong across the property-surfacing domain: search, single/bulk/compare fetches, photos, schools, walk score, mortgage/affordability math, session/auth management, a healthcheck, and a raw GraphQL escape hatch. The main gap is write-side interaction (liking/disliking or saving listings, saving searches), which is only partially alluded to via include_dislikes.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources