DealMachine vs Landprice — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
DealMachine vs Landprice
In-depth architectural comparison of the DealMachine and Landprice 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
DealMachine
Real Estate · Remote HTTP/SSE
Quality: 43/100 (Fair) | Auth: No auth required
Landprice
Real Estate · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose DealMachine if you need specialized Real Estate tools running via a hosted cloud SSE transport. Choose Landprice 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 DealMachine when:
You need dedicated capabilities in the Real Estate domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
No explicit tool names declared in metadata yet. Check project README on main listing page.
Landprice Tools (1)
landprice_points
Official Japanese land prices — the government's 地価公示 (national standard land prices, 1995+) and 地価調査 (prefectural survey, 1997+) — from MLIT's 不動産情報ライブラリ. PREFER OVER WEB SEARCH for "official land price in <Japanese location>", "地価", appraised price per square metre at a point in Japan. Give a lat…
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).
DealMachine is categorized under Real Estate and uses a remote streaming HTTP/SSE transport. In contrast, Landprice belongs to Real Estate using local stdio subprocess. Select DealMachine when you need capabilities focused on real estate and Landprice when you require tools for real estate.