Overassessed

What it can reach

From its install config and its own description; a sandbox run will confirm this later.

Checks on v1.0.0

1. Real tool

   passrules 2026-09-29.1 · 5 hours ago

2. Static scan

   passrules 2026-09-29.1 · 5 hours ago

3. Claims check

   skippedrules 2026-09-29.1 · 5 hours ago
   • infoLLM claims check is not configured on this deploy.

Install

Each app still asks you to confirm. Everything is pinned to the version checked above.

{
  "servers": {
    "overassessed": {
      "type": "http",
      "url": "https://overassessed.agentlookups.ai/mcp"
    }
  }
}

Tools it offers

As the server describes them. This text comes from the publisher and is shown as-is.

• check_assessment

  Fairness check for one Maryland property assessment against genuinely similar homes (same triennial reassessment group, similar size, lot and age, same zip), from a copy of the state's own assessment roll (SDAT) refreshed monthly. Input is a street address plus zip, or an SDAT account id (acct). A single match returns the parcel record, a uniformity object, a plain-language verdict, Maryland's appeal windows with official filing links, and honesty notes. The uniformity object gives BandSize (how many similar homes), where the assessment sits among them as percentiles (PctFMV for market value, PctImprPSF for improvement value per square foot, PctLand for land value), their medians (MedianFMV, MedianImprPSF, MedianLand), the median sales ratio of assessment to sale price (MedianSalesRatio) and its coefficient of dispersion (COD) over RatioSales sales dated RatioFromYear through RatioToYear (three calendar years ending with the year of the roll's newest sale dated on or before today), and Branch. Verdict branches: fair means the assessment is in the normal range for similar homes; review means it is on the high side; elevated means it is higher than almost all of them; insufficient means fewer than 25 similar homes exist for a fair comparison, which is no finding either way. On the insufficient branch the percentile and median fields are 0, meaning not computed. A single-match or multiple_matches result also carries a roll object: as_of is the date the state last updated the roll and pulled is the date this copy was taken (both YYYY-MM-DD), overdue is true when this copy is more than 35 days old, and a field the server does not know is left out. MedianSalesRatio and COD are 0 when RatioSales is below 10, meaning no ratio is published. When several parcels share the address, the result is multiple_matches, listing parcels with their account ids; passing one of those ids as acct selects that parcel. When more than 10 parcels share an address (a condominium building, for instance), the list holds 10 of them, with no unit numbers and no total count, and a zip does not narrow it further; the official SDAT record has a record for every unit. When nothing matches, the result carries an error field; the roll writes addresses in its own form (e.g. 1 STATE CIR), so a miss can mean a different spelling, or a zip other than the one the roll records, rather than a missing parcel. A zip is 5 digits; a ZIP+4 (21202-1234) is read as its first five digits. A malformed zip or acct returns an error field naming the expected form, a zip outside Maryland returns an error field stating that only Maryland is covered, and an acct the roll does not hold returns an error field stating that no parcel has that account id. The check is a fairness snapshot of the public record, not an appraisal, and not legal advice; the official SDAT record is authoritative.