PVAToday for AI

The county’s property record, as tools any AI can call.

McCracken County’s record, live from the PVA’s own exports, served over the Model Context Protocol. Ask Claude, or any assistant that speaks MCP, about a parcel, an owner, a street or a sale, and it looks the answer up instead of guessing, and tells you which export it came from.

Connect it Try the chat See the 19 tools

Why it matters

The record was always public. Now it can be asked.

Answers, not search boxes

“Who owns the lots around the park?” used to mean a lookup per parcel. An assistant with these tools finds the park, draws the circle, and reads every parcel in it, in one question.

From the source, with a date on it

Everything comes from the exports the PVA office delivers, and every reply says which one. No scraped copies, no mystery databases, nothing merged in from elsewhere.

History, not just today

Ask how a parcel stood on a past date, walk its transfers back to 1979, or see exactly what changed between two deliveries.

Fairness you can check

Valuation context places an assessment against real nearby sales, and the ratio study measures a whole class the way assessors do. Each sale is compared with the value from before it sold, and the method and the limits are stated every time.

Connect

One public endpoint, streamable HTTP. No account needed to read the public record.

The endpoint

Live

https://mcp.pva.today

Every tool is open to the public. A bearer token issued to a PVA office, or to operations, additionally unlocks looking up everything behind one mailing address, the QA report on its own deliveries and the raw rows as delivered. Nobody else needs one.

In Claude

Open Settings, then Connectors, and choose Add custom connector.
Name it PVA Today and paste the endpoint URL.
Turn it on in a chat and ask about McCracken County.

In Claude Code:

claude mcp add --transport http pva-today https://mcp.pva.today

Any MCP client

Clients that take a JSON config with remote servers:

{
  "mcpServers": {
    "pva-today": { "type": "http", "url": "https://mcp.pva.today" }
  }
}

Clients that only launch local (stdio) servers can bridge to it:

npx mcp-remote https://mcp.pva.today

Or just ask

The public chat at chat.pva.today runs on these same tools. Nothing to install.

Open the chat

The server also carries its own long-form docs as MCP resources: pva://docs/types for the shared shapes and pva://docs/tools/{name} per tool. A good assistant reads them when a question needs the fine print.

Honest by design

Built so an assistant can’t quietly get it wrong.

Every reply is dated

as_of names the export the answer came from: its date, the roll, the drop, and whether the answer is exact or reconstructed. Where it comes from a single delivered file, it carries that file’s hash.

And sourced

provenance names the family each part of the answer came from: the roll, the sales record, the change log, the delivered rows, or the place table.

A miss says why

found: false comes with a code (NOT_FOUND, AMBIGUOUS, INVALID_SCOPE, STALE_AS_OF, FORBIDDEN_SCOPE) and a reason. An ambiguous address returns the candidates. Nothing is filled in with a guess.

Valuation shows its work

How many sales, from when to when, by what method, and what it can’t see: condition, age, location, time. Each sale is measured against the value from before it sold, not the value the PVA reset to the price. A position against comparables, never an appraisal.

Three clocks, kept apart

When the PVA cut the file, which tax roll a value belongs to, and when a sale or a building happened are three different dates. The tools never blur them.

A record, not a mailing list

Public replies carry the record the PVA publishes, the owner’s mailing address included: it is public record, the same as at the office counter. What needs a credential is the rollup: turning one mailing address into every parcel behind it. A single record is an answer; a list keyed off an address is a different thing.

Warnings travel with the answer

Anything the model should say out loud (a truncated list, a filter not applied, a field that isn’t shown to this caller) rides along in warnings.

What every reply looks like

The same envelope from every tool. The reply to get_data_status, trimmed:

{
  "county": "ky/mccracken",
  "as_of": {
    "requested": "latest",
    "served_from": "drop:mccracken-2026-09-23",
    "drop_id": "mccracken-2026-09-23",
    "export_date": "2026-09-23",
    "roll": "2027 working roll",
    "fidelity": "exact"
  },
  "found": true,
  "data": { "export_date": "2026-09-23", "cadence_days": 210, … },
  "provenance": { "parcels": "pva_roll" },
  "warnings": []
}

county: Which county answered (ky/mccracken).
as_of: What was asked for, what served it: drop, export date, roll, fidelity (exact, reconstructed or unknown), and the delivered file and its hash when one file answers.
found: true for an answer. false is a miss, never an error or a guess.
code, reason: On a miss: why, in a word and a sentence.
candidates: On AMBIGUOUS: the parcels it could mean, so the next call can name one.
data: The answer itself.
provenance: Where each family of data came from.
warnings: What the answer should mention.
cursor, truncated: On paged lists: how to get the next page, and whether a limit cut this one.

Shared shapes

Most tools name one parcel (a Locator) or an area (a Scope). The fields sit flat among the tool’s other arguments.

Locator: one parcel

Give exactly one.

Argument	Type	What it does
`parcel_id`	string	A parcel number, in the PVA's form (for example 123-45-67-890).
`address`	string	A street address. A leading house number anchors the match, so 315 BROADWAY never returns 2315 BROADWAY. Several matches come back as AMBIGUOUS with up to five candidates.
`lat + lng`	number	A point; the parcel that contains it.

Scope: an area

Give at most one.

Argument	Type	What it does
`district`	string	A tax district code (02) or a taxing district name.
`street`	string	A street name, e.g. BROADWAY.
`lat + lng + radius_meters`	number	A circle. radius_meters defaults to 500, max 5000.
`west, south, east, north`	number	A bounding box.
`(nothing)`		The whole county.

as_of: a moment

An ISO date or a drop id. On or after the first export held, it resolves to the newest export on or before that date. Before it, values can’t be known and the reply is STALE_AS_OF; ownership before then is in get_timeline’s transfers.

Find a place or a parcel

Start here: turn a name, an address or a point on the map into the county's record.

`resolve_location`

Turns a place, landmark, road or neighborhood name into coordinates, so the area tools have somewhere to look. Fuzzy matching over the county's place table: neighborhoods, roads, schools, parks, landmarks.

Arguments

Argument	Type	What it does
`query`	string, required	A place, landmark, road or neighborhood name.
`category`	string	Filter, e.g. school, park, neighborhood, road.
`limit`	integer	Default 5, max 25.

Returns

Places best first, each with name, coordinates, category and a match score. Use the coordinates as a scope for the area tools.

Ask a chatWhat's near the National Quilt Museum?

`list_places`

New

Every named place in the county, with the parcel each one sits on and its owner of record. The list behind pva.today/mccracken/places.

Access. Open to everyone. Private homes (house, residential, apartment) are never listed, and the owner is a name only, never mailing detail.

Arguments

Argument	Type	What it does
`kinds`	string	places (default) \| all. all adds roads, towers, pipelines, parking and the like, each flagged infrastructure.
`category`	string	Only this category, e.g. park, school.
`query`	string	A name fragment.
`limit`	integer	Default 200, max 1000.
`offset`	integer	Where the page starts: the previous page's next_offset.
`cursor`	string	From the previous page's reply, to get the next page.

Returns

places, each with id, name, category, lat, lng, infrastructure, and parcel (parcel_id, site_address, owner) or null when the place is on no parcel. categories counts each category over the kinds asked for, before the category and query filters. total, returned and next_offset (null on the last page). hidden counts what was left out: infrastructure, and private_homes.

Ask a chatWhat parks are in McCracken, and who owns each?

`search_parcels`

Finds parcels by address fragment or parcel-number prefix, by area, or by filters. Largest first unless you ask for another order.

Arguments

