---
summary: "socrata_find_datasets now returns datasets behind Discovery domain aliases (#21); an invalid SOCRATA_APP_TOKEN degrades to keyless instead of failing every call (#23)"
breaking: false
security: false
---

# 0.1.14 — 2026-07-10

## Changed

- **`invalid_app_token` error contract** removed from `socrata_find_datasets`, `socrata_get_dataset`, and `socrata_query_dataset` — unreachable now that an invalid token degrades to keyless instead of throwing. ([#23](https://github.com/cyanheads/socrata-mcp-server/issues/23))

## Fixed

- **`socrata_find_datasets`** scoped to a portal whose catalog is indexed under a different Discovery domain (e.g. `data.seattle.gov`, cataloged under `cos-data.seattle.gov`) now returns those datasets, via a static `DISCOVERY_DOMAIN_ALIASES` map comma-joined into the Discovery `domains` filter — the caller's original domain is always retained, never substituted. ([#21](https://github.com/cyanheads/socrata-mcp-server/issues/21))
- **`SOCRATA_APP_TOKEN`** — an invalid or revoked token now degrades to keyless requests with a one-time `WARN` and an immediate retry, instead of failing every subsequent call with a configuration error. ([#23](https://github.com/cyanheads/socrata-mcp-server/issues/23))