Skip to main content
Glama
blongworth

nes-lter-mcp

by blongworth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to nes-lter-mcp

No user-submitted related servers found.

    Related Servers

    • ERDDAP MCP Server

      robertdcurrier
      F
      license
      Not graded
      quality
      D
      maintenance
      Access oceanographic and environmental data from 63+ ERDDAP servers worldwide through natural language queries. Search datasets, retrieve metadata, and download scientific data for climate research, marine biology, and coastal management.
      18
      -

    • fisheries-data

      adamsconchallos
      A
      license
      A
      quality
      B
      maintenance
      Enables natural-language research queries across marine data sources including FAO FishStat, BarentsWatch Fish Health, and Copernicus Marine, with data provenance and local file exports.
      7
      MIT

    • Ocean MCP

      ishimwe5555
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to work with Copernicus Marine ocean data through semantic tools for dataset discovery, metadata retrieval, recommendation, validation, point time-series extraction, area statistics, subsetting, and computation without exposing raw API plumbing.
      -

    • data-cityofnewyork

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying NYC Open Data datasets using natural language, with tools to search datasets, run SoQL queries, and retrieve metadata, all without an API key.
      254 npm
      MIT

    • Rasdaman MCP Server

      fastmcp-me
      A
      license
      A
      quality
      D
      maintenance
      Enables natural language interaction with rasdaman databases, allowing users to list coverages, describe datacubes, and execute WCPS queries.
      5
      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/5.0

    Scored across 10 tools

    Disambiguation3/5

    Most tools are distinct (stations, cruises, casts, CTD, track, schema, variable resolution). However, get_cast_profile vs query_ctd overlap since both return CTD profiles, and get_station_profile is explicitly a compatibility wrapper that duplicates query_ctd purpose—creating real misselection risk.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_, find_, get_, query_). Minor deviations exist with get_cruise_track (returns a URL rather than track data) and resolve_variable (verb_object but semantically different), but overall patterns are predictable.

    Tool Count4/5

    Ten tools is a reasonable count for an oceanographic data server covering stations, cruises, CTD casts, datasets, schema, and variable resolution. Slightly heavy but each tool addresses a distinct lookup/query need within the domain.

    Completeness5/5

    The surface covers the full NES-LTER data lifecycle: station discovery, cruise search, cast listing, profile retrieval, batch queries, dataset row fetching, schema introspection, and variable resolution. The get_station_profile wrapper suggests legacy coverage, and no obvious dead ends exist for a data-retrieval server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources