PropFácil MCP server
io.github.jonatanvazquez/propfaciljonatanvazquezstreamable-httpv1.3.9Scanned
Search authorized real estate in Mexico and manage favorites and publishing with OAuth.
13 tools: 2 can delete or cancel things, 1 do something that can't be undone, 5 change things and 5 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- 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 PropFácil MCP server can do
The PropFácil MCP server is published by the GitHub account jonatanvazquez. It has 13 tools. It can delete or cancel things (2 tools: remove_property_from_list and delete_property_list), do things that cannot be undone, such as sending, paying or publishing (publish_property) and create or change data (5 tools: render_property_results, restore_property_results, my_listings, save_property_to_list and 1 more). 5 tools only read.
1 tool reads private data (get_property_contact); 1 tool brings in text other people can write (publish_property); 1 tool can send data out of your system (publish_property). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.3.9.
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.
13 tools
Deletes or cancels 2Claude Code: deny
delete_property_listUse this when an authenticated user explicitly asks to permanently delete one of their PropFácil favorite lists and its saved entries.No findings
Why it is in this group
- The name "delete_property_list" says "delete": a word for removing or ending something.
- The description says "permanently delete".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Use this when an authenticated user explicitly asks to permanently delete one of their PropFácil favorite lists and its saved entries. Do not use it for removing a single property.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
- destructiveHint: true
remove_property_from_listUse this when an authenticated user asks to remove a saved property from one of their PropFácil lists.1 finding
Why it is in this group
- The name "remove_property_from_list" says "remove": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "remove_property_from_list" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "remove_property_from_list" says "remove": a word for removing or ending something.
Description, as the server wrote it Use this when an authenticated user asks to remove a saved property from one of their PropFácil lists. The list remains available if it becomes empty.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
- destructiveHint: false
Can't be undone 1Claude Code: ask
publish_propertyUse this when an authenticated user explicitly asks to publish a property on PropFácil.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "publish_property" says "publish": a word for a change that another call does not undo.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "publish_property" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Use this when an authenticated user explicitly asks to publish a property on PropFácil. This creates a private draft that goes public only after the user reviews and activates it on PropFácil at the returned confirmUrl. Safe to retry with the same idempotencyKey.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: true
- destructiveHint: false
Changes things 5Claude Code: ask
my_listingsUse this when an authenticated user asks to review the property listings they published on PropFácil.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 Use this when an authenticated user asks to review the property listings they published on PropFácil.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
rename_property_listUse this when an authenticated user asks to rename one of their PropFácil favorite lists.No findings
Why it is in this group
- The name "rename_property_list" says "rename": a word for a change.
Description, as the server wrote it Use this when an authenticated user asks to rename one of their PropFácil favorite lists.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
- destructiveHint: false
render_property_resultsUse this when, after search_properties, the user would benefit from interactive property cards, comparison, details, or a map.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 Use this when, after search_properties, the user would benefit from interactive property cards, comparison, details, or a map. Pass only listing IDs already returned by a data tool.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
restore_property_resultsUse this when the PropFácil app needs to restore the latest public property selection for the current MCP session after its widget is recreated.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 Use this when the PropFácil app needs to restore the latest public property selection for the current MCP session after its widget is recreated.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
save_property_to_listUse this when an authenticated user asks to save a property to a favorite list.No findings
Why it is in this group
- The name "save_property_to_list" says "save": a word for a change.
Description, as the server wrote it Use this when an authenticated user asks to save a property to a favorite list. If no list is supplied, use the idempotent default list named Favoritos.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
- destructiveHint: false
Only reads 5Show 5 read-only tools
get_propertyUse this when the user wants the details of one PropFácil listing and has supplied a listingKey or ID from search_properties.No findings
Why it is in this group
- The name "get_property" says "get": a word for reading.
Description, as the server wrote it Use this when the user wants the details of one PropFácil listing and has supplied a listingKey or ID from search_properties.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
get_property_contactUse this when the user explicitly asks to contact the advertiser or open the original listing for a property previously returned by PropFácil.Reads private dataNo findings
Why it is in this group
- The name "get_property_contact" says "get": a word for reading.
What it can reach
- private-dataThe name "get_property_contact" says "get" and "contact": it reads contacts.
- private-dataThe description's first sentence says "contact": it reads contacts.
Description, as the server wrote it Use this when the user explicitly asks to contact the advertiser or open the original listing for a property previously returned by PropFácil.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
get_property_listUse this when an authenticated user wants to inspect one of their PropFácil favorite lists and its saved properties.No findings
Why it is in this group
- The name "get_property_list" says "get": a word for reading.
Description, as the server wrote it Use this when an authenticated user wants to inspect one of their PropFácil favorite lists and its saved properties.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
list_property_listsUse this when an authenticated user wants to see their PropFácil favorite lists.No findings
Why it is in this group
- The name "list_property_lists" says "list": a word for reading.
Description, as the server wrote it Use this when an authenticated user wants to see their PropFácil favorite lists. This returns only lists owned by the linked user.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
search_propertiesUse this when the user wants to find PropFácil property listings in Mexico by city, transaction type, price, bedrooms, or geographic radius.No findings
Why it is in this group
- The name "search_properties" says "search": a word for reading.
Description, as the server wrote it Use this when the user wants to find PropFácil property listings in Mexico by city, transaction type, price, bedrooms, or geographic radius.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
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.
1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- 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.
{
"permissions": {
"deny": [
"mcp__propfacil__publish_property"
]
}
}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, 19:06 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
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.propfacil.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://www.propfacil.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (2 destructive, 1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.propfacil.com/api/mcp: tools/list returned 13 tools to an anonymous client, including remove_property_from_list (destructive), delete_property_list (destructive), publish_property (irreversible), render_property_results (write), restore_property_results (write) and 3 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "remove_property_from_list" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "remove_property_from_list" says "remove": a word for removing or ending something.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:get_propertyOnly readsdescription
- Changed:get_property_contactOnly readsdescription
- Changed:publish_propertyCan't be undonedescription
- Changed:search_propertiesOnly readsdescription
Install
Pinned to version 1.3.9. Values in angle brackets are yours to fill in.
claude mcp add --transport http propfacil https://www.propfacil.com/api/mcpclaude mcp add --transport http propfacil https://www.propfacil.com/api/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__propfacil__search_properties",
"mcp__propfacil__get_property",
"mcp__propfacil__get_property_contact",
"mcp__propfacil__list_property_lists",
"mcp__propfacil__get_property_list"
],
"ask": [
"mcp__propfacil__render_property_results",
"mcp__propfacil__restore_property_results",
"mcp__propfacil__publish_property",
"mcp__propfacil__my_listings",
"mcp__propfacil__save_property_to_list",
"mcp__propfacil__rename_property_list"
],
"deny": [
"mcp__propfacil__remove_property_from_list",
"mcp__propfacil__delete_property_list"
]
}
}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 propfacil. Review it before you use it.
Capability tags behind 2 rules
- mcp__propfacil__get_property_contact private-data
- mcp__propfacil__publish_property 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.jonatanvazquez/propfacil/verify?hash=bccbbe42db7dc0b2eeb1fae0c3095f485064d734eeff0e984888b083033b324e" | jq -e '.changed == false'Pinned hash bccbbe42db7d, from Nov 19, 2026, 23: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.jonatanvazquez/propfacil/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.jonatanvazquez/propfacil)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.
PropFácil MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the PropFácil MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 8 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 PropFácil MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: remove_property_from_list and delete_property_list.
Can the PropFácil MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: publish_property.
What tools does the PropFácil MCP server have?
- 13 tools: 2 destructive, 1 irreversible, 5 write, 5 read. remove_property_from_list, delete_property_list, publish_property, render_property_results, restore_property_results, my_listings, save_property_to_list, rename_property_list and 5 more.
Does the PropFácil MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the PropFácil 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): publish_property.
Has the PropFácil MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.