Skip to content
All data sources

Data.gov Catalog Discovery API and MCP server

API keydatagov-catalog

Bounded metadata-only search across the federal Data.gov catalog.

Data.gov Catalog Discovery is published by Data.gov Catalog API v4 search and covers United States federal catalog and participating non-federal publishers.

It refreshes on a schedule the publisher sets.

Last verified . That is when these facts were last rebuilt from the ParcelOps source registry, not when Data.gov Catalog API v4 search last refreshed the data itself.

API access

Your AI client reaches Data.gov Catalog Discovery through one ParcelOps MCP endpoint, so there is no separate key to hold for it and no per-source client to write. Reaching it takes your own credentials (API key).

Where it came from

Freshness and coverage

FreshnessScheduled · Catalog freshness follows publisher metadata synchronization.
Places coveredUnited States federal catalog and participating non-federal publishers
Time coveredNot declared
CredentialsCredentials required (API key)

What this source cannot tell you

  • Anything outside United States federal catalog and participating non-federal publishers. A request past that edge comes back empty rather than approximated.
  • Which years it spans, because the covered period is not declared.
  • Anything Data.gov Catalog API v4 search does not publish. ParcelOps returns this source as it stands and never fills a blank field from a different one.
  • Search results are catalog metadata, not the underlying datasets.
  • Distribution and landing-page URLs are never dereferenced by this connector.
  • Per-dataset Access & Use Information controls; non-federal records may have different terms.
  • The live v4 route is absent from GSA’s current published OpenAPI, so only verified q + limit first-page search is exposed.

Methods (2)

A method is one call your agent can make against this source.

  • searchCatalog

    read

    Search Data.gov catalog metadata by a bounded phrase.

    What you must provideq
    Records returneddataset-catalog-record
    How to get more resultsnone
    FreshnessScheduled (source-level)
    Input schema
    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "minLength": 2,
          "maxLength": 300
        },
        "limit": {
          "type": "integer",
          "minimum": 1,
          "maximum": 20
        }
      },
      "required": [
        "q"
      ],
      "additionalProperties": false
    }
    • The opaque next cursor is returned for evidence but replay is not exposed until GSA documents or verifies its contract.
  • getServiceInfo

    read

    Return verified inputs, auth, discovery-only scope, rate evidence, and unverified capabilities.

    FreshnessScheduled (source-level)
    Input schema
    {
      "type": "object",
      "properties": {},
      "required": [],
      "additionalProperties": false
    }

Where this source is used

  • Land research

    Parcel records, ground conditions, and what reaches the property line, for raw and rural land.

  • Data center siting

    Power, water, transport, airspace, and hazard screening for a site before anyone signs anything.

  • Commercial real estate

    Parcel and assessment records, building programs, and the entity on the other side of the deal.

  • Residential real estate

    The parcel record, the housing programs that touch an address, and the conditions a buyer asks about.

  • Real estate law

    Federal rule text, rulemaking dockets, party records, and the property facts a filing has to state.

  • Realtors and brokerages

    The facts behind a listing, the programs a buyer may qualify for, and your own files in the same place.