Voxhouses (Portugal)
REMOTE · WWW.VOXHOUSES.PT · SCANNED OCT 2
Property listings in Portugal: search, market stats, comparables, neighbourhoods.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2071 tokens (~295/item across 7 items; 7 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 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
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Voxhouses (Portugal) MCP server?
Voxhouses (Portugal) is a hosted endpoint at https://www.voxhouses.pt/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.voxhouses.pt
claude mcp add --transport http eu-voxs-voxhouses-pt 'https://www.voxhouses.pt/api/mcp'
{
"mcpServers": {
"eu-voxs-voxhouses-pt": {
"url": "https://www.voxhouses.pt/api/mcp"
}
}
} {
"servers": {
"eu-voxs-voxhouses-pt": {
"type": "http",
"url": "https://www.voxhouses.pt/api/mcp"
}
}
} [mcp_servers.eu-voxs-voxhouses-pt] url = "https://www.voxhouses.pt/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"eu-voxs-voxhouses-pt": {
"type": "remote",
"url": "https://www.voxhouses.pt/api/mcp",
"enabled": true
}
}
} openclaw mcp add eu-voxs-voxhouses-pt --url 'https://www.voxhouses.pt/api/mcp' --transport streamable-http
mcp_servers:
eu-voxs-voxhouses-pt:
url: "https://www.voxhouses.pt/api/mcp" {
"McpServers": {
"eu-voxs-voxhouses-pt": {
"Transport": "http",
"Url": "https://www.voxhouses.pt/api/mcp"
}
}
} assistant mcp add eu-voxs-voxhouses-pt -t streamable-http -u 'https://www.voxhouses.pt/api/mcp'
{
"mcpServers": {
"eu-voxs-voxhouses-pt": {
"type": "http",
"url": "https://www.voxhouses.pt/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 2 Oct 2026 · Probed https://www.voxhouses.pt/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=voxhouses.pt | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 3f41434f74ea282d13ebb02524ceb652 |
| SANs: voxhouses.pt, *.voxhouses.pt | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.voxhouses.pt. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pt. | present | 40155 | 13 | Verified |
| voxhouses.pt. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.voxhouses.pt/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.voxhouses.pt/api/mcp | HTTPS enforced | 302 | https://www.voxhouses.pt/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 →
find_similar_properties ~203
Given one listing, find comparable ones: same operation and area, similar typology, floor area and price. Use this when the user likes a property but wants alternatives — 'find me something similar', 'the same but cheaper', 'what else is there in this area'. Pass `maxPrice` for the cheaper case; without it, comparables are drawn from a band around the reference price. Comparability is by location, typology, area and price, not by text similarity: it answers 'is this well priced for what it is', which a keyword search cannot.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of comparables (default 6, max 20). |
| maxPrice | number | – | Optional budget ceiling, in the market currency. Use it for 'similar but cheaper'; it overrides the default band around the reference price. |
| slug | string | yes | Slug of the reference listing, as returned by search_properties or get_property_detail. |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| market | string | yes | – |
| properties | array | yes | – |
| reference | object | yes | The listing the comparables are measured against, echoed back for the comparison. |
| total | number | yes | Comparables returned. |
No examples provided.
get_market_stats ~532
Get price statistics for a slice of the Portugal property market: how many listings match, the median price, the p25–p75 range, the median price per m² and a breakdown by typology. Use this when the user asks what something costs, whether an asking price is fair, or how two areas compare — instead of listing individual properties. Takes the same filters as search_properties and describes exactly the set that tool would return, so the two never disagree. Reports medians and quartiles rather than averages, because property prices have a long right tail and a single luxury listing moves an average. Call once per area to compare areas.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string|array | – | State of repair, or an array of states. Only matches listings whose source published it. |
| energyClass | string | – | Energy certificate class. Selects the whole band the class belongs to: A+/A, B/B-, C, or D-and-below. Only matches listings that carry a certificate. |
| location | string | – | Location: district, municipality, neighbourhood, town or postal-code prefix (e.g. Lisbon, Cascais, Chiado, 2750). Not a free-text keyword search — words that are not places (e.g. 'sea view') will not… |
| minArea | number | – | Minimum floor area in m². Matches either the gross or the useful area, whichever the source published. Only matches listings that published an area. |
| minBathrooms | number | – | Minimum number of bathrooms. Only matches listings whose source published a bathroom count. |
| operation | string | – | buy = for sale, rent = to let. Defaults to buy; a listing is one or the other, so call twice to cover both. |
| priceMax | number | – | Maximum price, in the market currency. Note: listings advertised 'price on request' have no price and are excluded by either price bound. |
| priceMin | number | – | Minimum price, in the market currency. |
| propertyType | string|array | – | Property type, or an array of types. Omit to search all types. `farm` covers rural estates (quintas); `building` is a whole apartment block. |
| typology | string|array | – | Normalised typology code (T0, T1, T2, T3…), where the number is the count of bedrooms. Used in every market, including the German and Polish ones. Matched exactly; pass an array to match several. The… |
| Name | Type | Req | Description |
|---|---|---|---|
| byTypology | array | yes | Up to 6 most represented typologies, each with its own median. |
| count | number | yes | Listings matching the filters, with or without a published price. |
| currency | string | yes | – |
| market | string | yes | – |
| operation | string | yes | – |
| price | object|null | – | Price distribution, in percentiles. null when no matching listing publishes a price. There is deliberately no min or max: listings come from third-party sources and the extremes are set by data error… |
| pricePerM2Median | number|null | – | Median price per m² among listings that published both a price and an area. Best figure for comparing areas. |
| priced | number | yes | Subset with a published price — the base of every figure below. A large gap to `count` means many listings in this slice are 'price on request'. |
No examples provided.
get_property_detail ~78
Get the complete record of one listing in Portugal by its slug. Use this after search_properties when the user asks about a specific property: full description, features, photos, energy rating, condition, floor, year built, seller and the original source URL to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Unique listing slug, as returned by search_properties. |
| Name | Type | Req | Description |
|---|---|---|---|
| bathrooms | number | – | – |
| bedrooms | number | – | – |
| condition | string|null | – | – |
| currency | string | – | ISO 4217 code of this market. |
| description | string | – | – |
| district | string | – | District or region. |
| elevator | string|null | – | – |
| energyClass | string|null | – | – |
| features | array | – | Amenities as published by the source (Portuguese labels). |
| firstSeen | string | yes | ISO 8601 date the listing was first published. |
| floor | string|null | – | – |
| houseArea | number|null | – | Gross floor area in m². |
| landArea | number|null | – | Plot area in m²; relevant for houses, land and farms. |
| lastSeen | string | yes | ISO 8601 date we last confirmed the listing at the source. |
| municipality | string|null | – | Municipality (LAU) name. |
| neighbourhood | string|null | – | Neighbourhood, when the source located the listing precisely enough. |
| operation | string | yes | comprar = for sale, arrendar = to let. |
| orientation | string|null | – | – |
| phone | string|null | – | Advertiser phone when published at the source. |
| photos | array | – | Up to 5 image URLs. |
| price | number|null | – | null means the source does not publish a price (on request). |
| priceLabel | string | – | Formatted price for display; empty when price is null. |
| pricePerM2 | number|null | – | – |
| propertyType | string|null | – | Property type; the same token accepted by the propertyType filter. |
| sellerName | string|null | – | – |
| slug | string | yes | Stable identifier; use it in get_property_detail. |
| source | string|null | – | Portal or agency site the listing came from; null when published directly with us. |
| sourceUrl | string|null | yes | Original listing URL at the source. Cite this alongside url. |
| title | string | yes | – |
| typology | string | – | T-notation typology (T0…T6+); empty when unknown. |
| updatedAt | string | – | ISO 8601 date the record last changed on our side. |
| url | string | yes | Canonical listing page on this market's domain. |
| usefulArea | number|null | – | Net/usable floor area in m². |
| verified | boolean | – | Advertiser identity verified by us. |
| yearBuilt | string|null | – | – |
No examples provided.
search_articles ~74
Search editorial articles about the property market in Portugal: buying and renting guides, market analysis and practical advice. Use this when the user asks how something works — mortgages, contracts, taxes, the buying process — rather than asking for listings.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default 5, max 10). |
| Name | Type | Req | Description |
|---|---|---|---|
| articles | array | yes | – |
No examples provided.
search_neighbourhoods ~113
Search neighbourhood and municipality guides for Portugal, with median price per m² for buying and renting, price trend and an editorial summary. Use this when the user asks where to live or where to buy, or wants to compare areas, instead of asking for individual listings.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default 8, max 20). |
| query | string | – | Neighbourhood, municipality or district (e.g. Cascais, Príncipe Real). Omit to list all. |
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | – |
| neighbourhoods | array | yes | – |
| total | number | yes | – |
No examples provided.
search_properties ~626
Search current residential, rural and commercial real-estate listings for sale or rent in Portugal. Use this whenever the user wants to find, compare or explore properties — by location, budget, typology, property type, condition or energy rating. Returns price, price per m², typology, areas, neighbourhood, source and a citable listing URL, plus `total`: the exact number of listings matching the filters, which makes this tool usable to answer 'how many' questions. Listings are aggregated from portals and agency sites and refreshed continuously; each result carries the date it was last checked at the source. Sources publish uneven detail: filtering on an attribute silently excludes listings that omit it, so prefer the broadest filters that answer the question and report `total` as a floor, not a census.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string|array | – | State of repair, or an array of states. Only matches listings whose source published it. |
| energyClass | string | – | Energy certificate class. Selects the whole band the class belongs to: A+/A, B/B-, C, or D-and-below. Only matches listings that carry a certificate. |
| limit | number | – | Results per page (default 10, max 20). |
| location | string | – | Location: district, municipality, neighbourhood, town or postal-code prefix (e.g. Lisbon, Cascais, Chiado, 2750). Not a free-text keyword search — words that are not places (e.g. 'sea view') will not… |
| minArea | number | – | Minimum floor area in m². Matches either the gross or the useful area, whichever the source published. Only matches listings that published an area. |
| minBathrooms | number | – | Minimum number of bathrooms. Only matches listings whose source published a bathroom count. |
| operation | string | – | buy = for sale, rent = to let. Defaults to buy; a listing is one or the other, so call twice to cover both. |
| page | number | – | 1-based page number. Use it with `total` to walk through a large result set. |
| priceMax | number | – | Maximum price, in the market currency. Note: listings advertised 'price on request' have no price and are excluded by either price bound. |
| priceMin | number | – | Minimum price, in the market currency. |
| propertyType | string|array | – | Property type, or an array of types. Omit to search all types. `farm` covers rural estates (quintas); `building` is a whole apartment block. |
| sort | string | – | Result order. Default `recent` (most recently published first). |
| typology | string|array | – | Normalised typology code (T0, T1, T2, T3…), where the number is the count of bedrooms. Used in every market, including the German and Polish ones. Matched exactly; pass an array to match several. The… |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| hasMore | boolean | yes | true when further pages are available. |
| market | string | yes | ISO country code of this market. |
| operation | string | – | The operation actually searched (comprar = for sale, arrendar = to let). |
| page | number | yes | – |
| pageSize | number | – | – |
| properties | array | yes | – |
| shown | number | – | Listings returned on this page. |
| total | number | yes | Exact number of listings in this market matching the filters, across all pages. |
No examples provided.
search_properties_by_description ~445
Search Portugal listings by describing the property in plain language, matched against listing text by meaning rather than keywords. Use this for wants that are not filter fields — 'a renovated loft with exposed brick', 'quiet, lots of natural light, close to a school', 'a ruin to restore with a sea view'. Prefer search_properties when the request is entirely structural (typology, budget, location), and this tool when it is descriptive; combine both by passing structural filters here too, which are applied as hard constraints while the description only ranks. Results are ordered by relevance, so `total` is the number matching the structural filters, not the number that fit the description.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What the user is looking for, in their own words. Full phrases work better than keywords. Pass the qualities here and the hard limits in the other arguments. |
| limit | number | – | Maximum number of results (default 10, max 20). |
| location | string | – | Location: district, municipality, neighbourhood, town or postal-code prefix (e.g. Lisbon, Cascais, Chiado, 2750). Not a free-text keyword search — words that are not places (e.g. 'sea view') will not… |
| minArea | number | – | Minimum floor area in m². Matches either the gross or the useful area, whichever the source published. Only matches listings that published an area. |
| operation | string | – | buy = for sale, rent = to let. Defaults to buy; a listing is one or the other, so call twice to cover both. |
| priceMax | number | – | Maximum price, in the market currency. Note: listings advertised 'price on request' have no price and are excluded by either price bound. |
| priceMin | number | – | Minimum price, in the market currency. |
| propertyType | string | – | A single property type. Unlike search_properties, this tool takes one, not a list. |
| typology | string | – | A single exact typology code (T0, T1, T2…), where the number is the count of bedrooms. Buckets are not accepted here. |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| market | string | yes | – |
| properties | array | yes | Ordered by relevance to the description, most relevant first. |
| shown | number | yes | – |
| total | number | yes | Listings matching the structural filters. The description narrows the ranking, not this count. |
No examples provided.
What is the Voxhouses (Portugal) MCP server?
Voxhouses (Portugal) is an MCP server listed in the public MCP registry as eu.voxs/voxhouses-pt. Property listings in Portugal: search, market stats, comparables, neighbourhoods. This page covers its hosted endpoint (https://www.voxhouses.pt/api/mcp).
Is the Voxhouses (Portugal) MCP server safe to use?
Voxhouses (Portugal) scores 80 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 Voxhouses (Portugal) MCP server expose?
Voxhouses (Portugal) exposes 7 tools: search_properties, search_properties_by_description, get_market_stats, find_similar_properties, get_property_detail, and 2 more. Their descriptions and schemas cost roughly 2,071 tokens of context every time the server is loaded.
Does the Voxhouses (Portugal) MCP server require authentication?
No. We connected to Voxhouses (Portugal) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Voxhouses (Portugal) MCP server still maintained?
Voxhouses (Portugal) is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.