# Unlisted Property Search (remote · api.unlistedinc.com)

Search and explore residential properties that aren't for sale (yet)

- Trust score: 62/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.unlistedinc.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/com-unlistedinc-unlisted/api.md), [page](https://verifymcp.io/servers/com-unlistedinc-unlisted/api)

## Channel facts

- Endpoint: `https://api.unlistedinc.com/mcp`
- Transports: `streamable-http, sse`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 34/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1669 tokens (~333/item across 5 items; 3 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 6/100
  - Stability check failed: schema churn in the 8 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http com-unlistedinc-unlisted https://api.unlistedinc.com/mcp
```

### Codex

```toml
[mcp_servers.com-unlistedinc-unlisted]
url = "https://api.unlistedinc.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-unlistedinc-unlisted": {
      "type": "remote",
      "url": "https://api.unlistedinc.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-unlistedinc-unlisted --url https://api.unlistedinc.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-unlistedinc-unlisted:
    url: "https://api.unlistedinc.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-unlistedinc-unlisted": {
      "type": "http",
      "url": "https://api.unlistedinc.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 2.

### 2026-08-01 (score 61, −3)

- [security regression] Stability: 0.17 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [functional regression] “property_details_tool” made “id” required, so existing callers break

### 2026-07-31 (score 64, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (3)

### `property_details_tool` (~68 tokens)

Property Details

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.

Input parameters:

- `id` (string, required): Property ID

Output parameters:

- `address_line_1` (string): Street address
- `agent_cover_photo_uuid`: Agent-selected cover photo UUID — preferred over cover_photo_uuid when present
- `bathrooms` (number): Number of bathrooms
- `bedrooms` (number): Number of bedrooms
- `build_year` (number): Build year
- `building_area` (number): Building area (ft²)
- `city` (string): City name
- `cover_photo_uuid`: Curated cover photo UUID — preferred over photo_uuids[0] for display
- `estimated_value_one` (number): Estimated value
- `google_street_pose`
- `id` (number): Property identifier
- `last_sale_amount` (number): Last sale price
- `last_sale_date` (string): Last sale date
- `latitude` (number): Location latitude
- `likes_count` (number): Number of likes
- `longitude` (number): Location longitude
- `market_value` (number): Market value
- `owner_blurb` (string): Owner description
- `owner_expected_value` (number): Owner estimated value
- `owner_given_area` (number): Owner given building area (ft²)
- `owner_given_bathrooms` (number): Owner given number of bathrooms
- `owner_given_bedrooms` (number): Owner given number of bedrooms
- `owner_headline` (string): Owner headline
- `photo_uuids` (array): Photo UUIDs — use with CloudFront to build sized URLs (-thumbnail, -medium, -large)
- `state` (string): State abbreviation
- `stories` (number): Number of stories/floors
- `thumbnail_url` (string): Thumbnail image URL
- `unlisted_selling_soon_score` (number): Selling-soon score
- `unlisted_sorting_score` (number): Sorting score
- `url` (string): URL to view this property on Unlisted
- `views_count` (number): Number of views
- `waitlisters_count` (number): Number of waitlisters
- `zip` (string): ZIP code

### `property_search_tool` (~926 tokens)

Property Search

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.

Input parameters:

- `area_max`: Maximum building area (ft²)
- `area_min`: Minimum building area (ft²)
- `baths`: Minimum number of bathrooms
- `beds`: Minimum number of bedrooms
- `boundary_id`: Filter results to properties within a named geographic area (city, county, neighborhood, school district, etc.). Obtained from the autocomplete_tool.
- `build_max`: Maximum build year
- `build_min`: Minimum build year
- `geometry`: 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…
- `include_null_last_sale`: Include properties with no recorded sale date?
- `lot_area_max`: Maximum lot area (acres)
- `lot_area_min`: Minimum lot area (acres)
- `max_last_sale_date`: Maximum last sale date
- `max_results`: 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 n…
- `min_last_sale_date`: Minimum last sale date
- `perks`: Features and perks
- `price_max`: Maximum price ($)
- `price_min`: Minimum price ($)
- `property_use_standardized`: 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 inclu…
- `sort_type`: 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); owne…
- `stories`: Number of stories/floors
- `style`: Architectural style(s) to filter by

Output parameters:

- `alternative_search`
- `max_results`: Cap applied to results, if the user asked for a specific count
- `properties` (array)
- `search_url` (string): URL to view these results on Unlisted Discover
- `total_count` (number): Total number of properties matching the search

### `autocomplete_tool` (~159 tokens)

Search Autocomplete

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.

Input parameters:

- `query` (string, required): Place name, city, neighborhood, county, state, or street address to search for

Output parameters:

- `boundaries` (array): Matching geographic areas (cities, neighborhoods, counties, school districts, etc.). Use the id as boundary_id in PropertySearch.
- `properties` (array): Matching properties by address. Preferred primary method for finding exact addresses.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-unlistedinc-unlisted/api#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 62
- 2026-08-01: 61
- 2026-07-31: 64
- 2026-07-30: 60
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://api.unlistedinc.com/mcp
- Website: https://unlistedhomes.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-unlistedinc-unlisted/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-unlistedinc-unlisted/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-unlistedinc-unlisted/api