Skip to main content
Glama
spedas

spedas-mcp

Official
by spedas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to spedas-mcp

No user-submitted related servers found.

    Related Servers

    • space-mcp-server

      AiAgentKarl
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing AI agents with access to NASA and space/astronomy data including APOD, Mars rover photos, near-Earth asteroids, exoplanets, Earth imagery, natural events, and space weather.
      11
      MIT

    • NASA-MCP

      AnCode666
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that enables LLMs to query data from various NASA APIs, allowing access to astronomical data, space weather information, Earth imagery, and exoplanet information directly from compatible AI clients.
      21
      6
      MIT

    • astrodynamics-mcp

      astro-tools
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that equips LLM clients with authoritative astrodynamics tools including TLE/SGP4 propagation, Lambert solving, ground-station access, time-scale and coordinate-frame conversions, and more.
      2
      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

    B3.1/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with separate tools for browsing, fetching, managing caches, SPICE operations, and high-level planning. There is no ambiguity between tools like browse_observatories and browse_pds_missions, as they target different data sources.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using underscores (e.g., browse_observatories, fetch_data, manage_spice_kernels). High-level tools consistently include 'spedas' as a prefix. The naming is predictable and easy to navigate.

    Tool Count4/5

    With 21 tools, the set is slightly above the ideal range of 3-15, but the number is justified by the need to cover three distinct data sources (CDAWeb, PDS, SPICE) plus planning and management operations. The tools are well-scoped and not excessive.

    Completeness4/5

    The tool set covers core workflows: browsing, data fetching, cache management, SPICE computations, and planning. Minor gaps exist, such as the lack of a search tool for datasets by criteria, but overall it supports the main use cases for space physics data analysis.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources