France Dvf vs Permisapi MCP — MCP Server Comparison | AllMCPs
France Dvf vs Permisapi MCP
A side-by-side look at the France Dvf and Permisapi MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose France Dvf for real estate work as a local process; choose Permisapi MCP for real estate as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose France Dvf when
You need dedicated capabilities in the Real Estate domain.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
France Dvf is categorized under Real Estate and uses a local stdio subprocess. Permisapi MCP belongs to Real Estate and uses a local stdio subprocess. Pick France Dvf for real estate work and Permisapi MCP for real estate.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
France Dvf is listed as free. Auth: no auth required. Permisapi MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add france-dvf and evan-crx-permisapi-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, France Dvf has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Permisapi MCP has 56/100 (Good) with 3 views, 0 installs and 3 GitHub stars.