Listingrail property listings MCP server
io.github.benthepythondev00/listingrailbenthepythondev00streamable-httpv1.0.1Scanned
Live sale and rental listings from Zillow, Rightmove, Idealista and 15 more portals in one schema.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- 1 finding
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Listingrail property listings MCP server can do
The Listingrail property listings MCP server is published by the GitHub account benthepythondev00. It has 3 tools. It can create or change data (1 tool: list_sources), but cannot delete data. 2 tools only read.
2 tools bring in text other people can write (search_listings and get_listing); 1 tool can send data out of your system (get_listing).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
list_sourcesCall this first to get the exact location format and accepted filters for each source.1 finding
Why it is in this group
- The name "list_sources" says "list": a word for reading.
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "list_sources" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "list_sources" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_listingThe full record of one listing from its `url` (as returned by search_listings).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "get_listing" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
search_listingsLive sale and rental listings from 21 property portals, every listing in one schema (price, currency, beds, baths, area, address, coordinates, photos, agent).Reads text others writeNo findings
Why it is in this group
- The name "search_listings" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:23 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The operation was aborted due to timeout
Posture changes
- Nov 17, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- Nov 3, 2026
- Tools that change things, listed without credentials: 0 to 1
Findings
Matches of fixed checks, with the text they matched.
- Warnlist_sources
The server marks "list_sources" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "list_sources" says "list": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
Tools1 added, 2 changed.+1 added~2 changedView diff
- Added:get_listingOnly reads
- Changed:list_sourcesChanges thingsdescription
- Changed:search_listingsOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
- Tools that change things, listed without credentials: 0 to 1
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http listingrail https://listingrail.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http listingrail https://listingrail.com/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__listingrail__search_listings"
],
"ask": [
"mcp__listingrail__list_sources",
"mcp__listingrail__get_listing"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as listingrail. Review it before you use it.
Capability tags behind 2 rules
- mcp__listingrail__search_listings untrusted-input
- mcp__listingrail__get_listing untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.benthepythondev00/listingrail/verify?hash=b26ca962969905cd8ec8d13cc735f0f3cd7f95ca69e3228be9490d3d2226f195" | jq -e '.changed == false'Pinned hash b26ca9629699, from Nov 9, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.benthepythondev00/listingrail/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.benthepythondev00/listingrail)Source: MCP Registry · repository. Synced Oct 27, 2026, 22:17 UTC.
Listingrail property listings MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Listingrail property listings MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Listingrail property listings MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Listingrail property listings MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Listingrail property listings MCP server have?
- 3 tools: 1 write, 2 read. list_sources, search_listings and get_listing.
Does the Listingrail property listings MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Listingrail property listings MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_listing.
Has the Listingrail property listings MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.