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.

Listingrail property listings

REMOTE · LISTINGRAIL.COM

Live sale and rental listings from Zillow, Rightmove, Idealista and 15 more portals in one schema.

Available components

+3 this week 76 Trust /100

Last scanned (5 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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 Security80
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 667 tokens (~222/item across 3 items; 3 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 Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 4 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 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.

  • 29 Oct 26 +2
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “list_sources” rewrote its description, which is the text the model reads security
    • Tool “search_listings” rewrote its description, which is the text the model reads security
    • Schema quality: 434 → 667 ▼ functional
    • New tool “get_listing” functional
    • “search_listings” added an optional parameter “offset” cosmetic
  • 27 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 26 Oct 26 70

    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 5 Nov 2026 · Probed https://listingrail.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=listingrail.com CN=YE1,O=Let's Encrypt,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA384 54647f30735d07ba23a6117fa6cfe4de035
SANs: listingrail.com, www.listingrail.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of listingrail.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
listingrail.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://listingrail.com/mcp Verified 200
http (plaintext) http://listingrail.com/mcp HTTPS enforced 301 https://listingrail.com/mcp
MCP tools · 3 exposed · ~619 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
get_listing ~99

The full record of one listing from its `url` (as returned by search_listings). Costs 1 credit; a failed read costs nothing. Works only for sources with details=true in list_sources: realtor, redfin-rentals, craigslist (Craigslist and Redfin rentals among them).

NameTypeReqDescription
sourcestringyesPortal key of the listing.
urlstringyesThe listing's `url` from a search_listings answer.

No output schema declared.

No examples provided.

list_sources ~57

Call this first to get the exact location format and accepted filters for each source. Lists the portals search_listings can read: country, rent or sale, accepted filters, how to write the location and whether get_listing works for it. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_listings ~463

Live sale and rental listings from 21 property portals, every listing in one schema (price, currency, beds, baths, area, address, coordinates, photos, agent). Costs 1 credit per listing returned; a failed portal read costs nothing. Portal keys by country: AE: bayut (rent/sale), propertyfinder (sale/rent); CA: padmapper (rent); DE: immobilienscout24 (rent/sale), kleinanzeigen (rent/sale); ES: idealista (sale/rent), fotocasa (sale/rent); GB: rightmove (sale/rent), zoopla (sale/rent); IE: daft (rent/sale); IT: idealista (sale/rent); PL: otodom (rent/sale); PT: idealista (sale/rent), imovirtual (sale/rent); SE: hemnet (sale); US: zillow (sale), realtor (sale/rent), zillow-rentals (rent), redfin (sale), redfin-rentals (rent), zumper (rent), padmapper (rent), apartments-com (rent), craigslist (rent/sale). Call list_sources first for the location format and the filters each portal takes. Returns at most 50 listings per call; when `next_offset` is in the answer, call again with it as `offset` for the next page (only the rows returned are charged). Pass a listing's `url` to get_listing for its full record.

NameTypeReqDescription
filtersobject–Optional; only where the portal accepts them (see list_sources).
limitinteger–Listings to return (1 credit each).
locationstringyesPlace as the portal expects it (see list_sources), e.g. 'Austin, TX', 'SW11', 'madrid', or a search link from the portal.
offsetinteger–Listings to skip, for paging: use the `next_offset` of the previous answer. offset + limit may not pass 500.
sourcestringyesPortal key, e.g. 'zillow', 'rightmove', 'idealista'.
typestring–Rent or sale; default is the portal's first kind.

No output schema declared.

No examples provided.

Install

How do I install the Listingrail property listings MCP server?

Listingrail property listings is a hosted endpoint at https://listingrail.com/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 · listingrail.com

# add to Claude Code
claude mcp add --transport http benthepythondev00-listingrail 'https://listingrail.com/mcp'
Common questions

What is the Listingrail property listings MCP server?

Listingrail property listings is an MCP server listed in the public MCP registry as io.github.benthepythondev00/listingrail. Live sale and rental listings from Zillow, Rightmove, Idealista and 15 more portals in one schema. This page covers its hosted endpoint (https://listingrail.com/mcp).

Is the Listingrail property listings MCP server safe to use?

Listingrail property listings scores 76 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 Listingrail property listings MCP server expose?

Listingrail property listings exposes 3 tools: search_listings, list_sources, get_listing. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.

Does the Listingrail property listings MCP server require authentication?

No. We connected to Listingrail property listings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Listingrail property listings MCP server still maintained?

Listingrail property listings is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.