Skip to main content
Glama
Sign In
StarGazer1995

mcp-stargazing

by StarGazer1995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-stargazing

No user-submitted related servers found.

    Related Servers

    • Celestial Position MCP Server

      Rkm1999
      F
      license
      A
      quality
      D
      maintenance
      Provides altitude-azimuth coordinates for celestial objects including planets, over 117,000 stars, and 14,000 deep sky objects based on system time and configurable location.
      3
      1
      -

    • Sky Compass MCP

      cloudyrathor
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to determine a celestial object's magnetic compass bearing, altitude, and horizon visibility for a given location and time, including coordinate conversion and timed tracking samples.
      MIT

    • chuk-mcp-celestial

      IBM
      A
      license
      A
      quality
      F
      maintenance
      Provides authoritative astronomical data including moon phases, solar eclipses, and sun/moon rise and set times using the US Navy API or offline Skyfield calculations. It enables users to query Earth's seasons and celestial events for any location and date.
      8
      1
      Apache 2.0

    • Satellite MCP Server

      BuildASpacePro
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables satellite orbital mechanics calculations including visibility predictions, access window analysis, and TLE generation from natural language descriptions. Supports 200+ world cities and multiple orbit types (LEO, MEO, GEO, SSO, Molniya, Polar).
      -
    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.1/5.0

    Scored across 21 tools

    Disambiguation3/5

    Most tools are clearly separable (weather, celestial events, moon, planets, telescope targets), and the use/do-not-use guidance is unusually explicit. However, there are several overlapping decision paths: plan_stargazing_session vs get_best_stargazing_plan vs get_multiday_stargazing_plan, and analysis_area vs submit_area_analysis vs light_pollution_map. The two bbox-based plan tools are effectively legacy aliases of the preferred intent-based planner, which an agent must recognize from prose rather than the name.

    Naming Consistency4/5

    The dominant pattern is verb_noun snake_case (get_weather_by_position, get_celestial_pos, submit_area_analysis, cancel_area_analysis_task, list_visible_planets). A few names break the pattern with noun-only or irregular forms (analysis_area, light_pollution_map, plan_stargazing_session), but overall the convention is readable and predictable.

    Tool Count3/5

    21 tools is on the heavy side for a single domain, and a nontrivial share is infrastructure or legacy: a 4-tool background task lifecycle, two deprecated bbox planners, and get_tool_catalog/get_local_datetime_info utilities. The core astronomy and planning surface is well scoped, but the total feels over-expanded rather than every tool earning a distinct slot.

    Completeness4/5

    Coverage is broad: weather by name and coordinates, celestial positions/rise-set, moon, planets, nightly targets, equipment-matched targets, timed shooting plans, regional site search, light pollution, and multi-night planning. Minor gaps remain (e.g. satellite/comet/asteroid lookups, explicit seeing/transparency, direct multi-site weather comparison outside the planner), but nothing that creates an obvious dead end for observing workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources