Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Realty.Bingo

REMOTE · REALTY.BINGO

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

Available components

74 Trust /100

Last scanned (3 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 18 Oct 2026.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 29% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 +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.

  • 16 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 15 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Oct 26 72

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://realty.bingo/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=realty.bingo CN=YR2,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 RSA 2048 SHA256-RSA 5007cd1702831c3fa181465daa1377c3b8b
SANs: realty.bingo
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of realty.bingo. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
bingo. present 26002, 43616 8, 8 Verified
realty.bingo. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://realty.bingo/mcp Verified 200
http (plaintext) http://realty.bingo/mcp HTTPS enforced 308 https://realty.bingo/mcp
MCP tools · 12 exposed · ~1,897 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_property_investment ~182

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.

NameTypeReqDescription
assumptionsobject––
listing_idstring––
monthly_rentnumber–The user's own rent assumption; used instead of an estimate.
property_idstring––
use_rent_estimateboolean–Use a RentCast rent estimate when no monthly_rent is given (may use a live refresh).

No output schema declared.

No examples provided.

compare_properties ~83

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.

NameTypeReqDescription
property_idsarrayyes–
watchliststring–Score each against this saved search.

No output schema declared.

No examples provided.

get_property_alerts ~201

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).

NameTypeReqDescription
include_already_retrievedboolean––
limitinteger––
typesarray–Filter, e.g. ['PRICE_DROP','RENT_DROP'] for price changes or ['NEW_MATCHING_PROPERTY','NEW_STRONG_STYLE_MATCH'] for new matches.
watchliststring––

No output schema declared.

No examples provided.

get_property_details ~125

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.

NameTypeReqDescription
listing_idstring––
property_idstring––
refreshboolean–Fetch the latest listing record from its source if the stored one is over 24 hours old (uses a live refresh).

No output schema declared.

No examples provided.

get_property_history ~73

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.

NameTypeReqDescription
listing_idstring––
property_idstring––

No output schema declared.

No examples provided.

get_realtybingo_brief ~59

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

manage_property_watchlist ~72

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.

NameTypeReqDescription
actionstringyes–
confirmboolean––
namestring––

No output schema declared.

No examples provided.

manage_realtybingo_account ~94

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).

NameTypeReqDescription
actionstringyes–
confirmboolean––
keystring––
webhook_urlstring––

No output schema declared.

No examples provided.

record_property_feedback ~112

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.

NameTypeReqDescription
feedbackstringyes–
listing_idstring––
property_idstring––
reasonsarray––

No output schema declared.

No examples provided.

save_property_watchlist ~163

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).

NameTypeReqDescription
alert_prefsobject––
criteriaobjectyes–
monitoringstring––
namestringyes–
prioritystring––

No output schema declared.

No examples provided.

search_properties ~616

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.

NameTypeReqDescription
allow_live_requestboolean–false = stored data only (no provider request).
avoidarray–Features that exclude a listing when the listing states them, e.g. fixer-upper, pool.
bedrooms_exceptionobject–e.g. 'three bedrooms, but two is fine with an office': min_bedrooms 3 plus {min_bedrooms: 2, requires: ['home office']}
exclude_property_typesarray––
ideal_max_pricenumber–Soft target: listings above it rank lower but stay in.
include_non_matchingboolean–true = also return listings that fail a hard requirement, with the reason.
investmentobject––
limitinteger––
listing_typestringyes–
locationobjectyes–
max_distanceobject–Straight-line distance from a place the user names (e.g. work). Not driving time.
max_hoa_feenumber––
max_pricenumber–Hard ceiling: listings above it are excluded.
min_bathroomsnumber––
min_bedroomsinteger––
min_living_areainteger––
min_lot_areainteger––
min_pricenumber––
min_year_builtinteger––
must_havearray–Mandatory features, e.g. garage, fireplace. Unmentioned = unverified, not excluded (unless strict_unknowns).
nice_to_havearray–Soft features that improve ranking.
notesstring–The user's own words, kept for reference; terms in it that match the feature list become soft preferences.
offsetinteger––
preferred_bedroomsinteger––
property_typesarray––
sortstring––
strict_unknownsboolean–Exclude listings that do not state a must_have feature (default false: keep and flag).
stylesarray–Architectural styles, e.g. Craftsman, Victorian, mid-century modern.

No output schema declared.

No examples provided.

track_property ~117

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.

NameTypeReqDescription
actionstringyes–
listing_idstring––
min_drop_pctnumber–Only alert on reductions at least this large (percent).
notestring––
price_belownumber–Alert when the asking price (or rent) drops below this.
property_idstring––

No output schema declared.

No examples provided.

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.

remote · realty.bingo

# add to Claude Code
claude mcp add --transport http agentstructure-realty 'https://realty.bingo/mcp'
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.