gov-data-mcp 1.2.2 → 1.2.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gov-data-mcp",
-  "version": "1.2.2",
+  "version": "1.2.4",
   "mcpName": "io.github.malonestar/gov-data-mcp",
   "description": "MCP server exposing published US government open-data tools (EPA, FEMA, USGS, NOAA, FAA, USACE, FDIC, HUD, state licensing boards) as agent-callable tools, backed by Apify Actors.",
   "type": "module",

package/src/catalog.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-10-06T01:56:23.587Z",
+  "generatedAt": "2026-10-06T21:44:58.060Z",
   "owner": "malonestar",
   "count": 122,
   "actors": [
@@ -36,11 +36,22 @@
         "properties": {
           "county": {
             "type": "string",
-            "description": "Which assessor/parcel roll to build leads from. cook-il = Cook County IL (Chicago area, full mailing-address mismatch classification). philadelphia-pa = Philadelphia OPA (full classification). nyc = NYC PLUTO (owner names only — no mailing address in the source, so rows are corporate/LLC-owner flag lists with absentee_tier=unknown). Example: \"cook-il\".",
+            "description": "Which assessor/parcel roll to build leads from. cook-il = Cook County IL (Chicago area, full mailing-address mismatch classification). philadelphia-pa = Philadelphia OPA (full classification). nyc = NYC PLUTO (owner names only — no mailing address in the source, so rows are corporate/LLC-owner flag lists with absentee_tier=unknown). Added 2026-10: maricopa-az, harris-tx, cuyahoga-oh, davidson-tn and dc (county rolls) and nc-statewide, ny-statewide, co-statewide, ma-statewide, ct-statewide, vt-statewide (statewide rolls; use countyName to scope nc/ny/co to one county). Every added roll publishes both an owner mailing address and a situs address; Wisconsin, Minnesota and Arkansas are deliberately not offered (their mailing state cannot be read reliably). Example: \"cook-il\".",
             "enum": [
               "cook-il",
               "philadelphia-pa",
-              "nyc"
+              "nyc",
+              "maricopa-az",
+              "harris-tx",
+              "cuyahoga-oh",
+              "davidson-tn",
+              "dc",
+              "nc-statewide",
+              "ny-statewide",
+              "co-statewide",
+              "ma-statewide",
+              "ct-statewide",
+              "vt-statewide"
             ]
           },
           "absenteeTier": {
@@ -60,13 +71,17 @@
           },
           "propertyClassPrefix": {
             "type": "string",
-            "description": "Filter by the source's property-class code prefix. cook-il: Cook Assessor major class, e.g. \"2\" = residential, \"3\" = multi-family, \"5\" = commercial/industrial. nyc: PLUTO building class, e.g. \"A\" = one-family, \"C\" = walk-up apartments. philadelphia-pa: OPA category_code, e.g. \"1\" = single family (applied client-side). Leave empty for all classes. Example: \"2\"."
+            "description": "Filter by the source's property-class code prefix. cook-il: Cook Assessor major class, e.g. \"2\" = residential, \"3\" = multi-family, \"5\" = commercial/industrial. nyc: PLUTO building class, e.g. \"A\" = one-family, \"C\" = walk-up apartments. philadelphia-pa: OPA category_code, e.g. \"1\" = single family (applied client-side). Leave empty for all classes. Added rolls: the roll's own land-use / property-class code (e.g. Harris \"A1\", NY State \"210\", Massachusetts \"101\"), matched server-side as a prefix. Example: \"2\"."
           },
           "minAssessedValue": {
             "type": "integer",
-            "description": "Keep only parcels at or above this value. Uses market_value for philadelphia-pa and assesstot for nyc. The Cook County Parcel Universe dataset carries no assessed-value column, so this filter is ignored for cook-il (a warning is logged).",
+            "description": "Keep only parcels at or above this value. Uses market_value for philadelphia-pa and assesstot for nyc. The Cook County Parcel Universe dataset carries no assessed-value column, so this filter is ignored for cook-il (a warning is logged). Added rolls: each roll's own value column (Maricopa full cash value, HCAD market value, Cuyahoga market value, Nashville appraisal, DC assessment, NC parcel value, NY full market value, Colorado appraised value, MA/CT/VT assessed or listed value).",
             "minimum": 0
           },
+          "countyName": {
+            "type": "string",
+            "description": "Optional. For nc-statewide, ny-statewide and co-statewide: keep only one county, e.g. \"Mecklenburg\", \"Erie\", \"St Lawrence\" or \"Denver\". Checked against the counties the roll actually covers; an unknown or excluded county fails the run with the covered list (nothing billed). Ignored for the county rolls."
+          },
           "maxResults": {
             "type": "integer",
             "description": "Maximum number of lead rows to emit (caps your cost — you are billed per result row). Hard cap 10,000 per run. Example: 100.",
@@ -1335,7 +1350,7 @@
           },
           "maxResults": {
             "type": "integer",
-            "description": "Maximum number of license records to return per city (the actor paginates to reach this). Example: 50. Applied by default if omitted: 1000.",
+            "description": "Maximum number of rows for the WHOLE run, across all selected cities (each row is one billed result). Divided fairly between cities: a city with fewer matching licences than its share hands the rest to the others, and every city gets at least one row (a city that answers with nothing still emits one status row). Until build 1.1.7 this was a per-city cap, so an empty call across all 5 cities emitted 4,001 rows. Must be at least the number of cities selected. Example: 50. Applied by default if omitted: 1000.",
             "minimum": 1,
             "maximum": 50000
           },
@@ -5098,7 +5113,7 @@
           },
           "state": {
             "type": "string",
-            "description": "REQUIRED. Full state name exactly as HRSA stores it, e.g. \"Alabama\", \"California\", \"Texas\". There is no default and no \"all states\" mode: a nationwide HPSA/MUA pull is tens of thousands of designations, so the state must be named explicitly. Run one state per run and combine the datasets. Example: \"Alabama\"."
+            "description": "REQUIRED. A US state, DC or territory, as HRSA's full name (\"Texas\", \"District of Columbia\", \"U.S. Virgin Islands\") or a 2-letter USPS code (\"TX\", \"DC\", \"VI\"); case-insensitive. Codes are converted to HRSA's spelling before the query. A value that names no HRSA state or territory FAILS the run without billing rather than returning a confident empty (until build 1.1.9 \"TX\" matched nothing and SUCCEEDED with 0 rows). There is no default and no \"all states\" mode: a nationwide HPSA/MUA pull is tens of thousands of designations, so run one state per run and combine the datasets. Example: \"Alabama\"."
           },
           "minScore": {
             "type": "integer",
@@ -5179,7 +5194,7 @@
         "properties": {
           "states": {
             "type": "array",
-            "description": "2-letter USPS state codes to search (e.g. CO, TX, NY). Applied to every selected program layer. Defaults to [\"CO\"] if empty. Example: [\"CO\"].",
+            "description": "REQUIRED. The state(s) to search, as 2-letter USPS codes (e.g. [\"TX\"], [\"CO\",\"UT\"]) or full state names; DC and PR/VI/GU/AS/MP are accepted. Applied to every selected program layer. There is no default state and no nationwide mode: until build 1.1.5 an omitted or unrecognised value silently searched Colorado. An unrecognised entry now FAILS the run without billing. Example: [\"CO\"].",
             "items": {
               "type": "string"
             }
@@ -5224,7 +5239,10 @@
             "minimum": 1,
             "maximum": 25000
           }
-        }
+        },
+        "required": [
+          "states"
+        ]
       }
     },
     {
@@ -5808,7 +5826,8 @@
                 "MI",
                 "TN-NASHVILLE",
                 "KY-LOUISVILLE",
-                "AZ-PHOENIX"
+                "AZ-PHOENIX",
+                "ID"
               ],
               "enumTitles": [
                 "Texas (TABC)",
@@ -5824,7 +5843,8 @@
                 "Michigan (MLCC)",
                 "Nashville, TN (Metro Beer Permit Board)",
                 "Louisville, KY (Jefferson County ABC)",
-                "Phoenix, AZ (City Clerk new applications)"
+                "Phoenix, AZ (City Clerk new applications)",
+                "Idaho (ISP ABC)"
               ]
             }
           },