Argument	Type	What it does
`query`	string	Parcel-number prefix or address fragment, at least 2 characters. A leading house number anchors.
`scope`	Scope	At most one of district, street, a circle or a box; nothing means the county. See Shared shapes.
`owner_type`	string	individual \| llc \| trust \| estate \| corporate \| government \| religious
`absentee_only`	boolean	Only parcels whose mailing address differs from the site address.
`record_status`	string	assigned (default) \| unassigned (map-only parcels) \| any
`built_since`	integer	Only parcels with a building built in or after this year.
`sort`	string	size (default, largest first) \| value (highest assessed first) \| distance (the default with lat + lng) \| parcel_id
`detail`	string	summary (default: address and owner per hit) or ids (parcel ids, for a map).
`limit`	integer	Default 20; max 25 at summary, 500 at ids.
`cursor`	string	From the previous page's reply, to get the next page.

Returns

Current records only. Each hit carries acreage, assessed value and class. Paged: cursor for the next page, truncated when a limit cut the list.

Ask a chatWhat are the largest parcels the government owns along the riverfront downtown?

`get_parcel`

One parcel, whole: address, owner, the assessment for the roll in force, deed, last transfer and buildings. Ask for a past date and it answers as the record stood then.

Access. Open to everyone. At full detail the reply includes the owner's mailing address, which is public record; summary leaves it out.

Arguments

Argument	Type	What it does
`locator`	Locator	Exactly one of parcel_id, address, or lat + lng. See Shared shapes.
`detail`	string	summary (default) trims the legal description and mailing detail; full keeps them.
`include_buildings`	boolean	Default true.
`include_geometry`	boolean	Inline GeoJSON. Default false; geom_uri is always present.
`as_of`	string	An ISO date or a drop id: the parcel, owner and assessment as they stood then. Default the latest export. Buildings have no history and are always the latest.

Returns

The parcel record, with the delivered file it came from and that file's hash in as_of.

Ask a chatWho owned the McCracken County Courthouse parcel in February, and what was it assessed at?

`get_buildings`

The buildings on one parcel or across an area: type, year built, size, condition, grade and value.

Arguments

Argument	Type	What it does
`parcel_id / address`	string	One parcel (give one), or leave both out and give a scope.
`scope`	Scope	At most one of district, street, a circle or a box; nothing means the county. See Shared shapes.
`built_since`	integer	Only buildings built in or after this year.
`limit`	integer	Default 50, max 200.
`cursor`	string	From the previous page's reply, to get the next page.

Returns

Buildings newest first. They come from the improvements file and have no history.

Ask a chatWhat's been built within a mile of Kentucky Oaks Mall since 2020?

Back to the tool list

Owners and areas

Who holds what, who's next door, and what an area adds up to.

`get_portfolio`

What an owner holds, by name (or, for signed-in county staff, by mailing address). It can also add what that name bought or sold in the past.

Access. By owner_name, open to everyone. By mailing_address, signed-in county staff only; public callers get FORBIDDEN_SCOPE.

Arguments

Argument	Type	What it does
`owner_name`	string	Owner name or fragment; every word must match at a word boundary.
`mailing_address`	string	Signed-in county staff only; public callers get FORBIDDEN_SCOPE. A mailing address fragment; rolls up every entity at that address. Give this or owner_name.
`include_past`	boolean	Also parcels this name bought or sold, with roles past_buyer and past_seller.
`since`	string	ISO date: acquisitions and dispositions since then, from the sales record.
`limit`	integer	Default 25, max 200.
`as_of`	string	ISO date or drop id.
`cursor`	string	From the previous page's reply, to get the next page.

Returns

Parcels on the latest roll per parcel, with role; with include_past, counts of acquisitions and dispositions. A name search matches the words of the owner's name; the rollup by mailing address is for signed-in county staff only. Either approximates an owner; it does not prove two records are the same owner.

Ask a chatWhat property does the City of Paducah own, and what has it bought since 2024?

`get_neighborhood`

A parcel's neighbors within a radius, with touching parcels and shared ownership flagged.

Arguments

