Skip to main content
Glama
beenthatt-rehman

datagovin-mcp

by beenthatt-rehman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to datagovin-mcp

No user-submitted related servers found.

    Related Servers

    • MoSPI MCP Server by nso-india

      MoSPI MCP Serverofficial

      nso-india
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI-ready access to Indian government statistics through MCP, enabling natural language queries for economic, demographic, and social indicators.
      138
      MIT

    • bharatlas-mcp

      urbanmorph
      A
      license
      Not graded
      quality
      A
      maintenance
      Description: Query India's open geo data in natural language. 8 tools: list layers, inspect schemas, filter/group any column, point-in-polygon locate, spatial proximity search, downloads in 5 formats. Covers admin boundaries (state to village), city wards, forests, rivers, dams, hospitals, highways, airports, and more.
      39
      MIT

    • Datos.gob.es-MCP

      AnCode666
      A
      license
      A
      quality
      C
      maintenance
      Enables querying and analyzing over 90,000 public datasets from the Spanish Government Open Data Portal (datos.gob.es) using natural language, with tools for search, filtering, metadata access, and SPARQL queries.
      10
      5
      MIT

    • dados-pt

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Portugal's national open data portal (dados.gov.pt) through natural language.
      6 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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct responsibility: discover datasets (search_datasets), browse categories (list_sectors), inspect schema (get_dataset_info), and retrieve rows (query_dataset). No two tools could be confused for the same action.

    Naming Consistency5/5

    All four tool names follow a uniform verb_noun pattern (search_datasets, list_sectors, get_dataset_info, query_dataset). While the verbs differ, each one accurately maps to its unique action, and the snake_case style is consistent throughout.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped to the core use case of discovering and retrieving Indian open government data. Each tool is necessary and none feel redundant, making the tool count highly appropriate.

    Completeness4/5

    The tool surface covers the end-to-end read-only workflow: search, sector overview, schema inspection, and data extraction with pagination. Minor gaps include no direct way to list every dataset in the catalog and limited dataset metadata (e.g., update date), but agents can work around these via search and get_dataset_info.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources