# Voxhouses (Portugal)

> Property listings in Portugal: search, market stats, comparables, neighbourhoods.

- name: eu.voxs/voxhouses-pt
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 79/100 flags: no-repository
- quality: 91/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/eu.voxs%2Fvoxhouses-pt
- tools: https://api.protogrid.dev/v1/servers/eu.voxs%2Fvoxhouses-pt/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "voxhouses-pt": {
      "type": "http",
      "url": "https://www.voxhouses.pt/api/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 98
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-95% ~updated-49d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 91/100 (strong)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2024-11-05; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 7 of 7 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 2,959 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 7, about 2,959 tokens to load them all
- tool set hash: a1d34b1e5dbb63fc910442ee2579cd16
- badge: [![protogrid quality](https://protogrid.dev/badge/eu.voxs/voxhouses-pt.svg)](https://protogrid.dev/servers/eu.voxs/voxhouses-pt)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://www.voxhouses.pt/api/mcp (streamable-http, auth none, reachable true, uptime30d 0.94690263)

## Packages

_none_

## Tools (7)

- `find_similar_properties`: 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.
- `get_market_stats`: 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.
- `get_property_detail`: 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.
- `search_articles`: 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.
- `search_neighbourhoods`: 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.
- `search_properties`: 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.
- `search_properties_by_description`: 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.