Argument	Type	What it does
`locator`	Locator	Exactly one of parcel_id, address, or lat + lng. See Shared shapes.
`radius_meters`	number	Default 100, max 500.
`neighbor_limit`	integer	Default 8, max 25.
`detail`	string	list (ids and addresses) \| summary (default: adds owner, acreage, latest assessment, last sale) \| full (adds what changed since the last roll).
`as_of`	string	ISO date or drop id; only the anchor parcel honours it.

Returns

The anchor parcel plus neighbors, touching ones first, then by distance; neighbors with the same mailing address are flagged (the flag, never the address). With full, counts of change kinds across the anchor and its neighbors in the latest export.

Ask a chatWho owns the parcels that touch Noble Park?

`get_area_summary`

An area, added up: parcel count, acreage, total assessed value, distinct owners, and breakdowns by property class and owner type.

Arguments

Argument	Type	What it does
`scope`	Scope	At most one of district, street, a circle or a box; nothing means the county. See Shared shapes.
`as_of`	string	Accepted, but not yet applied to aggregates; the reply says so.

Returns

Totals for assigned parcels on the latest export (latest roll per parcel), a breakdown by property class with totals, and one by owner entity type.

Ask a chatHow much of tax district 02 is commercial, by assessed value?

Back to the tool list

Sales and history

What sold, what changed, and a parcel's story back to 1979.

`get_timeline`

One parcel's whole story, newest first: every transfer back to 1979, each roll's assessment, buildings by year built, and recorded changes.

Arguments

Argument	Type	What it does
`locator`	Locator	Exactly one of parcel_id, address, or lat + lng. See Shared shapes.
`kinds`	string[]	Subset of transfer, assessment, building, change, drop. Default all.
`since`	string	ISO date. Default no lower bound; the history begins in 1979.
`until`	string	ISO date.
`limit`	integer	Default 40, max 200.
`cursor`	string	From the previous page's reply, to get the next page.

Returns

Counts and span first, then events. Transfers carry parties, price, deed and validity; arms_length is true for validity code Z; gap is set when the seller is not the previous buyer (the PVA's record, not the clerk's index). Assessments carry gross, land, improvements, exemption and year-over-year change, with restated_from when a year was revised after it was first loaded.

Ask a chatWalk me through the ownership history of the old Market House parcel.

`get_sales`

Sales by sale date in an area: price, parties, deed, validity and flags. Default the last 24 months.

Arguments

Argument	Type	What it does
`scope`	Scope	At most one of district, street, a circle or a box; nothing means the county. See Shared shapes.
`since`	string	ISO date. Default 24 months ago.
`until`	string	ISO date.
`arms_length_only`	boolean	Keep only validity code Z (arms-length) sales.
`min_price`	number	Leave out sales below this price.
`limit`	integer	Default 20, max 200.
`cursor`	string	From the previous page's reply, to get the next page.

Returns

Each sale with date, price, buyer, seller, deed, validity code and label, and flags (future_date, junk_price, parcel_not_in_table). Sales on retired parcels are included. median_arms_length is over the page.

Ask a chatWhat sold within half a mile of Paducah Tilghman High School this year?

`get_market_pulse`

An area's market over time: sales per month, quarter or year, arms-length medians, how values moved each roll, and new construction.

Arguments

Argument	Type	What it does
`scope`	Scope	At most one of district, street, a circle or a box; nothing means the county. See Shared shapes.
`from`	string	ISO date. Default 24 months ago.
`to`	string	ISO date. Default today.
`bin`	string	month (default) \| quarter \| year

Returns

Per bin: sales, arms-length sales and the median arms-length price; value movement per roll (count up, count down, net) from the change log; new construction by year built.

Ask a chatHow has the market along Broadway moved over the last two years, by quarter?

`what_changed`

What the PVA's exports changed between two deliveries, in an area: counts by kind first, then the rows, with a materiality filter.

Arguments

