F
licenseNot graded
qualityD
maintenanceEnables AI assistants to query and retrieve biodiversity data from the Global Biodiversity Information Facility (GBIF), including species, occurrences, datasets, and literature.
-
gbif-mcp-server
Server Details
Search GBIF species taxonomy, occurrence records, datasets, and publishers.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- cyanheads/gbif-biodiversity-mcp-server
- GitHub Stars
- 1
- Server Listing
- GBIF Biodiversity MCP Server
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Changed
gbif_match_species1 field changed- changed
Input schema / properties / name / descriptionPrevious value: -"Scientific or common name to match. Examples: \"Parus major\", \"Great Tit\", \"Homo sapiens\". Fuzzy matching handles minor typos."New value: +"Scientific name to match. Examples: \"Parus major\", \"Agaricus bisporus\", \"Homo sapiens\". Fuzzy matching handles minor spelling variations. Common names are not supported — use gbif_search_species for vernacular name searches."
- Changed
gbif_search_occurrences1 field changed- removed
Output schema / properties / paginationNoteRemoved value: -{ - "description": "Warning when approaching the ~100,000 offset+limit cap. Use gbif_occurrence_facets or refine filters for larger result sets.", - "type": "string" -}
12 tool updates
- First observed
gbif_count_occurrences - First observed
gbif_get_dataset - First observed
gbif_get_occurrence - First observed
gbif_get_species - First observed
gbif_get_species_children - First observed
gbif_get_species_classification - First observed
gbif_match_species - First observed
gbif_occurrence_facets - First observed
gbif_search_datasets - First observed
gbif_search_occurrences - First observed
gbif_search_publishers - First observed
gbif_search_species
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Search GBIF species taxonomy, occurrence records, datasets, and publishers.
Search books and authors across Open Library, the Internet Archive open catalog.
GBIF MCP — wraps the Global Biodiversity Information Facility API v1 (free, no auth)
Search public Australian environmental evidence with provenance across authoritative catalogues.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables querying biodiversity data from the Global Biodiversity Information Facility (GBIF) API v1, supporting species occurrence searches and other GBIF endpoints through natural language.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables queries about global taxonomic data, including scientific name matching, classification chains, common names, and synonyms from the Catalogue of Life index.15MIT
- AlicenseAqualityDmaintenanceEnables searching the NIAID Data Ecosystem for biomedical research resources including datasets, clinical studies, and publications using Elasticsearch queries.3MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation5/5
Each tool clearly targets a distinct operation on a specific resource type (occurrences, species, datasets, publishers). For example, count_occurrences, search_occurrences, and occurrence_facets serve different purposes (counting, searching, aggregating), and get_species vs search_species vs match_species are well-differentiated. No two tools have overlapping functionality.
Naming Consistency4/5
All tools use the 'gbif_' prefix and mostly follow a verb_noun pattern (e.g., gbif_count_occurrences, gbif_get_dataset, gbif_search_occurrences). The only minor deviation is gbif_occurrence_facets, which places the verb second; however, the pattern is still highly recognizable and consistent overall.
Tool Count5/5
With 12 tools covering search, retrieval, counting, faceting, and matching across occurrences, species, datasets, and publishers, the tool count is well-proportioned to the server's purpose. Each tool addresses a specific need without redundancy or bloat.
Completeness5/5
The tool set covers the essential GBIF operations: name resolution (match_species), occurrence search and counting (search_occurrences, count_occurrences, occurrence_facets), species taxonomy (get_species, get_species_children, get_species_classification, search_species), dataset and publisher metadata (search_datasets, get_dataset, search_publishers), and detailed occurrence records (get_occurrence). No obvious dead ends or missing operations for typical biodiversity queries.