Attom
NPM · @PIPEWORX/MCP-ATTOM · 2 COMPONENTS
ATTOM MCP — Premium real estate data from ATTOM Data Solutions
Available components
Last scanned (9 hours ago)
Scores higher than 76% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-attom). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1410 tokens (~176/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-attom@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-attom |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-attom/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3601335744 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:be93f213a2f5b49c0df365b6fa879ff2717116ab88e65945fe6b48bb7c14cf736537d3b4938896ceacfddd950c98b7fa6cd5681012e2035153c0991c3 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attom_assessment ~138
"Property tax / taxes on [address]" / "assessed value of [house]" / "tax bill for [property]" / "what does the county say [home] is worth" — county tax-assessor record for a US property. Returns assessed value, market value, tax amount, tax year, and historical trends from public assessor data via ATTOM.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | ATTOM API key |
| address1 | string | yes | Street address (e.g., "123 Main St") |
| address2 | string | yes | City, state ZIP (e.g., "Denver, CO 80202") |
No output schema declared.
No examples provided.
attom_avm ~152
"What's [house] worth" / "home value of [address]" / "Zestimate alternative" / "estimated value of [property]" / "how much is [home] valued at" — automated valuation model (AVM) for any US residential property. Returns ATTOM's estimated market value, confidence score, and low/high range. Use for instant home-price questions; pair with attom_sales_history for recent comparable sales.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | ATTOM API key |
| address1 | string | yes | Street address (e.g., "123 Main St") |
| address2 | string | yes | City, state ZIP (e.g., "Denver, CO 80202") |
No output schema declared.
No examples provided.
attom_property_detail ~160
"Property details for [address]" / "specs of [house]" / "how many bedrooms / bathrooms" / "year built" / "square footage" / "lot size" — full property characteristics for a US residential or commercial address. Returns lot size, square footage, bedrooms, bathrooms, year built, construction type, and heating/cooling systems from ATTOM Data Solutions (the premium US real estate dataset). Use whenever an agent needs structured property attributes by address.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | ATTOM API key |
| address1 | string | yes | Street address (e.g., "123 Main St") |
| address2 | string | yes | City, state ZIP (e.g., "Denver, CO 80202") |
No output schema declared.
No examples provided.
attom_property_search ~290
"Find houses / homes / properties / real estate for sale or owned in [ZIP]" / "search properties near [coords]" / "homes in [neighborhood]" — search US residential and commercial properties by ZIP or lat/lng radius with filters (beds, baths, year built, property type). Returns matching addresses and ATTOM property IDs. Use first when you need to find candidate addresses, then call attom_property_detail / attom_avm / attom_sales_history on the picks.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | ATTOM API key |
| latitude | string | – | Latitude for radius search (use with longitude and radius) |
| longitude | string | – | Longitude for radius search (use with latitude and radius) |
| maxBathsTotal | string | – | Maximum total bathrooms |
| maxBeds | string | – | Maximum number of bedrooms |
| maxYearBuilt | string | – | Maximum year built |
| minBathsTotal | string | – | Minimum total bathrooms |
| minBeds | string | – | Minimum number of bedrooms |
| minYearBuilt | string | – | Minimum year built |
| postalCode | string | – | ZIP/postal code to search in |
| propertyType | string | – | Property type filter (e.g., "SFR", "CONDO", "APARTMENT") |
| radius | string | – | Search radius in miles (use with latitude/longitude) |
No output schema declared.
No examples provided.
attom_rental_avm ~138
"How much can I rent [house] for" / "estimated rent for [address]" / "rental income on [property]" / "rental yield of [home]" — rental AVM for a US residential property. Returns estimated monthly rent, rental yield percentage, and rental value range. Use for landlord / investor / cash-flow analysis questions.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | ATTOM API key |
| address1 | string | yes | Street address (e.g., "123 Main St") |
| address2 | string | yes | City, state ZIP (e.g., "Denver, CO 80202") |
No output schema declared.
No examples provided.
attom_sales_history ~136
"When was [house] last sold" / "sale history of [property]" / "previous owners of [address]" / "what did [house] sell for last time" — complete sales/transaction history for a US property by address. Returns sale dates, prices, deed types, and buyer/seller details from public deed records via ATTOM.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | ATTOM API key |
| address1 | string | yes | Street address (e.g., "123 Main St") |
| address2 | string | yes | City, state ZIP (e.g., "Denver, CO 80202") |
No output schema declared.
No examples provided.
attom_sales_trend ~198
"Housing market trends in [ZIP]" / "median home price in [area]" / "is [ZIP] heating up or cooling" / "sales volume in [neighborhood]" — aggregated real estate market trends by ZIP. Returns average/median sale price, sales volume, and price changes monthly / quarterly / yearly across a date range. Use for market-direction questions before pulling individual addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | ATTOM API key |
| endYear | string | yes | End year (e.g., "2024") |
| geoid | string | yes | A 5-digit ZIP code ("33158"). ATTOM's own "ZI"-prefixed form ("ZI33158") is also accepted; a bare ZIP is prefixed for you. |
| interval | string | yes | Time interval: monthly, quarterly, or yearly |
| startYear | string | yes | Start year (e.g., "2020") |
No output schema declared.
No examples provided.
attom_school_search ~146
"Schools near [address]" / "what school district is [house] in" / "best schools in [area]" / "public schools around [coords]" — find K-12 schools near a US location by lat/lng radius. Returns school name, type (public/private), grade levels, distance, and performance rankings. Use for relocation / family-housing questions paired with property search.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | ATTOM API key |
| latitude | string | yes | Latitude of the search center |
| longitude | string | yes | Longitude of the search center |
| radius | string | – | Search radius in miles (default 5, max 20) |
No output schema declared.
No examples provided.
How do I install the Attom MCP server?
Attom runs locally as an npm package, launched with npx -y @pipeworx/mcp-attom. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-attom
claude mcp add pipeworx-io-attom -- npx -y @pipeworx/mcp-attom
What is the Attom MCP server?
Attom is an MCP server listed in the public MCP registry as io.github.pipeworx-io/attom. ATTOM MCP, Premium real estate data from ATTOM Data Solutions. This page covers its npm package (@pipeworx/mcp-attom).
Is the Attom MCP server safe to use?
Attom scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Attom MCP server expose?
Attom exposes 8 tools: attom_property_detail, attom_property_search, attom_sales_history, attom_avm, attom_assessment, and 3 more. Their descriptions and schemas cost roughly 1,358 tokens of context every time the server is loaded.
Is the Attom MCP server still maintained?
Attom is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Attom MCP server under?
Attom declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.