Argument	Type	What it does
`scope`	Scope	At most one of district, street, a circle or a box; nothing means the county. See Shared shapes.
`since`	string	Drop id or ISO date. Default the drop before the latest.
`until`	string	Drop id or ISO date. Default the latest.
`kinds`	string[]	Change kinds. Default all but address_edit. Kinds: parcel_added, parcel_retired, parcel_unassigned, parcel_assigned, transfer, account_change, owner_edit, address_edit, value_change, restated_prior_year, class_change, exemption_change, improvement_added, zoning_change.
`min_value_pct`	number	Leave out value changes below this percent. Default 0.
`ownership_only`	boolean	Only transfers, added and retired parcels.
`limit`	integer	Default 20, max 200.
`cursor`	string	From the previous page's reply, to get the next page.

Returns

Counts by kind, then rows with old and new values and detail: the sale behind a transfer, the delta and percent behind a value change.

Ask a chatWhat changed downtown in the latest export? Only value changes over 10%.

Back to the tool list

Value and fairness

How assessments compare with what property sells for, stated with its method and its limits.

Every sale is measured against the value from before it sold

When a parcel sells, the PVA resets its assessed value to the sale price. So most recent sales match their current assessment exactly, and a ratio of today's value to the sale price would measure nothing: it would call every roll perfect.

Both tools measure each sale against the value the parcel carried before the sale: the roll last delivered before the sale date, as it was first delivered. That means only sales after the first roll PVAToday holds (February 2026) can count, and the window of usable sales grows with each roll the office delivers. Early on, samples are small, and the replies say so.

`get_valuation_context`

Updated

A position, not a verdict. Places one parcel's assessment against recent arms-length sales of the same kind of property nearby, and says how it got there.

Arguments

Argument	Type	What it does
`locator`	Locator	Exactly one of parcel_id, address, or lat + lng. See Shared shapes.
`radius_meters`	number	Where the search starts. Default 1000; it widens to at most 3000 until 5 sales are found.
`method`	string	auto (default) \| sales \| per_acre. auto uses farm-parcel comparison for farm class, sales when there are enough, value per acre otherwise; sales returns NOT_FOUND rather than fall back.

Returns

Comparables: arms-length (validity Z) sales of the same property class nearby in the last 24 months, starting 1 km out and widening up to 3 km until 5 are found. Each comparable's ratio is the assessment it carried before it sold (the roll last delivered before the sale date, as first delivered) divided by its sale price. The parcel's own ratio is estimated from its size (living sq ft for homes, building sq ft for commercial, acres for land) times the comparables' median price per unit, then placed against the comparables' middle half (25th to 75th percentile): lower than most, in line, or higher than most. It is judged only with 5 or more sales. Every reply states n, the sale date range, the method and caveats: not an appraisal; not adjusted for condition, age or location; sale prices not time-adjusted. Farm parcels: Kentucky assesses qualifying farmland at agricultural-use value, so the tool compares value per acre with other farm parcels instead of against market sales. Too few sales: it falls back to value per acre among same-class parcels, and says so.

Ask a chatIs the assessment on the Kentucky Oaks Mall in line with what similar commercial property nearby has sold for?

`get_ratio_study`

New

The tool for PVA-level work: an IAAO-style ratio study by property class and area. It judges a roll or a group of properties, not one parcel.

Arguments

Argument	Type	What it does
`scope`	Scope	At most one of district, street, a circle or a box; nothing means the county. See Shared shapes.
`property_class`	string	One class. Default every class in the area.

Returns

Per class: the number of arms-length sales, each measured against the assessment from before it sold (the roll last delivered before the sale date, as first delivered); level (median assessment ÷ sale ratio, IAAO target 0.90 to 1.10); uniformity (COD, coefficient of dispersion; targets 15 or under for residential, 20 for commercial, 25 for land); vertical equity (PRD, price-related differential, target 0.98 to 1.03; above 1.03 means cheaper properties carry a larger share); whether each is within the IAAO range; and the outlier sales at each end. Farm class is left out with a note, since it is assessed at agricultural value. The reply says these are the national IAAO standard, not the Kentucky Department of Revenue's own tolerances.

