Skip to main content
Glama
Sign In
oddsky

oddsky

by AlanShortz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to oddsky

No user-submitted related servers found.

    Related Servers

    • Rediscover

      shyamolkonwar
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to download public LIGO strain data, run bounded matched-filter template searches, check detector data quality, generate source-linked reports, and verify analysis artifacts through safe MCP tools. It exposes catalog references and numerical evidence without arbitrary shell or generated-code execution.
      9
      MIT

    • skyportal-mcp

      AnastasiaKWei
      A
      license
      A
      quality
      D
      maintenance
      A local MCP server for SkyPortal and Fritz that exposes astronomical transient data (photometry, spectra, classifications, observability) as tools for AI coding assistants.
      23
      BSD 3-Clause

    • 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
      22 npm
      2
      BSD 3-Clause

    • Planet Hunter MCP

      eagnespuerto
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI assistants to Vetstar, MAST, SIMBAD, VizieR, Gaia DR3, ExoFOP-TESS, the NASA Exoplanet Archive, NASA ADS, Crossref/DataCite, the UAT, and Zenodo so users can vet TESS candidates, fit ephemerides, check contamination and novelty, build RNAAS manuscripts, verify references, and prepare Zenodo submission bundles. It prepares analyses and files only, leaving uploads, submissions, and publishing to the user.
      1
      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 26 tools

    Disambiguation4/5

    Most tools target clearly distinct operations: data retrieval (get_lightcurve, describe_series), specialised analyses (lens_fit, eclipse_period, fold, periodogram), and the claim/hypothesis/prediction ledger are well separated. Only mild overlap exists in the time-domain group (periodogram vs eclipse_period vs fold, describe_series vs find_excursions vs compare_windows) and in the literature group (literature vs prior_art), but descriptions draw clear boundaries.

    Naming Consistency3/5

    All names are consistent snake_case, but the verb convention is mixed: action tools use verb_noun (add_claim, update_hypothesis, register_prediction, open_case, list_cases), while many analysis tools are bare nouns (fold, periodogram, neighbors, literature, prior_art, lens_fit, ir_excess). Readable but not a single predictable pattern.

    Tool Count3/5

    26 tools is on the heavy side, though the domain is genuinely broad (data ingestion, several independent astrophysical analyses, a provenance ledger, and a novelty check). It is borderline: a few tools (cross_band, wise_color, ir_excess) could arguably be folded into a single band/colour comparison tool without losing capability.

    Completeness4/5

    Coverage is strong: case creation, multi-survey data access, a full claim/hypothesis/prediction lifecycle with retraction and grading, plus blend/skeptic and prior-art checks. Minor gaps: no dedicated list_claims or list_hypotheses tool (only case_overview aggregates them) and no way to close/archive or delete a case.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources