ARV Estimator
PYPI · ARV-MCP
Estimate a home's after-repair value from scored, gated sold comps, with the evidence.
Available components
Last scanned (11 hours ago)
Scores higher than 78% of PyPI servers
Category Finance and Payments
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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 39 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mariov7757/arv-mcp). 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 Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1172 tokens (~293/item across 4 items; 3 tools + 1 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 64
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 pypi/arv-mcp@0.2.2
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mariov7757/arv-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mariov7757/arv-mcp/.github/workflows/release.yml@refs/tags/v0.2.2 |
| Rekor log index | 3601777667 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:1a63a8e06c1687cae9331b1054336d766c7666542d16d90a9cbc55c66b80d175 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 39 packages
| Packages resolved | 39 |
|---|---|
| No linked repository | 1 |
| 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 →
get_arv Estimate ARV from sold comps ~752
Estimate a property's value from nearby sold comps and return the evidence. How to use the result: - estimate.arv is TYPICAL value (similarity-weighted median of eligible sold comps' $/sqft x subject sqft). estimate.renovated_range is what the top of the eligible pool supports, i.e. the ARV a flip finished to the top of the neighbourhood could target. Quote both, labelled. If renovated_range is null, say there weren't enough comps to separate renovated sales. - Treat the estimate as one input: check it against the closest, highest- scoring eligible_comps and say whether they agree. Use each comp's `factors` to explain differences (size, age, pool...). - Read `guidance` first and pass its warnings on. In particular: arv_fallback=true means NOT comp-backed; low confidence.tier (1-2) means thin evidence; distressed comps (REO/short sale) pull prices down; a subject_source of "user_supplied" means the facts weren't verified. - market_context is current asking prices, a ceiling check only, never comps. - If subject.address differs from what the user asked (address_fuzzy_match), confirm it's the right property. - For what-ifs ("what if it had a pool / were 1,800 sqft"), call again with that fact overridden; cached data makes repeat calls fast. Errors come back as {"error": {"code", "message", ...}}: - ADDRESS_NOT_VERIFIED: the address was located but no record matches it. Ask the user for the facts in `needs` (and ideally `recommended`), then call again with them. - ADDRESS_NOT_FOUND: ask the user to check the address, or pass latitude and longitude with the facts. - MISSING_FACTS: ask for the listed facts and call again. - UNSUPPORTED_PROPERTY_TYPE (vacant land), NO_COMPS (try a larger radius_mi or days_back), RATE_LIMITED (wait retry_after_s), UPSTREAM_ERROR (data source unavailable): explain to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Full street address, e.g. '1234 E Main St, Mesa, AZ 85204'. Include the unit number for condos/townhomes. |
| baths | – | – | Bathrooms, halves as .5 (override). |
| beds | – | – | Bedrooms (override). |
| days_back | – | – | How far back to look for sales, in days (30-730, default 180). |
| garage | – | – | Garage spaces (override). |
| has_pool | – | – | Private pool (override). |
| include_market_context | boolean | – | Also fetch nearby active/pending listings (two extra requests). |
| latitude | – | – | Only when the address can't be located; pass with longitude. |
| longitude | – | – | Only when the address can't be located; pass with latitude. |
| lot_sqft | – | – | Lot size in sqft (override). |
| max_comps | – | – | How many eligible comps to return (1-25, default 10). |
| property_type | – | – | single_family, condo, townhome, multi_family, mobile, farm or land. Required when the address can't be verified. |
| radius_mi | – | – | Comp search radius in miles (0.25-5, default 1.5). Widen for rural or thin markets. |
| sqft | – | – | Living area sqft. Overrides the record; required when the address can't be verified. |
| stories | – | – | Levels in the unit (override). |
| year_built | – | – | Year built (override). |
Structured output declared, but exposes no named fields.
No examples provided.
get_comp_map Comps map data ~134
Comps-map data for the get_arv map view: the subject and every sold comp and active/pending listing with coordinates and marker/popup HTML. Called by the map itself, not by the model.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| baths | – | – | – |
| beds | – | – | – |
| days_back | – | – | – |
| garage | – | – | – |
| has_pool | – | – | – |
| latitude | – | – | – |
| longitude | – | – | – |
| lot_sqft | – | – | – |
| property_type | – | – | – |
| radius_mi | – | – | – |
| sqft | – | – | – |
| stories | – | – | – |
| year_built | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_property Look up a property's facts ~107
Look up the verified Realtor.com record for an address: size, beds/baths, year built, lot, stories, garage, pool, subdivision, status, list price (when on the market) and last sale. Works for sold, off-market and for-sale homes. Returns ADDRESS_NOT_VERIFIED / ADDRESS_NOT_FOUND errors when no record matches the exact street and unit. Use get_arv for valuations.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Full street address, including any unit number. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the ARV Estimator MCP server?
ARV Estimator runs locally as a PyPI package, launched with uvx arv-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · arv-mcp
claude mcp add mariov7757-arv-mcp -- uvx arv-mcp
What is the ARV Estimator MCP server?
ARV Estimator is an MCP server listed in the public MCP registry as io.github.mariov7757/arv-mcp. Estimate a home's after-repair value from scored, gated sold comps, with the evidence. This page covers its PyPI package (arv-mcp).
Is the ARV Estimator MCP server safe to use?
ARV Estimator scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 ARV Estimator MCP server expose?
ARV Estimator exposes 3 tools: get_arv, get_comp_map, lookup_property. Their descriptions and schemas cost roughly 993 tokens of context every time the server is loaded.
Is the ARV Estimator MCP server still maintained?
ARV Estimator 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 ARV Estimator MCP server under?
ARV Estimator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.