Landprice vs Codealive MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Landprice vs Codealive MCP
In-depth architectural comparison of the Landprice and Codealive MCP 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
Landprice
Developer Tools · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Codealive MCP
Developer Tools · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Landprice if you need specialized Developer Tools tools running via a local process. Choose Codealive MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
L
Choose Landprice when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
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…
Codealive MCP Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
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).
Landprice is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Codealive MCP belongs to Developer Tools using local stdio subprocess. Select Landprice when you need capabilities focused on developer tools and Codealive MCP when you require tools for developer tools.