Skip to main content
Glama
geovicco-dev

bhoonidhi-mcp

by geovicco-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to bhoonidhi-mcp

No user-submitted related servers found.

    Related Servers

    • CMR Model Context Protocol by podaac

      CMR Model Context Protocolofficial

      podaac
      F
      license
      B
      quality
      D
      maintenance
      An MCP server that integrates AI retrievals with NASA's Common Metadata Repository (CMR), allowing users to search NASA's catalog of Earth science datasets through natural language queries.
      1
      4
      -

    • EO-MCP

      ShafHaider007
      F
      license
      B
      quality
      B
      maintenance
      A Python MCP server for discovering and analyzing Sentinel-2 L2A imagery, enabling AI agents to search scenes, check quality, and compute spectral indices like NDVI, NDWI, and NBR from remote COG windows.
      4
      -

    • MCP Data Server

      boettiger-lab
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that connects AI agents to cloud-native geospatial data via STAC metadata and DuckDB with H3 spatial indexing, enabling zero-configuration SQL queries on terabyte-scale datasets over S3.
      23
      BSD 3-Clause

    • geopera-mcp

      geo-pera
      A
      license
      C
      quality
      D
      maintenance
      MCP server for the Geopera geospatial data platform that enables AI agents to discover imagery, place and manage orders, and run analytics using the same API as other Geopera clients.
      100
      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 15 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: search is separated from preview, save, download, and cart operations, and download_status vs download_wait are clearly one-off vs watcher. Even where arguments overlap, the descriptions draw explicit boundaries.

    Naming Consistency3/5

    Most query tools follow verb_noun (remove_query, search_scenes, list_queries), but cart_* uses noun-verb order (cart_add, cart_list) and auth_status/download_status/download_wait are noun-phrase style. Everything is snake_case and readable, but the naming pattern is mixed rather than uniform.

    Tool Count5/5

    15 tools is within the ideal range, and each tool covers a distinct stage of the archive-to-download/cart workflow. There is no apparent redundancy or padding.

    Completeness4/5

    The set covers discovery, geocoding, search, dry-run preview, saved-query lifecycle, auth status, download execution/monitoring, and cart management. Minor gaps like no in-server edit of saved queries, no active-download listing, and no direct archival request action are workarounds via the portal or CLI.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources