Unlisted Property Search MCP server
com.unlistedhomes/unlistedunlistedhomes.comstreamable-httpv1.0.0Scanned
Search and explore residential properties that aren't for sale (yet)
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Unlisted Property Search MCP server can do
The Unlisted Property Search MCP server is published by unlistedhomes.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: autocomplete_tool), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.0.
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
autocomplete_toolAutocomplete a search term to find geographic areas (cities, counties, neighborhoods, school districts, states, etc.) and properties by address.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Search Autocomplete
Only reads 2Show 2 read-only tools
property_details_toolFetch full details for a single Unlisted property by its ID.No findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Property Details
property_search_toolSearch for properties on Unlisted that meet certain criteria.No findings
Why it is in this group
- The name "property_search_tool" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Property Search
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 or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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 20, 2026, 18:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- 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
- yes
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.unlistedhomes.com/mcp: tools/list returned 3 tools to an anonymous client, including autocomplete_tool (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http unlisted https://api.unlistedhomes.com/mcpclaude mcp add --transport http unlisted https://api.unlistedhomes.com/mcpRun 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__unlisted__property_details_tool",
"mcp__unlisted__property_search_tool"
],
"ask": [
"mcp__unlisted__autocomplete_tool"
],
"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 unlisted. Review it before you use it.
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/com.unlistedhomes/unlisted/verify?hash=1d1d0bfa071ef4701c08c7320538dd7b3fc9f0487097a20703b125275ff34fa2" | jq -e '.changed == false'Pinned hash 1d1d0bfa071e, from Nov 14, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.unlistedhomes/unlisted/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.unlistedhomes/unlisted)Source: MCP Registry. Synced Oct 21, 2026, 18:10 UTC.
Unlisted Property Search MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Unlisted Property Search MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Unlisted Property Search MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Unlisted Property Search 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 Unlisted Property Search MCP server have?
- 3 tools: 1 write, 2 read. autocomplete_tool, property_details_tool and property_search_tool.
Does the Unlisted Property Search MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Unlisted Property Search MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Unlisted Property Search MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.