Skip to main content
Glama
alexandre-do

vancouver-city-opendata-mcp

by alexandre-do
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to vancouver-city-opendata-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-data-va

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and querying Virginia Open Data (datahub.va.gov) via the Socrata API, providing tools to search datasets, run SoQL queries, and retrieve metadata.
      242 npm
      MIT

    • data-sonoma

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching, querying, and retrieving metadata from Sonoma County Open Data datasets via Socrata SoQL or natural language.
      258 npm
      MIT
    • data-winnipeg by pipeworx-io

      data-winnipegofficial

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and querying Winnipeg Open Data datasets through natural language or SoQL, with tools for datasets, metadata, and row-level data.
      247 npm
      MIT

    • mcp-data-providence

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying and searching the Providence Open Data catalog via Socrata SoQL, including dataset search, data querying, and metadata retrieval.
      263 npm
      MIT

    • MCP Data Vermont

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching, querying, and retrieving metadata from Vermont Open Data (data.vermont.gov) datasets using Socrata SoQL, all via natural language.
      264 npm
      MIT

    • data-calgary

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying Calgary open data from data.calgary.ca using the Socrata SODA API through natural language questions or direct tool calls.
      379 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct stage of the open-data workflow: catalog search, metadata/schema retrieval, record querying, facet discovery, and dataset export. Even though query_records and export_dataset both return rows, their intended use cases are clear and non-conflicting.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: search_datasets, get_dataset, query_records, get_facets, export_dataset. The pattern is predictable and makes it easy to infer tool behavior from the name alone.

    Tool Count5/5

    Five tools is well-scoped for an open-data portal MCP server. Each tool earns its place by covering a necessary part of the exploration-and-extraction workflow without unnecessary redundancy.

    Completeness5/5

    The server covers the full read-only lifecycle for open data: discover datasets, inspect schema, explore facet values, query records, and export in multiple formats. There are no obvious dead ends or missing actions that would prevent an agent from accomplishing the apparent purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources