Skip to content

gbif-biodiversity-mcp-server

io.github.cyanheads/gbif-biodiversity-mcp-servercyanheadsstreamable-httpv0.8.2Scanned

Search GBIF species taxonomy, occurrence records, datasets, and publishers.

13 tools: 2 change things and 11 only read.

Tools: 0 delete, 0 irreversible, 2 write, 11 read.
  • Reads private data · 1
  • Reads text others write · 13
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the gbif-biodiversity-mcp-server can do

The gbif-biodiversity-mcp-server is published by the GitHub account cyanheads. It has 13 tools. It can create or change data (2 tools: gbif_match_species and gbif_occurrence_facets), but cannot delete data. 11 tools only read.

1 tool reads private data (gbif_get_dataset); 13 tools bring in text other people can write (gbif_match_species, gbif_bulk_match_species, gbif_get_species and 10 more).

The fixed checks matched 3 findings (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 0.8.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Changes things 2Claude Code: ask
  • gbif_match_speciesMatch a scientific name against the GBIF backbone taxonomy.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Match a scientific name against the GBIF backbone taxonomy. Returns the best-matching taxon with full classification and a confidence score (0–100). This is the mandatory first step for any GBIF workflow — it returns the backbone taxonKey required by gbif_search_occurrences, gbif_count_occurrences, and gbif_occurrence_facets. When the name GBIF matched is a synonym — the queried name, or the higher taxon a HIGHERRANK match falls back to — taxonKey is the accepted taxon it resolves to and matchedTaxonKey carries the synonym's own key; occurrence counts differ sharply between the two, so pass taxonKey. acceptedName names that accepted taxon whenever GBIF's answer does. matchType HIGHERRANK is GBIF's label for a match made at a higher rank: a misspelled or unknown species falls back to its genus or even its kingdom, at a confidence that can exceed 90, and a bare genus name carries the label too, matched as that genus. taxonKey then covers that whole taxon, or its accepted taxon when it is a synonym, and a notice names it. Below confidence 80, the match should be reviewed. matchType NONE means no usable match was found — try removing the strict flag or broadening the name; when GBIF reports several equal matches, as for a genus name shared by an animal and a plant, set kingdom to pick one. GBIF no longer updates the backbone, so a name described or revised since its last build falls back to a higher taxon there; checklistKey 7ddf754f-d193-4cc9-b351-99906754a03b matches against the Catalogue of Life eXtended Release instead, GBIF's current taxonomy, and returns its keys as strings in checklistTaxonKey and checklistMatchedTaxonKey with no taxonKey or rank keys — they are not backbone keys, and no tool that takes a numeric taxonKey can use them, but gbif_search_occurrences, gbif_count_occurrences, and gbif_occurrence_facets take checklistTaxonKey under that name, with checklistKey 7ddf754f-d193-4cc9-b351-99906754a03b.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_occurrence_facetsAggregate occurrence counts across a dimension (COUNTRY, STATE_PROVINCE, YEAR, BASIS_OF_RECORD, DATASET_KEY, KINGDOM_KEY, etc.).Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,043 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...nce/absence split itself, pass facet OCCURRENCE_STATUS with occurrenceStatus ANY."

      What this check looks for
    Description, as the server wrote it
    Aggregate occurrence counts across a dimension (COUNTRY, STATE_PROVINCE, YEAR, BASIS_OF_RECORD, DATASET_KEY, KINGDOM_KEY, etc.). Returns one page of facet values ranked by count descending — the top facetLimit at facetOffset 0, a later slice of the same ranking past that. No record payloads returned. Core tool for distribution analysis and trend queries: "which countries have the most records for this species?", "how has observation volume changed since 2010?". Key and GADM dimensions (KINGDOM_KEY through SPECIES_KEY, DATASET_KEY, PUBLISHING_ORG, GADM_LEVEL_0_GID through GADM_LEVEL_3_GID) return bare keys; includeLabels names the taxon, dataset, publishing organization, or administrative area behind each one on the page. Scope the aggregation with taxonKey (or checklistTaxonKey with checklistKey, for a Catalogue of Life key), country (uppercase ISO 3166-1 alpha-2), publishingCountry, stateProvince, gadmGid, year, month or a month range, eventDate (a date or date range), scientificName, latitude/longitude ranges, hasCoordinate, hasGeospatialIssue, isInCluster, coordinateUncertaintyInMeters, elevation and depth ranges, geometry and geoDistance (a radius around a point; all spatial filters intersect), basisOfRecord, datasetKey, publishingOrg, catalogNumber, institutionCode, recordedBy, mediaType, typeStatus, establishmentMeans, license, occurrenceStatus, or iucnRedListCategory filters. country, basisOfRecord, taxonKey, and checklistTaxonKey each take one value or an array: values within one filter are OR-ed, so an array aggregates into one ranking, and different filters still intersect, except that GBIF unions a taxon key with scientificName. Also the way to split a result set too large for gbif_search_occurrences to page (offset+limit caps at 100,001): facet by DATASET_KEY, then search each datasetKey on its own. Aggregates sightings only by default, matching gbif_search_occurrences and gbif_count_occurrences; to measure the presence/absence split itself, pass facet OCCURRENCE_STATUS with occurrenceStatus ANY.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
Only reads 11Show 11 read-only tools
  • gbif_bulk_match_speciesResolve up to 50 scientific names to GBIF backbone taxon keys in one call — the batch counterpart to gbif_match_species for checklist, inventory, and species-list workflows that wo…Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "resolve": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,467 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...if_search_species for vernacular searches. Below confidence 80, review the match."

      What this check looks for
    Description, as the server wrote it
    Resolve up to 50 scientific names to GBIF backbone taxon keys in one call — the batch counterpart to gbif_match_species for checklist, inventory, and species-list workflows that would otherwise need one round trip per name. Each name is matched independently and results are returned in input order, one entry per processed name. An entry is a name string, or { name, kingdom } to narrow that one name to a kingdom: a name shared across kingdoms, such as Oenanthe (a bird genus and a plant genus), matches nothing until its entry names one, while a kingdom applied to every name would move the others (Parus major under Plantae matches the pear Pyrus major). By default, an oversized batch processes the first 50 and returns the remaining entries, as submitted, in unprocessedNames. A name GBIF matched at a higher rank yields matchType HIGHERRANK with a note naming the taxon matched and what its key covers: that whole taxon, or its accepted taxon when it is a synonym — a misspelled species can fall back to its genus or kingdom at a confidence above 90, and a bare genus name carries the label too, matched as that genus. A name with no match yields matchType NONE (no key) instead of failing the batch, with a note carrying GBIF's explanation when it gives one, such as several equal matches for a name shared across kingdoms; a per-name lookup failure yields matchType ERROR carrying that name's error message and, when the failure was classified, a machine-readable reason — the rest of the batch is unaffected, and the call as a whole still succeeds unless the deployment cannot reach the Catalogue of Life route checklistKey needs (a GBIF_BASE_URL not ending in /v1), which fails the call. When the name GBIF matched is a synonym — the queried name, or the higher taxon a HIGHERRANK match falls back to — taxonKey is the accepted taxon it resolves to, matchedTaxonKey carries the synonym's own key, and acceptedName names the accepted taxon whenever GBIF's answer does. checklistKey 7ddf754f-d193-4cc9-b351-99906754a03b matches the whole batch against the Catalogue of Life eXtended Release instead of the backbone, which GBIF no longer updates; its keys come back as strings in checklistTaxonKey and checklistMatchedTaxonKey, with no taxonKey, and the occurrence tools take checklistTaxonKey under that name, with the same checklistKey. Common names are not supported — use gbif_search_species for vernacular searches. Below confidence 80, review the match.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_count_occurrencesCount occurrences matching a taxon + location filter without fetching records.Reads text others writeNo findings

    Why it is in this group

    • The name "gbif_count_occurrences" says "count": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Count occurrences matching a taxon + location filter without fetching records. Use for quick totals ("how many Aves records in Sweden?") or before deciding whether to paginate a full search. Accepts taxonKey (or checklistTaxonKey with checklistKey, for a Catalogue of Life key), country (uppercase ISO 3166-1 alpha-2), publishingCountry, stateProvince, gadmGid, scientificName, spatial ranges, geometry, and geoDistance (a radius around a point; all intersected), elevation and depth ranges, year, month or a month range, eventDate (a date or date range), basisOfRecord, hasCoordinate (alias isGeoreferenced), hasGeospatialIssue, isInCluster, coordinateUncertaintyInMeters, datasetKey, publishingOrg, catalogNumber, institutionCode, recordedBy, mediaType, typeStatus, establishmentMeans, license, occurrenceStatus, and iucnRedListCategory. country, basisOfRecord, taxonKey, and checklistTaxonKey each take one value or an array: values within one filter are OR-ed, and different filters still intersect, except that GBIF unions a taxon key with scientificName. Counts sightings only by default, matching gbif_search_occurrences — GBIF also indexes absence records, and for some taxa they are the overwhelming majority. A count above 100,001 is the signal to partition rather than page: gbif_search_occurrences cannot reach past that offset, so split the query by DATASET_KEY via gbif_occurrence_facets and search each dataset separately.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_get_datasetFetch full dataset metadata by UUID key — title, description, citation text, contacts, license, DOI, record count, numConstituents (sub-datasets), temporal coverage, geographic cov…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "gbif_get_dataset" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fetch full dataset metadata by UUID key — title, description, citation text, contacts, license, DOI, record count, numConstituents (sub-datasets), temporal coverage, geographic coverage with its bounding boxes, the deletion timestamp of a dataset GBIF no longer publishes, and the publishing organization key, which gbif_search_datasets takes as publishingOrg. Use after gbif_search_datasets or when an occurrence record's datasetKey needs provenance detail. Contacts are capped by contactLimit (default 10); contactsTotal and contactsReturned report the full count.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_get_occurrenceFetch a single occurrence record by its GBIF occurrence key.Reads text others writeNo findings

    Why it is in this group

    • The name "gbif_get_occurrence" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fetch a single occurrence record by its GBIF occurrence key. Returns the Darwin Core record — coordinates with what the publisher withheld or generalized about them (informationWithheld, dataGeneralizations), elevation and depth, administrative geography (GADM levels 0–3), dates, collections metadata, collector identifiers and record number, the identification date (dateIdentified), the recorder's remarks, habitat, sampling protocol and organism quantity, type status, establishment means, the backbone key at every rank, the accepted taxon behind a synonym, conservation status, license, rights holder, publishing organization, the source dataset's name, the link to the source record (references), media links with their rights holders, duplicate-cluster membership (isInCluster), and quality issue flags. Check occurrenceStatus before reading the record as a sighting: NOT_DETECTED (ABSENT or NOT_DETECTED in the occurrenceStatus filter) means a survey looked for the taxon and did not find it. Use the occurrence key from gbif_search_occurrences results.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_get_speciesFetch a single taxon usage by its GBIF taxon key, from the GBIF backbone or any other checklist.Reads text others writeNo findings

    Why it is in this group

    • The name "gbif_get_species" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fetch a single taxon usage by its GBIF taxon key, from the GBIF backbone or any other checklist. Returns full classification, authorship, taxonomic status, vernacular name, descendant count, and publication reference. Use after gbif_match_species when you need the complete record rather than the match summary, or on a taxon usage key from gbif_search_species. datasetKey names the checklist the record belongs to, and key and the rank, parent, and accepted keys are taxon usage keys of that checklist. nubKey is the mapped backbone key, the one the occurrence tools take as taxonKey; it is absent where the backbone has no mapping. When taxonomicStatus is SYNONYM, acceptedKey and accepted fields identify the accepted taxon. The extinct field is absent (not false) on most records — only present on explicitly flagged taxa.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_get_species_childrenList direct children of a taxon usage within its own checklist — genera within a family, species within a genus, subspecies within a species.Reads text others writeNo findings

    Why it is in this group

    • The name "gbif_get_species_children" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List direct children of a taxon usage within its own checklist — genera within a family, species within a genus, subspecies within a species. Each child is a usage of the parent's checklist: datasetKey names that checklist, key is its taxon usage key there, and nubKey is the mapped backbone key the occurrence tools take, absent where the backbone has no mapping. Paginated. Use gbif_match_species to get a backbone taxonKey first, then iterate with offset for large groups.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_get_species_classificationReturn the parent chain for a taxon — from kingdom (or domain) down to the immediate parent of the queried taxon — as an ordered array.Reads text others writeNo findings

    Why it is in this group

    • The name "gbif_get_species_classification" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Return the parent chain for a taxon — from kingdom (or domain) down to the immediate parent of the queried taxon — as an ordered array. Each entry has its rank, canonical name, taxon usage key, checklist, and backbone mapping. The array is returned root-first (kingdom → phylum → class → … → immediate parent of the queried taxon); the queried taxon itself is not included — call gbif_get_species for its own record. The chain is read in the queried taxon's own checklist: datasetKey names it, each key is a taxon usage key there, and nubKey is the mapped backbone key the occurrence tools take, absent where the backbone has no mapping. Useful for building taxonomic trees or understanding placement without walking the checklist level by level.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_search_datasetsSearch GBIF datasets by keyword, type, publishing country (uppercase ISO 3166-1 alpha-2), publishing organization, or hosting organization.Reads text others writeNo findings

    Why it is in this group

    • The name "gbif_search_datasets" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Search GBIF datasets by keyword, type, publishing country (uppercase ISO 3166-1 alpha-2), publishing organization, or hosting organization. The two organization filters answer different questions — publishingOrg matches the organization whose data it is, hostingOrg the organization whose installation serves it — and an organization key from gbif_search_publishers usually wants publishingOrg. Returns dataset title, description, license, record count, DOI, and the publishing organization's key and name; the key goes back in as publishingOrg. Use to find the source dataset behind a set of records, or to explore what data collections are available for a taxon, country, or organization.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_search_occurrencesSearch GBIF occurrence records with Darwin Core filters.Reads text others write1 finding

    Why it is in this group

    • The name "gbif_search_occurrences" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,184 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...PI with a GBIF.org account or the monthly GBIF Parquet snapshot on AWS Open Data."

      What this check looks for
    Description, as the server wrote it
    Search GBIF occurrence records with Darwin Core filters. Use taxonKey from gbif_match_species for reliable results — a key names exactly one taxon, where a scientificName shared across kingdoms matches nothing; a Catalogue of Life key goes in checklistTaxonKey with checklistKey 7ddf754f-d193-4cc9-b351-99906754a03b. Accepts country (uppercase ISO 3166-1 alpha-2, where the record was observed), publishingCountry (the publishing organization's country — a different question), stateProvince, gadmGid (a GADM administrative-area code GBIF derives from coordinates), bounding box (decimalLatitude/decimalLongitude ranges), WKT polygon geometry, geoDistance (a radius around a point), elevation and depth ranges, year range, month or month range, eventDate (a date or date range), basis of record, coordinate filter, hasGeospatialIssue, dataset key, publishingOrg (the publishing organization), catalogNumber, institutionCode, recordedBy (collector), mediaType, typeStatus, establishmentMeans, and license. country, basisOfRecord, taxonKey, and checklistTaxonKey each take one value or an array: values within one filter are OR-ed, and different filters still intersect, except that GBIF unions a taxon key with scientificName. Rows carry no media unless includeMedia is set. Returns sightings only by default — GBIF also indexes absence records (surveys that looked and found nothing), and occurrenceStatus controls whether they are included. Pagination is capped at offset+limit=100,001 and GBIF offers no cursor or scroll, so a larger result set is covered only by partitioning it — facet it by DATASET_KEY with gbif_occurrence_facets and search each datasetKey separately. BASIS_OF_RECORD and PUBLISHING_COUNTRY are gap-free second cuts for a dataset bucket still over the cap; YEAR, MONTH, STATE_PROVINCE, and SPECIES_KEY lose records lacking that dimension. Repeat every biological filter on the facet call and each partition search, including the same occurrenceStatus, and compare sub-split sums against the bucket total. Bulk retrieval is outside this server: use the asynchronous GBIF Download API with a GBIF.org account or the monthly GBIF Parquet snapshot on AWS Open Data.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_search_publishersSearch organizations registered with GBIF by name fragment or country.Reads text others writeNo findings

    Why it is in this group

    • The name "gbif_search_publishers" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Search organizations registered with GBIF by name fragment or country. Returns organization key, title, and country — sufficient to chain into gbif_search_datasets as publishingOrg for the datasets an organization published, or as hostingOrg for the ones its own installation serves, or to understand who publishes data for a region. publishingOrg is the usual chain: most organizations publish through an installation someone else runs, so hostingOrg matches nothing for them.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • gbif_search_speciesSearch or browse the GBIF backbone taxonomy by default, or an explicit checklist datasetKey.Reads text others writeNo findings

    Why it is in this group

    • The name "gbif_search_species" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Search or browse the GBIF backbone taxonomy by default, or an explicit checklist datasetKey. Accepts scientific name fragments, rank and taxonomic status filters, and higher-taxon constraints — status ["ACCEPTED"] with rank SPECIES under a genus lists only that genus's accepted species. Useful for exploring what species exist under a higher taxon (e.g., "list all families of Coleoptera"), for simple name-fragment searches, or when gbif_match_species returns too narrow a result. kingdom, family, and genus scope the browse to a higher taxon: each is resolved to its backbone key before the search runs, so the narrowest one supplied is what scopes, an alternative name resolves to the taxon it is a synonym of, and a name that matches no backbone taxon at that rank fails rather than returning the whole index. Names are matched by their exact spelling in any letter case, never fuzzily. Paginated — use limit and offset to walk through results, up to an offset + limit of 100,000.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://gbif-biodiversity.caseyjhand.com/mcp: tools/list returned 13 tools to an anonymous client, including gbif_match_species (write), gbif_occurrence_facets (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools9 changed.~9 changedView diff
  2. Tools8 changed.~8 changedView diff
  3. Tools13 changed.~13 changedView diff
  4. Tools9 changed.~9 changedView diff
  5. Tools4 changed.~4 changedView diff

Install

Pinned to version 0.8.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http gbif-biodiversity https://gbif-biodiversity.caseyjhand.com/mcp
claude mcp add --transport http gbif-biodiversity https://gbif-biodiversity.caseyjhand.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__gbif-biodiversity__gbif_bulk_match_species",
      "mcp__gbif-biodiversity__gbif_get_species",
      "mcp__gbif-biodiversity__gbif_search_species",
      "mcp__gbif-biodiversity__gbif_get_species_classification",
      "mcp__gbif-biodiversity__gbif_get_species_children",
      "mcp__gbif-biodiversity__gbif_search_occurrences",
      "mcp__gbif-biodiversity__gbif_count_occurrences",
      "mcp__gbif-biodiversity__gbif_get_occurrence",
      "mcp__gbif-biodiversity__gbif_search_datasets",
      "mcp__gbif-biodiversity__gbif_get_dataset",
      "mcp__gbif-biodiversity__gbif_search_publishers"
    ],
    "ask": [
      "mcp__gbif-biodiversity__gbif_match_species",
      "mcp__gbif-biodiversity__gbif_occurrence_facets"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gbif-biodiversity. Review it before you use it.

Capability tags behind 13 rules
  • mcp__gbif-biodiversity__gbif_match_species untrusted-input
  • mcp__gbif-biodiversity__gbif_bulk_match_species untrusted-input
  • mcp__gbif-biodiversity__gbif_get_species untrusted-input
  • mcp__gbif-biodiversity__gbif_search_species untrusted-input
  • mcp__gbif-biodiversity__gbif_get_species_classification untrusted-input
  • mcp__gbif-biodiversity__gbif_get_species_children untrusted-input
  • mcp__gbif-biodiversity__gbif_search_occurrences untrusted-input
  • mcp__gbif-biodiversity__gbif_count_occurrences untrusted-input
  • mcp__gbif-biodiversity__gbif_get_occurrence untrusted-input
  • mcp__gbif-biodiversity__gbif_occurrence_facets untrusted-input
  • mcp__gbif-biodiversity__gbif_search_datasets untrusted-input
  • mcp__gbif-biodiversity__gbif_get_dataset private-data, untrusted-input
  • mcp__gbif-biodiversity__gbif_search_publishers untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/gbif-biodiversity-mcp-server/verify?hash=ee17ff65477f32fe462e4fbfe097d5bfb24b0a6db7cf8488e8f923af552c6339" | jq -e '.changed == false'

Pinned hash ee17ff65477f, from Nov 19, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.cyanheads/gbif-biodiversity-mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.cyanheads/gbif-biodiversity-mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.cyanheads/gbif-biodiversity-mcp-server.svg)](https://radar.anlyon.com/servers/io.github.cyanheads/gbif-biodiversity-mcp-server)

Source: MCP Registry · repository. Synced Nov 19, 2026, 16:18 UTC.

gbif-biodiversity-mcp-server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the gbif-biodiversity-mcp-server safe?

No scan can promise that. What its definitions show: 13 tools, 2 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the gbif-biodiversity-mcp-server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the gbif-biodiversity-mcp-server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the gbif-biodiversity-mcp-server have?

13 tools: 2 write, 11 read. gbif_match_species, gbif_occurrence_facets, gbif_bulk_match_species, gbif_get_species, gbif_search_species, gbif_get_species_classification, gbif_get_species_children, gbif_search_occurrences and 5 more.

Does the gbif-biodiversity-mcp-server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the gbif-biodiversity-mcp-server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the gbif-biodiversity-mcp-server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.