@@ -7658,7 +7678,7 @@
         "properties": {
           "states": {
             "type": "array",
-            "description": "REQUIRED. US states to pull (two-letter codes; full names also accepted). Supported: TX (daily new applications, new licensees, roster, delta), FL (new licensees, weekly roster, delta), CT (new licensees, roster, delta with broker affiliation), CO (new licensees, roster, delta), DE (new licensees, roster, delta), NY (active roster + broker-change delta; NY publishes no issue date). Several states can be combined; maxResults is split across them. Example: [\"TX\"].",
+            "description": "REQUIRED. US states to pull (two-letter codes; full names also accepted). Supported: TX (daily new applications, new licensees, roster, delta), FL (new licensees, weekly roster, delta), CT (new licensees, roster, delta with broker affiliation), CO (new licensees, roster, delta), DE (new licensees, roster, delta), NY (active roster + broker-change delta; NY publishes no issue date). Several states can be combined; maxResults is split across them. Example: [\"TX\",\"CO\"].",
             "items": {
               "type": "string"
             }
@@ -7681,7 +7701,7 @@
           },
           "maxResults": {
             "type": "integer",
-            "description": "Maximum number of records to push to the dataset (billing is per result). When several states are requested the cap is split across them, and budget an earlier state does not use passes to the next. Example: 200.",
+            "description": "Maximum number of records to push to the dataset (billing is per result). When several states are requested the cap is split across them, and budget an earlier state does not use passes to the next. Example: 80. Applied by default if omitted: 200.",
             "minimum": 1,
             "maximum": 50000
           },
@@ -8336,7 +8356,7 @@
         "properties": {
           "mode": {
             "type": "string",
-            "description": "openings = ONE row per business that just opened, resolved across every register the state publishes (TX: SOS charter via the franchise-tax roster + sales-tax permit with first-sales date; other states: the SOS registry) with opened_evidence and a three-valued opened_confidence. search = look up companies by name. new_businesses = raw recently formed entities, one row per registry record. Example: \"openings\". Applied by default if omitted: \"search\".",
+            "description": "openings = ONE row per business that just opened, resolved across every register the state publishes (TX: SOS charter via the franchise-tax roster + sales-tax permit with first-sales date; other states: the SOS registry) with opened_evidence and a three-valued opened_confidence. search = look up companies by name. new_businesses = raw recently formed entities, one row per registry record. If mode is omitted (an API or MCP call) the default is search, which with the default query \"LLC\" is a name search for LLC -- NOT openings (openings is only the Console prefill). Pass mode explicitly. Example: \"openings\". Applied by default if omitted: \"search\".",
             "enum": [
               "openings",
               "search",
@@ -9687,7 +9707,7 @@
           },
           "mode": {
             "type": "string",
-            "description": "snapshot = emit the current normalized WARN notices. delta = compare against a prior snapshot and emit only change rows (new / updated / removed). Delta needs priorItems or priorKvKey. Applied by default if omitted: \"snapshot\".",
+            "description": "snapshot = emit the current normalized WARN notices. delta = compare against a prior snapshot and emit only change rows (new / updated / removed). The prior snapshot comes from priorItems, or from the named store under priorKvKey (default key \"default\" when neither is given), so a scheduled delta needs no extra input. Applied by default if omitted: \"snapshot\".",
             "enum": [
               "snapshot",
               "delta"