unlisted
Registry code: 47a29a00db7fe188
Unlisted is a central source of information for all residential properties in the USA -- every property not just those that are for sale and listed on the MLS etc.
Use these tools together to search for and retrieve property information:
- endpoint
- https://api.unlistedinc.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is unlisted live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is unlisted free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does unlisted have?
- 3 tools: autocomplete_tool, property_details_tool, property_search_tool.
- Is unlisted safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.1%· all time 99.1%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search us residential properties by criteria
- resolve an address to a property id
- get details for a property
- takes → gives
- text, data → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
property_search_tool reads open 4h ago
Search for properties on Unlisted that meet certain criteria. boundary_id should always be used unless doing a nation-wide search, and is obtained by using the autocomplete_tool. Returns up to 100 matches; use max_results only when the user asks for a specific count. When telling the user what you're doing, say "area" not "boundary", and "home" or "property profile" not "listing". Don't mention internal IDs or parameter names.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "beds": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 1 } ], "description": "Minimum number of bedrooms" }, "baths": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 1 } ], "description": "Minimum number of bathrooms" }, "perks": { "anyOf": [ { "type": "null" }, { "type": "array", "items": { "enum": [ "accessible", "arbor_pergola", "arena", "attic", "balcony", "barn", "bath_house", "boat_access", "boat_house", "boat_lift", "bonus_room", "breakfast_nook", "breezeway", "cabin", "canopy", "cellar", "central_vacuum", "community_rec_room", "courtyard", "deck", "elevator", "escalator", "exercise_room", "family_room", "finished_basement", "fire_sprinklers", "fireplace", "first_floor_bedroom", "first_floor_laundry", "game_room", "garage", "gazebo", "golf_course_green", "granary", "great_room", "green_house", "guest_house", "hobby_room", "intercom", "kennel", "laundry_room", "lean_to", "loading_platform", "media_room", "milk_house", "mobile_home_hookup", "mud_room", "office", "outdoor_kitchen", "overhead_door", "patio", "pergola", "pole_structure", "pond", "pool", "pool_house", "porch", "poultry_house", "practice_green", "quonset", "rooftop_garden", "rv_parking", "safe_room", "sauna", "security_alarm", "shed", "silo", "sitting_room", "sound_system", "sports_court", "sprinklers", "stable", "storage_building", "storm_shelter", "storm_shutter", "study", "study_room", "sunroom", "tax_ex_disabled", "tax_ex_senior", "tax_ex_veteran", "tax_ex_widow", "tennis_court", "universal_access", "utility_building", "utility_room", "water_feature", "wet_bar", "wine_cellar" ], "type": "string" } } ], "description": "Features and perks" }, "style": { "anyOf": [ { "type": "null" }, { "type": "array", "items": { "enum": [ "art_deco", "bungalow", "cape_cod", "colonial", "contemporary", "craftsman", "creole", "dutch_colonial", "federal", "french_provincial", "georgian", "gothic_revival", "greek_revival", "international", "italianate", "monterey", "national", "neoclassical", "mcm_prairie", "pueblo", "queen_anne", "ranch", "regency", "saltbox", "second_empire", "shed", "shingle", "shotgun", "spanish_eclectic", "split_level", "stick", "tudor", "victorian", "other" ], "type": "string" } } ], "description": "Architectural style(s) to filter by" }, "stories": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 1 } ], "description": "Number of stories/floors" }, "area_max": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 0 } ], "description": "Maximum building area (ft²)" }, "area_min": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 0 } ], "description": "Minimum building area (ft²)" }, "geometry": { "anyOf": [ { "type": "null" }, { "type": "object", "required": [ "type", "coordinates" ], "properties": { "type": { "enum": [ "Polygon" ], "type": "string" }, "coordinates": { "type": "array", "items": { "type": "array", "items": { "type": "array", "items": { "type": "number" }, "maxItems": 2, "minItems": 2, "description": "[longitude, latitude]" }, "minItems": 4 }, "description": "Array of linear rings; first ring is the outer boundary" } } } ], "description": "GeoJSON Polygon to spatially filter properties. This is handy for when a boundary id is not found, or for other special cases where the user describes an area that is not well-known, or does not have a proper name.Coordinates are [longitude, latitude] pairs; first and last point must match to close the ring. Can be combined with boundary_id — results must satisfy both constraints. Example: {\"type\":\"Polygon\",\"coordinates\":[[[-87.635560,41.885830],[-87.628755,41.885842],[-87.628685,41.879399],[-87.635509,41.879389],[-87.635560,41.885830]]]}" }, "build_max": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 0 } ], "description": "Maximum build year" }, "build_min": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 0 } ], "description": "Minimum build year" }, "price_max": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 0 } ], "description": "Maximum price ($)" }, "price_min": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 0 } ], "description": "Minimum price ($)" }, "sort_type": { "anyOf": [ { "type": "null" }, { "enum": [ "default", "owner_updated_at", "selling_soon_score", "likes", "last_sale_date" ], "type": "string" } ], "description": "Sort order for results. Use default unless the user specifies otherwise. default: ranked by Unlisted's overall relevance/quality score, heavily weighted by selling_soon_score (best match first); owner_updated_at: properties most recently updated by their owner first (active/engaged sellers); selling_soon_score: properties with the highest likelihood of going to market soon, first; likes: most-liked properties first; last_sale_date: most recently sold properties first (properties with no sale date are excluded)." }, "boundary_id": { "anyOf": [ { "type": "null" }, { "type": "number" } ], "description": "Filter results to properties within a named geographic area (city, county, neighborhood, school district, etc.). Obtained from the autocomplete_tool." }, "max_results": { "anyOf": [ { "type": "null" }, { "type": "integer", "maximum": 100, "minimum": 1 } ], "description": "Cap the total number of results shown to the user. Only use when the user explicitly asks for a specific count, e.g. 'show me the top 5' or 'give me 20 homes'. Must be 100 or fewer. Leave blank for normal searches." }, "lot_area_max": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 0 } ], "description": "Maximum lot area (acres)" }, "lot_area_min": { "anyOf": [ { "type": "null" }, { "type": "number", "minimum": 0 } ], "description": "Minimum lot area (acres)" }, "max_last_sale_date": { "anyOf": [ { "type": "null" }, { "type": "string", "format": "date" } ], "description": "Maximum last sale date" }, "min_last_sale_date": { "anyOf": [ { "type": "null" }, { "type": "string", "format": "date" } ], "description": "Minimum last sale date" }, "include_null_last_sale": { "anyOf": [ { "type": "null" }, { "type": "boolean" } ], "description": "Include properties with no recorded sale date?" }, "property_use_standardized": { "anyOf": [ { "type": "null" }, { "type": "array", "items": { "anyOf": [ { "enum": [ "single_family", "condos_and_townhouses", "coops", "manufactured", "misc", "multi_24", "multi_5", "other", "vacant_land" ], "type": "string" }, { "type": "integer" } ] } } ], "description": "Filter by property use type. Each item can be a category name (selects all codes in the group) or an individual ATTOM numeric code to cherry-pick. If omitted, all standard residential types are included. Categories and their codes — single_family [181,363,364,380,383,385,440,467,468]: SFR, cluster homes, rural residences, homesteads, ADU; condos_and_townhouses [366,376,377,379,382,386,390,416,421,452]: condos, PUDs, patio homes, row houses, townhouses, garden homes, zero lot line; coops [367,461]: cooperatives; manufactured [371,373]: mobile/manufactured/modular homes; multi_24 [369,372,378,388,469,470]: 2-4 unit multifamily (duplexes, triplexes, quads, generic multifamily); multi_5 [360,374,381]: apartments and large multifamily/income properties; misc [375,384]: seasonal/cabin/vacation + miscellaneous residential; vacant_land [398,401,453,462]: residential vacant land and uninhabitable/destroyed structures; other [171,254,306,368,370,387,402,447]: mixed-use, historical, dormitories, fraternity/sorority houses, timeshares, under construction, tiny houses, unknown." } } }arguments 442 linesautocomplete_tool reads unknown 4h ago
Autocomplete a search term to find geographic areas (cities, counties, neighborhoods, school districts, states, etc.) and properties by address. Use this to look up boundary IDs for the boundary_id parameter in PropertySearch, OR Use this to look up property IDs for the id parameter in property details tool. If a search does not yield the expected results attempt to simplify and/or shorten the query, removing potentially problematic or unneeded words/symbols. When telling the user what you're doing, say "area" not "boundary", and "home" or "property profile" not "listing". Don't mention internal IDs or parameter names.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Place name, city, neighborhood, county, state, or street address to search for" } } }arguments 13 linesproperty_details_tool reads unknown 4h ago
Fetch full details for a single Unlisted property by its ID. When telling the user what you're doing, say "area" not "boundary", and "home" or "property profile" not "listing". Don't mention internal IDs or parameter names.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Property ID" } } }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id47a29a00db7fe188.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/47a29a00db7fe188/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/47a29a00db7fe188?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.