Skip to main content
Glama
Sign In
NASA PDS Registry MCP Server

NASA PDS Registry MCP Server

Official
by NASA-PDS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to NASA PDS Registry MCP Server

No user-submitted related servers found.

    Related Servers

    • Cassini Mission Plan MCP

      opagani
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying of the Cassini-Huygens mission dataset with tools for listing, searching, counting, aggregating, and browsing activities.
      MIT

    • mcp-exoplanet-archive

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying NASA Exoplanet Archive data using ADQL TAP, planet search, composite parameters, Kepler candidates, and microlensing events.
      483 npm
      MIT

    • NASA MCP Server

      adithya1012
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to NASA's public APIs including Astronomy Picture of the Day, Mars Rover Images, and Near Earth Objects data, enabling users to query and retrieve space-related information through natural language.
      5
      MIT

    • NASA MCP Server

      BACH-AI-Tools
      A
      license
      B
      quality
      D
      maintenance
      Provides standardized access to 20+ NASA data sources including astronomy pictures, Mars rover photos, near-Earth objects, satellite imagery, space weather, and planetary data through a unified interface optimized for AI consumption.
      23
      9 npm
      ISC

    • ecosyste.ms Packages MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to fetch open package metadata across 100+ registries and to resolve every registry a given package or repository is published to via package URL or repository URL. Also exposes the supported registry catalog with ecosystem and package counts, keylessly over MCP or plain HTTP.
      496 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

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    The four search_* tools map cleanly onto distinct PDS Context product types (Investigations, Targets, Instrument Hosts, Instruments), and descriptions reinforce the boundaries. crawl_context_product, search_collections, and get_product each target clearly different operations, leaving little room for misselection.

    Naming Consistency5/5

    All tool names follow a predictable verb_noun snake_case pattern (search_investigations, crawl_context_product, get_product). The search_ prefix is used consistently for the five query tools, and the verb choices accurately reflect each operation.

    Tool Count5/5

    Seven tools is well-scoped for a specialized registry query server, with each tool earning its place by covering a distinct resource or operation. Nothing feels redundant or missing count-wise.

    Completeness4/5

    Core workflows are covered: search across the four context types, search collections, traverse associations, and fetch by URN. Minor gaps exist—no dedicated search_products or bundle search, and the only product retrieval is by exact URN, but agents can largely work around these.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources