Attom vs Permisapi MCP
A side-by-side look at the Attom 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 Attom 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 Attom when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
Choose Permisapi MCP when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PERMISAPI_KEY. - You want tools like
search_permits, get_permit_details, fuzzy_search_addresses.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 41/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | PERMISAPI_KEY |
| Verified owner |
Tools & capabilities
Attom tools
No tool names declared yet. Check the project README from the listing page.
Permisapi MCP tools 18
search_permitsFreeget_permit_detailsFreefuzzy_search_addressesFreefind_dvf_neighborsProget_mdb_scoreProget_score_explanationProget_plu_zoningProget_risksProget_parcelle_geometryProget_existing_buildingsProget_parcelle_by_idProget_neighbor_parcelsPro- +6 more on the listing page
Ready-to-paste client configs
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.
Attom
{
"mcpServers": {
"attom": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-attom"
]
}
}
}
Permisapi MCP
{
"mcpServers": {
"evan-crx-permisapi-mcp": {
"command": "uvx",
"args": [
"--python",
"3.11",
"permisapi-mcp"
],
"env": {
"PERMISAPI_KEY": "YOUR_PERMISAPI_KEY_HERE"
}
}
}
}
Frequently asked questions
Attom is categorized under Real Estate and uses a local stdio subprocess. Permisapi MCP belongs to Real Estate and uses a local stdio subprocess. Pick Attom 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.
Attom has no declared pricing — check the project's own site. 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 attom and evan-crx-permisapi-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Attom has a quality signal of 41/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.