Skip to main content
Glama
rokoss21

astrovisor-mcp

by rokoss21
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to astrovisor-mcp

No user-submitted related servers found.

    Related Servers

    • yellow-pages

      ethank64
      F
      license
      A
      quality
      D
      maintenance
      Exposes two MCP tools (discover and execute) that enable agents to query an OpenAPI schema via natural language and execute matched API operations.
      2
      -

    • openapi-to-mcp

      The-Swarm-Corporation
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to call any OpenAPI-defined API by automatically converting its operations into tools, with built-in support for authentication, rate limiting, and response handling.
      7
      Apache 2.0

    • aqc-mcp

      inoribea
      A
      license
      B
      quality
      D
      maintenance
      MCP server that provides tools to query 17+ astronomical databases (e.g., SIMBAD, VizieR, Gaia) via HTTP/TAP APIs, enabling AI applications to access astronomical data through natural language.
      23
      9 npm
      2
      BSD 3-Clause

    • Relay

      adarshp14
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
      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.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: one for executing API calls, three for exploring OpenAPI specs, one for retrieving results, and one for conventions. No overlapping functionality.

    Naming Consistency5/5

    All tool names follow a consistent 'astrovisor_<action>' pattern using snake_case, making them predictable and easy to understand.

    Tool Count5/5

    With 6 tools, the server is well-scoped for its purpose of interacting with an API explorer and executor. Neither too few nor too many.

    Completeness4/5

    The tool set covers the core workflow: exploring operations, retrieving metadata, executing requests, and fetching results. A minor gap is the lack of a way to list stored results, but this is acceptable given the design.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources