Yatmo MCP server
OfficialRelated Servers
Alternatives to Yatmo MCP server
- AlicenseAqualityDmaintenanceProvides US real estate data including housing stats, demographics, nearby amenities, area comparisons, cost-of-living analysis, and neighborhood search via free public APIs without any API keys.6MIT
Related Servers
- -licenseNot gradedqualityCmaintenanceProvides real-time London area intelligence including postcode data, crime, schools, transport, and investment metrics, enabling AI assistants to answer property-related queries.-
- AlicenseAqualityBmaintenanceEnables AI assistants to query UK property data including EPCs, sale history, planning, flood risk, council tax, demographics, and more via the Homedata API.1869 PyPIMIT
- AlicenseAqualityBmaintenanceUnified UK property search across major portals with deduplication and open-data enrichment, enabling natural-language queries for listings, sold prices, EPC, crime, schools, and market stats.10MIT

OneGoodAreaofficial
AlicenseNot gradedqualityBmaintenanceOneGoodArea gives AI agents and developer tools access to sourced, dated and confidence-rated place intelligence across Great Britain. Resolve locations, analyse and compare neighbourhoods, discover similar areas, generate decision-focused briefs and monitor changes through 12 MCP tools backed by deterministic, explainable data.737 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to resolve places and statistical variables, then retrieve harmonised public statistics such as population, income, health, employment, and emissions with publisher provenance and child-place comparisons.56 npmMIT
- FlicenseNot gradedqualityBmaintenanceUK property listing description generator. Give an AI assistant a postcode or address — it fetches comparable sales, EPC ratings, and Rightmove listings, then writes three copy variants ready for Rightmove, social media, and email.1-
TDQS
Scored across 4 tools
The four tools overlap substantially: yatmo_get_location_summary already reports nearest school, supermarket, and public transport, which duplicates what yatmo_get_nearest_by_category returns, and yatmo_get_accessibility_profile re-covers public-transport/nearest-stop data. Descriptions do clarify the granularity (aggregated summary vs. list vs. single nearest vs. derived accessibility view), so an agent can mostly choose correctly, but the boundaries are fuzzy.
All tools follow a strict 'yatmo_get_<noun>' snake_case pattern (get_location_summary, get_nearby_pois, get_nearest_by_category, get_accessibility_profile). The verb and namespace prefix are uniform throughout with no deviation.
Four tools is a tight but sensible scope for a neighbourhood/property-location service, and each tool maps to a distinct query granularity. It is on the lean side, but no tool feels redundant enough to be dead weight.
The surface covers the core location workflows: aggregate summary, filtered POI listing, single nearest POI with distance/travel time, and an accessibility view. Minor gaps exist (e.g., no batch/multi-category query or distance/commute matrix), but agents can compose the existing tools to cover most questions.