PropFácil
REMOTE · WWW.PROPFACIL.COM
Search authorized real estate in Mexico and manage favorites and publishing with OAuth.
Available components
Last scanned (9 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_property_list). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1283 tokens (~91/item across 14 items; 13 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_property” rewrote its description, which is the text the model reads security
- Tool “get_property_contact” rewrote its description, which is the text the model reads security
- Tool “search_properties” rewrote its description, which is the text the model reads security
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “publish_property” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Aug 26 0
- Schema quality: 68 → 86 ▼ functional
- Tool coverage: 19% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Server version: 1.3.8 → 1.3.9 functional
- “delete_property_list” reworded the description of “listId” cosmetic
- “get_property_list” reworded the description of “listId” cosmetic
- “publish_property” reworded the description of “areaSqm” cosmetic
- “publish_property” reworded the description of “bathrooms” cosmetic
- “publish_property” reworded the description of “bedrooms” cosmetic
- “publish_property” reworded the description of “city” cosmetic
- “publish_property” reworded the description of “currency” cosmetic
- “publish_property” reworded the description of “description” cosmetic
- “publish_property” reworded the description of “isCommercial” cosmetic
- “publish_property” reworded the description of “latitude” cosmetic
- “publish_property” reworded the description of “longitude” cosmetic
- “publish_property” reworded the description of “price” cosmetic
- “publish_property” reworded the description of “state” cosmetic
- “publish_property” reworded the description of “title” cosmetic
- “publish_property” reworded the description of “transactionType” cosmetic
- “remove_property_from_list” reworded the description of “listId” cosmetic
- “remove_property_from_list” reworded the description of “propertyId” cosmetic
- “rename_property_list” reworded the description of “listId” cosmetic
- “rename_property_list” reworded the description of “name” cosmetic
- “render_property_results” reworded the description of “title” cosmetic
- “save_property_to_list” reworded the description of “listId” cosmetic
- “save_property_to_list” reworded the description of “listName” cosmetic
- “save_property_to_list” reworded the description of “note” cosmetic
- “search_properties” reworded the description of “city” cosmetic
- “search_properties” reworded the description of “limit” cosmetic
- “search_properties” reworded the description of “maxPrice” cosmetic
- “search_properties” reworded the description of “minBedrooms” cosmetic
- “search_properties” reworded the description of “minPrice” cosmetic
- “search_properties” reworded the description of “transactionType” cosmetic
- 20 Aug 26 0
First indexed and scored.
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://www.propfacil.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.propfacil.com | CN=YR1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | RSA 4096 | SHA256-RSA | 65ece58c74ea77f8a8e8cd409a474df8cf8 |
| SANs: www.propfacil.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 secure
Validation of www.propfacil.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| propfacil.com. | present | 2371 | 13 | Verified |
| www.propfacil.com. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.propfacil.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.propfacil.com/api/mcp | HTTPS enforced | 302 | https://www.propfacil.com/api/mcp |
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 →
delete_property_list Delete a favorite list ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listId | string | yes | Identifier of a favorite list owned by the authenticated user. |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
| listId | string | yes | – |
No examples provided.
get_property Get property details ~51
Use this when the user wants the details of one PropFácil listing and has supplied a listingKey or ID from search_properties.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A listingKey or listing ID returned by search_properties. |
| Name | Type | Req | Description |
|---|---|---|---|
| property | – | yes | – |
No examples provided.
get_property_contact Get property contact ~55
Use this when the user explicitly asks to contact the advertiser or open the original listing for a property previously returned by PropFácil.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A listingKey or listing ID returned by search_properties or get_property. |
| Name | Type | Req | Description |
|---|---|---|---|
| contact | – | yes | – |
No examples provided.
get_property_list Get a favorite list ~49
Use this when an authenticated user wants to inspect one of their PropFácil favorite lists and its saved properties.
| Name | Type | Req | Description |
|---|---|---|---|
| listId | string | yes | Identifier of a favorite list owned by the authenticated user. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| list | object | yes | – |
No examples provided.
list_property_lists List favorite lists ~35
Use this when an authenticated user wants to see their PropFácil favorite lists. This returns only lists owned by the linked user.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| lists | array | yes | – |
No examples provided.
my_listings List my properties ~28
Use this when an authenticated user asks to review the property listings they published on PropFácil.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| listings | array | yes | – |
No examples provided.
publish_property Publish a property ~293
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.
| Name | Type | Req | Description |
|---|---|---|---|
| areaSqm | number | – | Property area in square meters. |
| bathrooms | number | – | Number of bathrooms, including fractional half-bath values when applicable. |
| bedrooms | integer | – | Number of bedrooms; use zero only when the property has none. |
| city | string | yes | Mexican city or municipality where the property is located. |
| currency | string | – | Currency used for the advertised price. |
| description | string | yes | Public, accurate description of the property. |
| idempotencyKey | string | yes | Stable unique key for this publish request; reuse it when retrying. |
| isCommercial | boolean | – | True for commercial real estate; false for residential real estate. |
| latitude | number | – | WGS84 latitude for the property location. |
| longitude | number | – | WGS84 longitude for the property location. |
| price | number | yes | Positive advertised price in the selected currency. |
| state | string | – | Mexican state where the property is located, when known. |
| title | string | yes | Public listing title shown to prospective buyers or tenants. |
| transactionType | string | yes | Whether the property is offered for sale or lease. |
| Name | Type | Req | Description |
|---|---|---|---|
| confirmUrl | string | – | Private page where the user reviews and activates the draft. |
| id | string|null | yes | – |
| idempotentReplay | boolean | yes | – |
| reasons | array | yes | – |
| status | string | yes | – |
| url | string|null | yes | – |
No examples provided.
remove_property_from_list Remove property from favorites ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listId | string | yes | Identifier of a favorite list owned by the authenticated user. |
| propertyId | string | yes | A listingKey for the saved property to remove. |
| Name | Type | Req | Description |
|---|---|---|---|
| listId | string | yes | – |
| propertyId | string | yes | – |
| removed | boolean | yes | – |
No examples provided.
rename_property_list Rename a favorite list ~58
Use this when an authenticated user asks to rename one of their PropFácil favorite lists.
| Name | Type | Req | Description |
|---|---|---|---|
| listId | string | yes | Identifier of a favorite list owned by the authenticated user. |
| name | string | yes | New name for the favorite list. |
| Name | Type | Req | Description |
|---|---|---|---|
| list | object | yes | – |
No examples provided.
render_property_results Show property results ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| propertyIds | array | yes | Up to 12 listingKey values returned by search_properties. |
| title | string | – | Short user-facing heading for the rendered property selection. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| properties | array | yes | – |
| title | string | yes | – |
No examples provided.
restore_property_results Restore property results ~36
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| render | object|null | yes | – |
No examples provided.
save_property_to_list Save property to favorites ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listId | string | – | Identifier of a favorite list owned by the authenticated user. |
| listName | string | – | Name for a new favorite list; defaults to Favoritos. |
| note | string | – | Optional private note stored with the saved property. |
| propertyId | string | yes | A listingKey returned by search_properties. |
| Name | Type | Req | Description |
|---|---|---|---|
| list | object | yes | – |
| propertyId | string | yes | – |
| saved | boolean | yes | – |
No examples provided.
search_properties Search properties ~163
Use this when the user wants to find PropFácil property listings in Mexico by city, transaction type, price, bedrooms, or geographic radius.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Mexican city or municipality name explicitly requested by the user. |
| limit | integer | – | Maximum number of results to return. |
| maxPrice | number | – | Maximum listing price in the listing currency. |
| minBedrooms | integer | – | Minimum number of bedrooms. |
| minPrice | number | – | Minimum listing price in the listing currency. |
| near | string | – | Map center as lat,lng. Use only a location explicitly supplied by the user. |
| radius | number | – | Search radius in meters. |
| transactionType | string | – | Listing operation: ForSale to buy or ForLease to rent. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| nextCursor | string|null | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the PropFácil MCP server?
PropFácil is a hosted endpoint at https://www.propfacil.com/api/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 · www.propfacil.com
claude mcp add --transport http jonatanvazquez-propfacil 'https://www.propfacil.com/api/mcp'
What is the PropFácil MCP server?
PropFácil is an MCP server listed in the public MCP registry as io.github.jonatanvazquez/propfacil. Search authorized real estate in Mexico and manage favorites and publishing with OAuth. This page covers its hosted endpoint (https://www.propfacil.com/api/mcp).
Is the PropFácil MCP server safe to use?
PropFácil scores 81 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 PropFácil MCP server expose?
PropFácil exposes 13 tools: search_properties, get_property, get_property_contact, render_property_results, restore_property_results, and 8 more. Their descriptions and schemas cost roughly 1,094 tokens of context every time the server is loaded.
Does the PropFácil MCP server require authentication?
No. We connected to PropFácil without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PropFácil MCP server still maintained?
PropFácil 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.