Skip to main content
Glama
jdzhrch

OpenCivicQuery

by jdzhrch

Related Servers

Alternatives to OpenCivicQuery

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that puts open data on tap, enabling LLM clients to search, inspect, and query 30,000+ civic datasets from Socrata portals with built-in guardrails like row caps and actionable error messages.
      4
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives LLM agents typed, cached access to civic open-data portals via Socrata (SODA 2.1 + Discovery API), enabling search, query, profiling, sampling, and CSV export of datasets.
      6
      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
      A
      quality
      D
      maintenance
      An MCP server that gives Claude deep access to US public data -- demographics, economics, crime, employment, weather, housing, transit, schools, budgets, and more across 30+ cities for government intelligence workflows.
      28
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query NYC public records through a hosted MCP server, supporting civic workflows such as property research, business evaluation, public money tracking, and influence mapping.
      9 npm
      MIT

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct role across the lifecycle: discovering packs/datasets, inspecting schema, running queries, and reading or pinning snapshots. The pair pin_snapshot and get_snapshot is clearly separated by write/preserve versus read/verify semantics. Search and listing tools are differentiated by catalog search versus documented source packs.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_source_packs, search_datasets, describe_dataset, query_dataset, pin_snapshot, get_snapshot). The convention is predictable throughout.

    Tool Count5/5

    Six tools is well scoped for a civic data query server, covering discovery, schema inspection, querying, and evidence snapshots without unnecessary surface area. Each tool clearly earns its place.

    Completeness4/5

    The surface covers the core workflow from dataset discovery through schema inspection, query execution, and snapshot verification/pinning. Minor gaps exist around managing pinned snapshots, such as listing or unpinning them, but these do not block the primary use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues