Skip to main content
Glama
jefseghers-del

gbif-mcp

by jefseghers-del
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to gbif-mcp

No user-submitted related servers found.

    Related Servers

    • gbif-mcp

      tyson-swetnam
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query and retrieve biodiversity data from the Global Biodiversity Information Facility (GBIF), including species, occurrences, datasets, and literature.
      111 npm
      MIT

    • mcp-gbif

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying biodiversity data from the Global Biodiversity Information Facility (GBIF) API v1, supporting species occurrence searches and other GBIF endpoints through natural language.
      114 npm
      MIT

    • mcp-nbb

      lacausecrypto
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables discovery and retrieval of National Bank of Belgium statistical data across 221 SDMX dataflows, with search, descriptions, custom queries, and comparisons of economic indicators.
      25 PyPI
      3
      MIT

    • be-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      B
      maintenance
      Enables retrieval of Belgian legislation metadata and full text by ELI coordinates from the official gazette (Moniteur Belge), supporting French, Dutch, and German languages.
      3
      46 PyPI
      Apache 2.0
    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 13 tools

    Disambiguation4/5

    Every tool has a distinct role: single-species status, area species lists, occurrence records, counts, mapping, and report generation are clearly separated. The only mild ambiguity is between `telling_in_gebied` and `soorten_in_gebied`, since both use the same area filters and one could be used instead of the other; the descriptions explicitly position one as a fast count-only path and the other as the detailed list.

    Naming Consistency3/5

    Names are readable and mostly follow a descriptive noun-phrase style (`soorten_in_gebied`, `gebieden_rond`, `datarapport_natuur`), but several tools use imperative verbs (`zoek_soort`, `exporteer_bevraging`, `geocodeer_adres`) and others are bare nouns (`lijst`, `bronnen`, `waarnemingen`). There is no consistent verb_noun convention, though the mixed style is still understandable.

    Tool Count5/5

    Thirteen tools is well within the ideal range and appropriate for a read-only biodiversity reporting domain. Each tool fills a clear workflow stage: species lookup, status, observations, area summaries, protected-area data, mapping, export, and final PDF report generation.

    Completeness5/5

    The toolset covers the full query-to-deliverable lifecycle: geocoding, taxon resolution, list/status lookups, occurrence queries, area-based aggregation, protected-area overlays, map generation, data export, and a generated datarapport. For a read-only nature-reporting service, there are no obvious dead ends or missing core operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources