Skip to main content
Glama
nyc-open-data-mcp

nyc-open-data-mcp

by frogr

Related Servers

Alternatives to nyc-open-data-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying NYC Open Data datasets using natural language, with tools to search datasets, run SoQL queries, and retrieve metadata, all without an API key.
      93 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Lets AI assistants discover public Socrata open-data portals, search their datasets, inspect schemas, and run bounded read-only SoQL queries to answer questions with live government data. All access is strictly read-only and results come straight from the publisher's portal.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query U.S. public-health datasets such as disease surveillance, mortality, behavioral risk factors, and flu activity through the Socrata API, using natural language or direct tool calls.
      98 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to query and analyze New York City spending, contracts, budget, payroll, and revenue data through the public Checkbook NYC API using structured search tools.
      12
      343 npm
      3
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to search and browse NYC City Record notices — procurement solicitations, contract awards, public hearings, and agency notices — through NYC Open Data. Provides tools for full-text search, agency and notice-type filtering, open solicitations by deadline, and date-range queries.
      9
      456 npm
      2
      MIT

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    search_datasets (catalog discovery) and query_dataset (SoQL execution) are clearly separated by a documented workflow. However, restaurant_inspections and service_requests_311 overlap with what query_dataset could do against those same datasets, so an agent may wonder when to use the specialized tools versus the generic query tool.

    Naming Consistency3/5

    All names are snake_case, which is good, but conventions are mixed: search_datasets and query_dataset use verb_noun, while restaurant_inspections and service_requests_311 are noun phrases with no verb. Readable but not a predictable pattern.

    Tool Count4/5

    Four tools is on the lean side but each earns its place: one discovery, one general query, and two high-value pre-built domain queries. A reasonable, well-scoped set for the server's purpose.

    Completeness4/5

    search_datasets plus query_dataset give broad coverage of the whole NYC Open Data catalog, and the two specialized tools add convenience aggregations. Minor gaps like dataset metadata/column-listing or write operations exist but read-only SoQL over any dataset covers most needs.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data