Attom
Server Details
ATTOM MCP — Premium real estate data from ATTOM Data Solutions
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 43.6% over 39 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-attom
- GitHub Stars
- 0
- Server Listing
- ATTOM
TDQS
Scored across 39 tools
Most tools have distinct purposes, but the ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded trio is genuinely confusing (beta explicitly 'currently matches ask_pipeworx exactly'), and discovery tools (discover_tools vs suggest_questions) plus AI-visibility tools (ai_visibility_check vs scan_competitor_ai_presence) overlap. The five polymarket_* tools have clearer boundaries but still require careful reading.
Consistent snake_case style throughout, but the naming is domain-prefixed inconsistently: some tools carry attom_, pipeworx_, or polymarket_ prefixes while dozens of core meta-tools (recall, remember, forget, subscribe, deep_research, entity_profile, compare_entities) are bare. No single predictable pattern unifies the set, though it remains readable.
39 tools is heavy and exceeds the comfortable range, especially given many are composite meta-tools that fan out internally already. Several (ask_pipeworx_beta, ask_pipeworx_grounded, suggest_questions vs discover_tools) add surface area without clearly earning a distinct slot.
Real-estate capabilities (search, detail, avm, rental_avm, assessment, sales_history, sales_trend, school_search) are fairly comprehensive, and cross-entity/Polymarket coverage is rich. However the surface is a sprawling multi-domain router whose scope wildly exceeds the 'Attom' server name, so coverage is broad but thematically incoherent rather than clearly complete.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
Related MCP Connectors
Property Records MCP — address-level US property records (sales history,
RealEstateAPI MCP — property search, detail, and skip-trace (realestateapi.com)
Xome MCP — US residential foreclosure/REO/short-sale auction calendar and
Altos Research MCP — Real estate market intelligence
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceExposes ATTOM's real estate API as MCP tools, enabling property details, valuations, assessments, sales, and area data via natural language.2-
- AlicenseNot gradedqualityCmaintenanceChains FRED, BLS, ATTOM, and HUD APIs to provide housing intelligence data through a single MCP server.3 npm1MIT
- AlicenseAqualityCmaintenanceMCP server giving agents canonical access to 180M+ US parcels with ownership, valuation, permits, deeds, hazard, and market data.816 npmApache 2.0

mcp-batchdataofficial
AlicenseNot gradedqualityCmaintenanceEnables property-data lookups by address, attribute-based property searches across 155M+ records, and skip-tracing to resolve owner contact information via the BatchData API.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.