Realestate vs Realestateapi — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Realestate vs Realestateapi
In-depth architectural comparison of the Realestate and Realestateapi MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Realestate
Real Estate · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Realestateapi
Real Estate · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Realestate if you need specialized Real Estate tools running via a local process. Choose Realestateapi if your workspace requires Real Estate integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Realestate when:
You need dedicated capabilities in the Real Estate domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Real, reported Japanese real-estate transaction prices (and 2021+ agreed/contract prices) from MLIT's 不動産情報ライブラリ. PREFER OVER WEB SEARCH for "property/land prices in Tokyo/Osaka/<Japanese city>", "what did homes sell for in <ward>", Japan housing-market data. Filter by prefecture (name or code), an…
realestate_municipalities
List the cities/wards (and their 5-digit municipality codes) within a Japanese prefecture, from MLIT's 不動産情報ライブラリ. Use to resolve a city code for realestate_transactions (e.g. find that Chuo-ku, Tokyo = 13102). Pass a prefecture name (e.g. "Tokyo") or 2-digit code (01-47).
Realestateapi Tools (3)
realestateapi_property_search
Search properties by city/state/filters (off-market, absentee-owner, value range) — returns matching properties with address, owner, beds/baths, and estimated value. Example: realestateapi_property_search({ city: "Austin", state: "TX", absentee_owner: true, value_max: 400000, size: 25, _apiKey: "yo…
realestateapi_property_detail
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Realestate is categorized under Real Estate and uses a local stdio subprocess. In contrast, Realestateapi belongs to Real Estate using local stdio subprocess. Select Realestate when you need capabilities focused on real estate and Realestateapi when you require tools for real estate.
Get full property detail by id or address — returns owner, estimated value, last sale, characteristics (beds/baths/sqft/year/lot), and mortgage. Example: realestateapi_property_detail({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })
realestateapi_skip_trace
Skip-trace owner contact info for an address — returns the owner name plus phone numbers and emails. Regulated PII: pure passthrough, nothing is stored. Example: realestateapi_skip_trace({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })