Skip to main content
Glama
bezilaszlo

eea-climate-data-mcp

by bezilaszlo

Related Servers

Alternatives to eea-climate-data-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with the European Environment Agency (EEA) GeoNetwork Catalogue API to search, manage, and edit geographic metadata records. It supports advanced spatial searches, metadata exports in multiple formats, and authenticated updates to records and their attachments.
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables querying a local copy of the EU ETS Union Registry to search installations by name, country or activity, trace any installation's yearly verified emissions, free allocation and surrendered units, aggregate company installations by LEI, and rank top emitters, each answer carrying the snapshot date and attribution.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and accessing EU open datasets from data.europa.eu, including metadata discovery and dataset retrieval.
      20 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and browsing the Copernicus Climate Data Store catalogue and submitting retrieval jobs for climate datasets such as ERA5, CMIP6, and CORDEX projections.
      21 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Ireland's CSO PxStat statistics, including table search, catalog browsing, metadata retrieval, and filtered data queries with cell limits.
      MIT

    TDQS

    B3.4/5.0

    Scored across 18 tools

    Disambiguation3/5

    The SQL-related tools (validate_sql, explain_sql, query_sql, preview_rows, list_distinct_values) have overlapping purposes, though descriptions help distinguish them. get_emissions_series and query_sql both return data but serve different intents, and get_measure vs list_measures is clear.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern: get_, list_, search_, describe_, validate_, explain_, query_, preview_. There are no mixed conventions or inconsistent styles.

    Tool Count3/5

    18 tools is on the heavier side, largely due to 12 SQL-focused tools. The server's purpose is broad (emissions, measures, SQL exploration), but the count feels slightly over-optimized for coherence.

    Completeness4/5

    The tool set covers emissions data, sector metadata, PaMs catalogue, and SQL exploration. Missing update/delete operations are appropriate for a read-only data server. Core workflows are supported with no dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues