# Realty.Bingo (remote · realty.bingo)

Property search, comparison, investment analysis and watchlists with change alerts

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `realty.bingo`: 74/100 (this document), [markdown](https://verifymcp.io/servers/agentstructure-realty/realty.md), [page](https://verifymcp.io/servers/agentstructure-realty/realty)

## Channel facts

- Endpoint: `https://realty.bingo/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- 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-10-18.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2136 tokens (~178/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 29% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Realty.Bingo MCP server?

Realty.Bingo is a hosted endpoint at https://realty.bingo/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http agentstructure-realty 'https://realty.bingo/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "agentstructure-realty": {
      "url": "https://realty.bingo/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "agentstructure-realty": {
      "type": "http",
      "url": "https://realty.bingo/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.agentstructure-realty]
url = "https://realty.bingo/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agentstructure-realty": {
      "type": "remote",
      "url": "https://realty.bingo/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add agentstructure-realty --url 'https://realty.bingo/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  agentstructure-realty:
    url: "https://realty.bingo/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "agentstructure-realty": {
      "Transport": "http",
      "Url": "https://realty.bingo/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add agentstructure-realty -t streamable-http -u 'https://realty.bingo/mcp'
```

### Other

```json
{
  "mcpServers": {
    "agentstructure-realty": {
      "type": "http",
      "url": "https://realty.bingo/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-10-18 (score 74, +1)

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

### 2026-10-16 (score 73, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-15 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-14 (score 72)

First indexed and scored.

## MCP tools (12)

### `search_properties` (~616 tokens)

Search properties

Find active U.S. homes for sale or rent in a city+state, ZIP codes, a radius around a point, or a polygon. Hard requirements (max_price, min_bedrooms, min_bathrooms, property_types, must_have) filter; soft preferences (ideal_max_price, preferred_bedrooms, nice_to_have, styles) rank; avoid and exclude_property_types exclude. Each result has a 0-100 match score with reasons and uncertainties, the features the listing states (with evidence class), source details and when it was last confirmed active. Features a listing does not mention are UNKNOWN, never assumed. Reuses data fetched in the last 12 hours; otherwise makes a live request if the daily allowance permits. Source: Realtor.com (via RapidAPI) with RentCast as fallback; each result names its source. Never present results beyond what is returned.

Input parameters:

- `allow_live_request` (boolean): false = stored data only (no provider request).
- `avoid` (array): Features that exclude a listing when the listing states them, e.g. fixer-upper, pool.
- `bedrooms_exception` (object): e.g. 'three bedrooms, but two is fine with an office': min_bedrooms 3 plus {min_bedrooms: 2, requires: ['home office']}
- `exclude_property_types` (array)
- `ideal_max_price` (number): Soft target: listings above it rank lower but stay in.
- `include_non_matching` (boolean): true = also return listings that fail a hard requirement, with the reason.
- `investment` (object)
- `limit` (integer)
- `listing_type` (string, required)
- `location` (object, required)
- `max_distance` (object): Straight-line distance from a place the user names (e.g. work). Not driving time.
- `max_hoa_fee` (number)
- `max_price` (number): Hard ceiling: listings above it are excluded.
- `min_bathrooms` (number)
- `min_bedrooms` (integer)
- `min_living_area` (integer)
- `min_lot_area` (integer)
- `min_price` (number)
- `min_year_built` (integer)
- `must_have` (array): Mandatory features, e.g. garage, fireplace. Unmentioned = unverified, not excluded (unless strict_unknowns).
- `nice_to_have` (array): Soft features that improve ranking.
- `notes` (string): The user's own words, kept for reference; terms in it that match the feature list become soft preferences.
- `offset` (integer)
- `preferred_bedrooms` (integer)
- `property_types` (array)
- `sort` (string)
- `strict_unknowns` (boolean): Exclude listings that do not state a must_have feature (default false: keep and flag).
- `styles` (array): Architectural styles, e.g. Craftsman, Victorian, mid-century modern.

### `get_property_details` (~125 tokens)

Get property details

Everything Realty.Bingo holds on one property (property_id) or listing (listing_id): attributes, current and other listings, listing contact as published, features with evidence, identity-resolution confidence, recent changes and any stored rent/value estimates (labelled as estimates). refresh: true fetches the latest record if the stored one is over a day old.

Input parameters:

- `listing_id` (string)
- `property_id` (string)
- `refresh` (boolean): Fetch the latest listing record from its source if the stored one is over 24 hours old (uses a live refresh).

### `save_property_watchlist` (~163 tokens)

Save a property watchlist

Save the user's search criteria once as a named, persistent watchlist (same criteria as search_properties) with alert preferences (min_score, new listings, price drops with optional minimum percent or amount, back on market). Realty.Bingo then monitors the area on a schedule, independent of any conversation, and records new matching listings, price reductions and relistings as alerts. Saving again with the same name replaces it. Returns how the criteria were interpreted (hard vs soft vs excluded) and a preview from stored data. Preferences about the people in a neighbourhood are refused (fair housing).

Input parameters:

- `alert_prefs` (object)
- `criteria` (object, required)
- `monitoring` (string)
- `name` (string, required)
- `priority` (string)

### `manage_property_watchlist` (~72 tokens)

Manage watchlists

list, get, pause, resume or delete (confirm: true) the user's watchlists by name, or 'matches' to see the best-scoring current listings for one. Also shows plan limits.

Input parameters:

- `action` (string, required)
- `confirm` (boolean)
- `name` (string)

### `get_property_alerts` (~201 tokens)

Get property alerts

New alerts from monitoring: NEW_MATCHING_PROPERTY, NEW_STRONG_STYLE_MATCH, PRICE_DROP, RENT_DROP, PRICE_THRESHOLD_REACHED, RENT_THRESHOLD_REACHED, PROPERTY_BACK_ON_MARKET, LISTING_STATUS_CHANGED, SAVED_PROPERTY_UPDATED, INVESTMENT_CRITERIA_MATCHED. Filter by types (e.g. price changes only) or watchlist. Each alert has the property, source, previous and current values, detection time, freshness and why it matched. Returned alerts are marked retrieved. Relay the message wording; do not upgrade it (a price drop is not a bargain, a removed listing is not a sale).

Input parameters:

- `include_already_retrieved` (boolean)
- `limit` (integer)
- `types` (array): Filter, e.g. ['PRICE_DROP','RENT_DROP'] for price changes or ['NEW_MATCHING_PROPERTY','NEW_STRONG_STYLE_MATCH'] for new matches.
- `watchlist` (string)

### `track_property` (~117 tokens)

Track a property

Follow one property (track), stop (untrack) or list tracked ones. Optional price_below threshold and min_drop_pct. Tracked properties produce alerts on every verified price or status change.

Input parameters:

- `action` (string, required)
- `listing_id` (string)
- `min_drop_pct` (number): Only alert on reductions at least this large (percent).
- `note` (string)
- `price_below` (number): Alert when the asking price (or rent) drops below this.
- `property_id` (string)

### `get_property_history` (~73 tokens)

Get property history

Price and status history for a property: what Realty.Bingo observed (with dates), detected changes, and the listing source's own reported history, kept separate and labelled. Includes cumulative change since first observed. Never infers an earlier price.

Input parameters:

- `listing_id` (string)
- `property_id` (string)

### `compare_properties` (~83 tokens)

Compare properties

Side-by-side comparison of 2-5 properties (property_id) on price, price per sq ft, size, age, HOA, time observed, price changes and stated features (unknown where the listing is silent); optional match scores against a saved watchlist.

Input parameters:

- `property_ids` (array, required)
- `watchlist` (string): Score each against this saved search.

### `analyze_property_investment` (~182 tokens)

Analyze an investment property

Gross rental yield, gross annual rent, price-to-rent and price per sq ft for a sale listing, from the user's monthly_rent, an active rental listing for the same property, or a RentCast rent estimate (labelled). With assumptions (down payment, rate, taxes, insurance, vacancy, repairs, management, capex) also cash flow, cap rate and cash-on-cash, plus a sensitivity table. Gross yield is not a return; always relay the disclaimer.

Input parameters:

- `assumptions` (object)
- `listing_id` (string)
- `monthly_rent` (number): The user's own rent assumption; used instead of an estimate.
- `property_id` (string)
- `use_rent_estimate` (boolean): Use a RentCast rent estimate when no monthly_rent is given (may use a live refresh).

### `record_property_feedback` (~112 tokens)

Record property feedback

Record the user's reaction to a property: like, save (also tracks it), dislike, dismiss (never shown again), hide, contacted_agent, toured, with optional reasons (price, hoa, location, size, condition, style, layout, lot, noise, other). Only when the user says so. Returns learned preference suggestions and clarifying questions to ask.

Input parameters:

- `feedback` (string, required)
- `listing_id` (string)
- `property_id` (string)
- `reasons` (array)

### `manage_realtybingo_account` (~94 tokens)

Manage account and preferences

view the account, plan, usage and every stored preference with its provenance; confirm, reject or delete a learned preference; clear personalization or delete the account (both need confirm: true and an explicit request); set or remove a signed webhook for alerts (paid plans).

Input parameters:

- `action` (string, required)
- `confirm` (boolean)
- `key` (string)
- `webhook_url` (string)

### `get_realtybingo_brief` (~59 tokens)

Realty.Bingo brief

A personalized digest: pending alert counts and the top few, each watchlist's best current matches and data age, tracked properties and their changes this week, learned-preference suggestions and questions worth asking. Does not mark alerts retrieved.

## Diagnostics

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

## Score history

- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72

## Common questions

### What is the Realty.Bingo MCP server?

Realty.Bingo is an MCP server listed in the public MCP registry as io.github.agentstructure/realty. Property search, comparison, investment analysis and watchlists with change alerts. This page covers its hosted endpoint (https://realty.bingo/mcp).

### Is the Realty.Bingo MCP server safe to use?

Realty.Bingo scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Realty.Bingo MCP server expose?

Realty.Bingo exposes 12 tools: search_properties, get_property_details, save_property_watchlist, manage_property_watchlist, get_property_alerts, and 7 more. Their descriptions and schemas cost roughly 1,897 tokens of context every time the server is loaded.

### Does the Realty.Bingo MCP server require authentication?

Yes. Realty.Bingo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Realty.Bingo MCP server still maintained?

Realty.Bingo is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://realty.bingo/mcp
- Website: https://realty.bingo/
- Changelog RSS feed: https://verifymcp.io/servers/agentstructure-realty/realty.xml
- Changelog JSON feed: https://verifymcp.io/servers/agentstructure-realty/realty.json
- HTML version of this page: https://verifymcp.io/servers/agentstructure-realty/realty