Ask a chatRun a ratio study for residential property in McCracken County. Is the roll level, and are cheaper homes carrying more than their share?

Back to the tool list

The record and its deliveries

How current the data is, where each fact came from, and what the office sent.

`get_data_status`

Which PVA export the data reflects, and a one-line pulse. A good first call: it tells you how current everything else is.

Arguments

No arguments.

Returns

The export date and roll, the five pipeline stages with times (received, verified, loaded, diffed, published), the export before it, the cadence in days, change counts since the export before, and a pulse line (sales per month, median arms-length price).

Ask a chatHow current is the McCracken County data?

`find_record_origin`

Which export first carried a parcel's current owner, value, deed, address, class, exemption or zoning, with a pointer to the exact delivered row.

Arguments

Argument	Type	What it does
`locator`	Locator	Exactly one of parcel_id, address, or lat + lng. See Shared shapes.
`field`	string	owner \| value \| deed \| address \| class \| exemption \| zoning. Default every field with a recorded change.

Returns

For each field, the most recent recorded change that set the current value: the drop, its export date, and a raw_uri to the delivered row with the file's hash, so the record can be cited to the byte. Unchanged since the first export means the origin is genesis.

Ask a chatWhen did the courthouse parcel's current owner first show up in the PVA's exports?

`get_delivery`

The Register: one delivery (drop) or a window of them, with stages, the files sent and change counts.

Access. Open to everyone. The QA report and notes are shown to the office (its own drops) and ops.

Arguments

Argument	Type	What it does
`drop_id`	string	One drop, e.g. mccracken-2026-09-23.
`delivery_id`	string	One upload's id from the ingestion service.
`date`	string	ISO date: the drop exported or received that day.
`from + to`	string	List drops in the window (export date).
`stage`	string	Only drops that reached this stage: received \| verified \| loaded \| diffed \| published.
`limit`	integer	Default 20, max 100.
`cursor`	string	From the previous page's reply, to get the next page.

Returns

Newest first. Each entry: source, roll, the five stage times, the files sent with hashes, the previous drop, change counts by kind.

Ask a chatList every delivery from the McCracken PVA this year and where each one stands.

`get_delivery_records`

The rows of one delivery: the changes it made, or (for the office and ops) the rows exactly as delivered.

Access. view changes is open. view raw is for the office (its own drops) and ops; anyone else gets FORBIDDEN_SCOPE.

Arguments

Argument	Type	What it does
`drop_id`	string, required	The drop.
`view`	string	changes (default) \| raw (rows as delivered).
`unit`	string	For raw: which file, e.g. tblREProperty.txt.
`kind`	string	For changes: one change kind.
`parcel_id`	string	One parcel's rows (across files, for raw).
`limit`	integer	Default 50, max 500.
`cursor`	string	From the previous page's reply, to get the next page.

Returns

Change rows, or raw rows with fields in delivered order, each with a raw_uri and the file's hash.

Ask a chatShow me every transfer in the September delivery.

`get_anomalies`

What the office should check in a delivery: the things that look wrong, counted, with examples.

Arguments

Argument	Type	What it does
`drop_id`	string	Default the latest drop.
`kind`	string	future_date \| junk_price \| future_building \| undated_building \| big_restatement \| contract_unit_left_out \| retired \| qa. Default all.
`limit`	integer	Examples per kind. Default 5, max 50.

Returns

Counts per kind with examples: future-dated sales (with the years the rest of that deed book carries), prices that look like account numbers, buildings dated after the export or undated, prior-year values restated by 25% or more, contract files left out, parcels gone from both the table and the map, and what verification flagged in the files.

Ask a chatAnything in the latest export the PVA office should double-check?

Back to the tool list