@cyanheads/gbif-biodiversity-mcp-server 0.8.0 → 0.8.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/AGENTS.md +5 -5
- package/CLAUDE.md +5 -5
- package/README.md +62 -48
- package/changelog/0.8.x/0.8.0.md +1 -1
- package/changelog/0.8.x/0.8.1.md +39 -0
- package/changelog/0.8.x/0.8.2.md +38 -0
- package/changelog/template.md +10 -3
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/dist/mcp-server/resources/definitions/gbif-dataset.resource.d.ts +8 -0
- package/dist/mcp-server/resources/definitions/gbif-dataset.resource.d.ts.map +1 -1
- package/dist/mcp-server/resources/definitions/gbif-dataset.resource.js +27 -6
- package/dist/mcp-server/resources/definitions/gbif-dataset.resource.js.map +1 -1
- package/dist/mcp-server/resources/definitions/gbif-species.resource.d.ts +6 -3
- package/dist/mcp-server/resources/definitions/gbif-species.resource.d.ts.map +1 -1
- package/dist/mcp-server/resources/definitions/gbif-species.resource.js +31 -10
- package/dist/mcp-server/resources/definitions/gbif-species.resource.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-bulk-match-species.tool.d.ts +23 -4
- package/dist/mcp-server/tools/definitions/gbif-bulk-match-species.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-bulk-match-species.tool.js +119 -42
- package/dist/mcp-server/tools/definitions/gbif-bulk-match-species.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-count-occurrences.tool.d.ts +45 -12
- package/dist/mcp-server/tools/definitions/gbif-count-occurrences.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-count-occurrences.tool.js +18 -56
- package/dist/mcp-server/tools/definitions/gbif-count-occurrences.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-get-dataset.tool.d.ts +8 -0
- package/dist/mcp-server/tools/definitions/gbif-get-dataset.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-get-dataset.tool.js +43 -10
- package/dist/mcp-server/tools/definitions/gbif-get-dataset.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-get-occurrence.tool.d.ts +28 -0
- package/dist/mcp-server/tools/definitions/gbif-get-occurrence.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-get-occurrence.tool.js +210 -40
- package/dist/mcp-server/tools/definitions/gbif-get-occurrence.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-get-species-children.tool.d.ts +5 -3
- package/dist/mcp-server/tools/definitions/gbif-get-species-children.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-get-species-children.tool.js +33 -14
- package/dist/mcp-server/tools/definitions/gbif-get-species-children.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-get-species-classification.tool.d.ts +4 -2
- package/dist/mcp-server/tools/definitions/gbif-get-species-classification.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-get-species-classification.tool.js +33 -16
- package/dist/mcp-server/tools/definitions/gbif-get-species-classification.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-get-species.tool.d.ts +6 -3
- package/dist/mcp-server/tools/definitions/gbif-get-species.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-get-species.tool.js +64 -24
- package/dist/mcp-server/tools/definitions/gbif-get-species.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-match-species.tool.d.ts +9 -2
- package/dist/mcp-server/tools/definitions/gbif-match-species.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-match-species.tool.js +125 -71
- package/dist/mcp-server/tools/definitions/gbif-match-species.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-occurrence-facets.tool.d.ts +54 -12
- package/dist/mcp-server/tools/definitions/gbif-occurrence-facets.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-occurrence-facets.tool.js +122 -77
- package/dist/mcp-server/tools/definitions/gbif-occurrence-facets.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-search-datasets.tool.d.ts +5 -0
- package/dist/mcp-server/tools/definitions/gbif-search-datasets.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-search-datasets.tool.js +41 -4
- package/dist/mcp-server/tools/definitions/gbif-search-datasets.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-search-occurrences.tool.d.ts +62 -12
- package/dist/mcp-server/tools/definitions/gbif-search-occurrences.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-search-occurrences.tool.js +147 -67
- package/dist/mcp-server/tools/definitions/gbif-search-occurrences.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-search-publishers.tool.d.ts +1 -1
- package/dist/mcp-server/tools/definitions/gbif-search-publishers.tool.js +1 -1
- package/dist/mcp-server/tools/definitions/gbif-search-publishers.tool.js.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-search-species.tool.d.ts +25 -2
- package/dist/mcp-server/tools/definitions/gbif-search-species.tool.d.ts.map +1 -1
- package/dist/mcp-server/tools/definitions/gbif-search-species.tool.js +67 -26
- package/dist/mcp-server/tools/definitions/gbif-search-species.tool.js.map +1 -1
- package/dist/mcp-server/tools/utils.d.ts +279 -37
- package/dist/mcp-server/tools/utils.d.ts.map +1 -1
- package/dist/mcp-server/tools/utils.js +602 -47
- package/dist/mcp-server/tools/utils.js.map +1 -1
- package/dist/services/gbif/gbif-service.d.ts +50 -8
- package/dist/services/gbif/gbif-service.d.ts.map +1 -1
- package/dist/services/gbif/gbif-service.js +139 -29
- package/dist/services/gbif/gbif-service.js.map +1 -1
- package/dist/services/gbif/types.d.ts +185 -27
- package/dist/services/gbif/types.d.ts.map +1 -1
- package/dist/services/gbif/types.js +149 -10
- package/dist/services/gbif/types.js.map +1 -1
- package/package.json +7 -7
- package/server.json +5 -5
- package/skills/gbif-biodiversity-guide/SKILL.md +22 -17
package/AGENTS.md
CHANGED
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
# Developer Protocol
|
|
2
2
|
|
|
3
3
|
**Server:** @cyanheads/gbif-biodiversity-mcp-server
|
|
4
|
-
**Version:** 0.8.
|
|
5
|
-
**Framework:** [@cyanheads/mcp-ts-core](https://www.npmjs.com/package/@cyanheads/mcp-ts-core) `^0.13.
|
|
6
|
-
**Engines:** Bun ≥1.4.
|
|
4
|
+
**Version:** 0.8.2
|
|
5
|
+
**Framework:** [@cyanheads/mcp-ts-core](https://www.npmjs.com/package/@cyanheads/mcp-ts-core) `^0.13.22`
|
|
6
|
+
**Engines:** Bun ≥1.4.4, Node ≥24.0.0
|
|
7
7
|
**MCP SDK:** `@modelcontextprotocol/server` ^2.4.0
|
|
8
8
|
**Zod:** ^4.6.7
|
|
9
9
|
|
|
@@ -353,7 +353,7 @@ When you complete a skill's checklist, check the boxes and add a completion time
|
|
|
353
353
|
| `bun run tree` | Generate directory structure doc |
|
|
354
354
|
| `bun run format` | Auto-fix formatting (safe fixes only) |
|
|
355
355
|
| `bun run format:unsafe` | Also apply Biome's unsafe autofixes — review the diff; they can change behavior |
|
|
356
|
-
| `bun run test` | Run tests (Vitest — use `bun run test`, not `bun test`) |
|
|
356
|
+
| `bun run test` | Run tests (Vitest — use `bun run test`, not `bun test`). `vitest` is pinned at exactly `5.1.0` in `devDependencies`, because the forks pool in 5.1.1 calls `child.channel.unref()`, which Bun 1.4.4 does not implement, so every test file fails under `bun run test`; re-test on a newer Bun or Vitest before lifting the pin |
|
|
357
357
|
| `bun run start:stdio` | Production mode (stdio) |
|
|
358
358
|
| `bun run start:http` | Production mode (HTTP) |
|
|
359
359
|
| `bun run changelog:build` | Regenerate `CHANGELOG.md` from `changelog/*.md` |
|
|
@@ -366,7 +366,7 @@ When you complete a skill's checklist, check the boxes and add a completion time
|
|
|
366
366
|
|
|
367
367
|
## Bundling
|
|
368
368
|
|
|
369
|
-
`bun run bundle` produces a `.mcpb` extension bundle for one-click install in Claude Desktop. `mcpb pack` reads `.mcpbignore`, not `.gitignore`, so every root path the bundle must not ship — source, tests, docs, caches, logs, agent docs, plugin manifests, gitignored local files — needs a root-anchored line there (`/docs/`, never `docs/`, which also strips `node_modules/*/docs/`); `lint:packaging` names each missing or unanchored line. Root `skills/` ships on purpose. The pack step is followed by `scripts/clean-mcpb.ts`, which prunes dev dependencies (`mcpb clean`) and strips four classes of `node_modules/**` content that root-anchored `.mcpbignore` patterns cannot reach: dependency-shipped agent docs
|
|
369
|
+
`bun run bundle` produces a `.mcpb` extension bundle for one-click install in Claude Desktop. `mcpb pack` reads `.mcpbignore`, not `.gitignore`, so every root path the bundle must not ship — source, tests, docs, caches, logs, agent docs, plugin manifests, gitignored local files — needs a root-anchored line there (`/docs/`, never `docs/`, which also strips `node_modules/*/docs/`); `lint:packaging` names each missing or unanchored line. Root `skills/` ships on purpose. The pack step is followed by `scripts/clean-mcpb.ts`, which prunes dev dependencies (`mcpb clean`) and strips four classes of `node_modules/**` content that root-anchored `.mcpbignore` patterns cannot reach: dependency-shipped agent docs — `framework-skills/`, `skills/`, `.claude/`, `.agents/`, `AGENTS.md`, and `CLAUDE.md` at a package's root, and `SKILL.md` anywhere (a `skills/` deeper in a package, such as the MCP SDK's `dist/ext/skills/`, is runtime code and ships); platform-specific native bindings, which would otherwise lock the bundle to the platform it was packed on; node-gyp build output beside a `binding.gyp` (`config.gypi`, Makefiles, `obj.target/`, `.deps/`, object files and debug symbols), which records the packing machine's paths — compiled `*.node` addons stay; and build-only package files — the framework's `changelog/`, `scripts/`, `templates/`, and config bases (`biome.json`, `vitest.config.base.mjs`, `config/tsconfig.base.json`), and `better-sqlite3`'s `deps/` and `src/` C sources. MCPB is stdio-only — HTTP and Cloudflare Workers deployments are unaffected. Consumers who don't need it can delete `manifest.json` and `.mcpbignore`; `lint:packaging` skips cleanly.
|
|
370
370
|
|
|
371
371
|
**Adding an env var requires both files:** `server.json` (registry discovery, `environmentVariables[]`) and `manifest.json` (bundle install UX, `mcp_config.env` + `user_config`). `lint:packaging` (run by `devcheck`) verifies the env var names match, that every `user_config` option is wired into `mcp_config.env` as `"X": "${user_config.X}"` (the host substitutes nothing else — `"${X}"` reaches the server as that literal string), and that an optional string option carries `"default": ""`.
|
|
372
372
|
|
package/CLAUDE.md
CHANGED
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
# Developer Protocol
|
|
2
2
|
|
|
3
3
|
**Server:** @cyanheads/gbif-biodiversity-mcp-server
|
|
4
|
-
**Version:** 0.8.
|
|
5
|
-
**Framework:** [@cyanheads/mcp-ts-core](https://www.npmjs.com/package/@cyanheads/mcp-ts-core) `^0.13.
|
|
6
|
-
**Engines:** Bun ≥1.4.
|
|
4
|
+
**Version:** 0.8.2
|
|
5
|
+
**Framework:** [@cyanheads/mcp-ts-core](https://www.npmjs.com/package/@cyanheads/mcp-ts-core) `^0.13.22`
|
|
6
|
+
**Engines:** Bun ≥1.4.4, Node ≥24.0.0
|
|
7
7
|
**MCP SDK:** `@modelcontextprotocol/server` ^2.4.0
|
|
8
8
|
**Zod:** ^4.6.7
|
|
9
9
|
|
|
@@ -353,7 +353,7 @@ When you complete a skill's checklist, check the boxes and add a completion time
|
|
|
353
353
|
| `bun run tree` | Generate directory structure doc |
|
|
354
354
|
| `bun run format` | Auto-fix formatting (safe fixes only) |
|
|
355
355
|
| `bun run format:unsafe` | Also apply Biome's unsafe autofixes — review the diff; they can change behavior |
|
|
356
|
-
| `bun run test` | Run tests (Vitest — use `bun run test`, not `bun test`) |
|
|
356
|
+
| `bun run test` | Run tests (Vitest — use `bun run test`, not `bun test`). `vitest` is pinned at exactly `5.1.0` in `devDependencies`, because the forks pool in 5.1.1 calls `child.channel.unref()`, which Bun 1.4.4 does not implement, so every test file fails under `bun run test`; re-test on a newer Bun or Vitest before lifting the pin |
|
|
357
357
|
| `bun run start:stdio` | Production mode (stdio) |
|
|
358
358
|
| `bun run start:http` | Production mode (HTTP) |
|
|
359
359
|
| `bun run changelog:build` | Regenerate `CHANGELOG.md` from `changelog/*.md` |
|
|
@@ -366,7 +366,7 @@ When you complete a skill's checklist, check the boxes and add a completion time
|
|
|
366
366
|
|
|
367
367
|
## Bundling
|
|
368
368
|
|
|
369
|
-
`bun run bundle` produces a `.mcpb` extension bundle for one-click install in Claude Desktop. `mcpb pack` reads `.mcpbignore`, not `.gitignore`, so every root path the bundle must not ship — source, tests, docs, caches, logs, agent docs, plugin manifests, gitignored local files — needs a root-anchored line there (`/docs/`, never `docs/`, which also strips `node_modules/*/docs/`); `lint:packaging` names each missing or unanchored line. Root `skills/` ships on purpose. The pack step is followed by `scripts/clean-mcpb.ts`, which prunes dev dependencies (`mcpb clean`) and strips four classes of `node_modules/**` content that root-anchored `.mcpbignore` patterns cannot reach: dependency-shipped agent docs
|
|
369
|
+
`bun run bundle` produces a `.mcpb` extension bundle for one-click install in Claude Desktop. `mcpb pack` reads `.mcpbignore`, not `.gitignore`, so every root path the bundle must not ship — source, tests, docs, caches, logs, agent docs, plugin manifests, gitignored local files — needs a root-anchored line there (`/docs/`, never `docs/`, which also strips `node_modules/*/docs/`); `lint:packaging` names each missing or unanchored line. Root `skills/` ships on purpose. The pack step is followed by `scripts/clean-mcpb.ts`, which prunes dev dependencies (`mcpb clean`) and strips four classes of `node_modules/**` content that root-anchored `.mcpbignore` patterns cannot reach: dependency-shipped agent docs — `framework-skills/`, `skills/`, `.claude/`, `.agents/`, `AGENTS.md`, and `CLAUDE.md` at a package's root, and `SKILL.md` anywhere (a `skills/` deeper in a package, such as the MCP SDK's `dist/ext/skills/`, is runtime code and ships); platform-specific native bindings, which would otherwise lock the bundle to the platform it was packed on; node-gyp build output beside a `binding.gyp` (`config.gypi`, Makefiles, `obj.target/`, `.deps/`, object files and debug symbols), which records the packing machine's paths — compiled `*.node` addons stay; and build-only package files — the framework's `changelog/`, `scripts/`, `templates/`, and config bases (`biome.json`, `vitest.config.base.mjs`, `config/tsconfig.base.json`), and `better-sqlite3`'s `deps/` and `src/` C sources. MCPB is stdio-only — HTTP and Cloudflare Workers deployments are unaffected. Consumers who don't need it can delete `manifest.json` and `.mcpbignore`; `lint:packaging` skips cleanly.
|
|
370
370
|
|
|
371
371
|
**Adding an env var requires both files:** `server.json` (registry discovery, `environmentVariables[]`) and `manifest.json` (bundle install UX, `mcp_config.env` + `user_config`). `lint:packaging` (run by `devcheck`) verifies the env var names match, that every `user_config` option is wired into `mcp_config.env` as `"X": "${user_config.X}"` (the host substitutes nothing else — `"${X}"` reaches the server as that literal string), and that an optional string option carries `"default": ""`.
|
|
372
372
|
|
package/README.md
CHANGED
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
|
|
8
8
|
<div align="center">
|
|
9
9
|
|
|
10
|
-
[](./CHANGELOG.md) [](./LICENSE) [](https://github.com/users/cyanheads/packages/container/package/gbif-biodiversity-mcp-server) [](https://modelcontextprotocol.io/) [](https://www.npmjs.com/package/@cyanheads/gbif-biodiversity-mcp-server) [](https://www.typescriptlang.org/) [](https://bun.sh/)
|
|
11
11
|
|
|
12
12
|
</div>
|
|
13
13
|
|
|
@@ -35,26 +35,26 @@ Species taxonomy, occurrence records, datasets, and publishers from the Global B
|
|
|
35
35
|
|
|
36
36
|
| Tool | Description |
|
|
37
37
|
|:---|:---|
|
|
38
|
-
| `gbif_match_species` | Match a scientific name to the GBIF backbone, returning its taxon key, confidence, and classification |
|
|
39
|
-
| `gbif_bulk_match_species` | Match up to 50 scientific names in one call, one result per name in input order |
|
|
40
|
-
| `gbif_get_species` | Fetch a
|
|
41
|
-
| `gbif_search_species` | Search or browse the backbone by name fragment, rank, or a kingdom, family, or genus name |
|
|
38
|
+
| `gbif_match_species` | Match a scientific name to the GBIF backbone or the Catalogue of Life, returning its taxon key, confidence, and classification |
|
|
39
|
+
| `gbif_bulk_match_species` | Match up to 50 scientific names, each optionally narrowed to a kingdom, in one call, one result per name in input order |
|
|
40
|
+
| `gbif_get_species` | Fetch a taxon usage by key, from the backbone or any checklist: classification, authorship, synonymy, vernacular name, descendant count |
|
|
41
|
+
| `gbif_search_species` | Search or browse the backbone by name fragment, rank, taxonomic status, or a kingdom, family, or genus name |
|
|
42
42
|
| `gbif_get_species_classification` | Return a taxon's parent chain, root-first from kingdom to its immediate parent |
|
|
43
43
|
| `gbif_get_species_children` | List a taxon's direct children, such as the genera in a family or the species in a genus |
|
|
44
|
-
| `gbif_search_occurrences` | Search 3.9B+ occurrence records by taxon, place, date, basis of record, presence/absence, and IUCN category |
|
|
44
|
+
| `gbif_search_occurrences` | Search 3.9B+ occurrence records by taxon, place, date, basis of record, publishing organization, type status, establishment means, license, presence/absence, and IUCN category |
|
|
45
45
|
| `gbif_count_occurrences` | Count occurrences matching a filter without fetching records |
|
|
46
|
-
| `gbif_get_occurrence` | Fetch one
|
|
47
|
-
| `gbif_occurrence_facets` | Aggregate occurrence counts by country, year, dataset, taxon, status, and other dimensions, optionally naming taxon and
|
|
46
|
+
| `gbif_get_occurrence` | Fetch one Darwin Core occurrence record by key |
|
|
47
|
+
| `gbif_occurrence_facets` | Aggregate occurrence counts by country, year, dataset, taxon, status, and other dimensions, optionally naming taxon, dataset, publishing organization, and GADM area buckets |
|
|
48
48
|
| `gbif_search_datasets` | Search datasets by keyword, type, publishing country, or publishing or hosting organization |
|
|
49
|
-
| `gbif_get_dataset` | Fetch full dataset metadata by UUID: citation, contacts, license, DOI, publishing organization key, coverage |
|
|
49
|
+
| `gbif_get_dataset` | Fetch full dataset metadata by UUID: citation, contacts, license, DOI, publishing organization key, coverage with bounding boxes, deletion timestamp |
|
|
50
50
|
| `gbif_search_publishers` | Search GBIF-registered publishing organizations by name or country |
|
|
51
51
|
|
|
52
52
|
### Resources
|
|
53
53
|
|
|
54
54
|
| Resource | Description |
|
|
55
55
|
|:---|:---|
|
|
56
|
-
| `gbif://species/{taxonKey}` | Taxon record from the GBIF backbone: classification, authorship, synonymy status, vernacular name |
|
|
57
|
-
| `gbif://dataset/{datasetKey}` | Dataset metadata: title, description, citation, license, contacts, coverage, publishing organization key |
|
|
56
|
+
| `gbif://species/{taxonKey}` | Taxon usage record from the GBIF backbone or any checklist: classification, authorship, synonymy status, vernacular name |
|
|
57
|
+
| `gbif://dataset/{datasetKey}` | Dataset metadata: title, description, citation, license, contacts, coverage with bounding boxes, deletion timestamp, publishing organization key |
|
|
58
58
|
|
|
59
59
|
Both resources are also reachable via `gbif_get_species` and `gbif_get_dataset`; many MCP clients are tool-only and never surface resources.
|
|
60
60
|
|
|
@@ -68,56 +68,68 @@ Both resources are also reachable via `gbif_get_species` and `gbif_get_dataset`;
|
|
|
68
68
|
|
|
69
69
|
### `gbif_match_species` <sub>tool</sub>
|
|
70
70
|
|
|
71
|
-
- One scientific `name` (common names go to `gbif_search_species`), with optional `strict`, a `kingdom` to disambiguate,
|
|
72
|
-
- Returns `taxonKey`, the accepted taxon to pass to the occurrence tools, plus `matchedTaxonKey` when a synonym was resolved, `matchType` (`EXACT`, `FUZZY`, or `HIGHERRANK`: a match at a higher rank, such as a misspelled species falling back to its genus or kingdom, where `taxonKey` covers that whole taxon, or its accepted taxon when the taxon GBIF fell back to is a synonym, and a `notice` names it), `confidence` 0–100 (review below 80; a `HIGHERRANK` match can score above 90), and the classification with a key at each rank
|
|
71
|
+
- One scientific `name` (common names go to `gbif_search_species`), with optional `strict`, a `kingdom` to disambiguate, an expected `rank`, and a `checklistKey`
|
|
72
|
+
- Returns `taxonKey`, the accepted taxon to pass to the occurrence tools, plus `matchedTaxonKey` when a synonym was resolved and `acceptedName` (its canonical name, without authorship) whenever GBIF's answer names the accepted taxon, `matchType` (`EXACT`, `FUZZY`, or `HIGHERRANK`: a match at a higher rank, such as a misspelled species falling back to its genus or kingdom, where `taxonKey` covers that whole taxon, or its accepted taxon when the taxon GBIF fell back to is a synonym, and a `notice` names it), `confidence` 0–100 (review below 80; a `HIGHERRANK` match can score above 90), and the classification with a key at each rank
|
|
73
73
|
- `matchType` `NONE` fails as `no_match`, carrying GBIF's note when it gives one (for several equal matches, set `kingdom`); a blank `kingdom` fails as `invalid_filter`
|
|
74
|
+
- `checklistKey` is opt-in. Omitted, or `d7dddbf4-2cf0-4f39-9b2a-bb099caae36c`, matches the GBIF Backbone, whose integer keys the occurrence and species tools take; GBIF no longer updates it. `7ddf754f-d193-4cc9-b351-99906754a03b` matches the Catalogue of Life eXtended Release, the taxonomy GBIF now maintains, where a recently described or revised name can match exactly. Its keys come back as case-sensitive strings in `checklistTaxonKey` (and `checklistMatchedTaxonKey` for a synonym) with no `taxonKey`, `matchedTaxonKey`, or rank keys. The occurrence tools take one as `checklistTaxonKey` with the same `checklistKey`; the species tools, which take a numeric backbone `taxonKey`, do not. `status` may then be `PROVISIONALLY_ACCEPTED` and `matchType` `VARIANT`. The route is `GBIF_BASE_URL` with its trailing `/v1` replaced by `/v2`, so a base URL not ending in `/v1` fails the call as a configuration error
|
|
74
75
|
|
|
75
76
|
---
|
|
76
77
|
|
|
77
78
|
### `gbif_bulk_match_species` <sub>tool</sub>
|
|
78
79
|
|
|
79
|
-
- Scientific `names` with `strict
|
|
80
|
-
- Each result carries `name` and `matchType`, and on a match `taxonKey`, `matchedTaxonKey` (synonyms), and `confidence`; a `HIGHERRANK` row carries a `note` naming the higher taxon GBIF matched and what its `taxonKey` covers: that taxon, or its accepted taxon when it is a synonym. An unmatched name is `NONE`, with GBIF's explanation in `note` when it gives one (such as several equal matches for a name shared across kingdoms); a failed lookup is `ERROR` with `error` and, when classified, `reason`, and neither fails the batch
|
|
80
|
+
- Scientific `names` with `strict` and `checklistKey` (as on `gbif_match_species`, applied to the whole batch); the first 50 are processed in input order. Each entry is a name string or `{ name, kingdom }`, where the entry's `kingdom` applies to that name alone and resolves a name shared across kingdoms such as *Oenanthe* (a bird genus and a plant genus). A blank `kingdom` on any entry, the unprocessed tail included, fails the call as `invalid_filter`. With read-limit clamping enabled (default), extra entries are returned in `unprocessedNames` exactly as submitted, preserving order and duplicates for the next call
|
|
81
|
+
- Each result carries `name` and `matchType`, and on a match `taxonKey`, `matchedTaxonKey` and `acceptedName` (synonyms), and `confidence`; a `HIGHERRANK` row carries a `note` naming the higher taxon GBIF matched and what its `taxonKey` covers: that taxon, or its accepted taxon when it is a synonym. An unmatched name is `NONE`, with GBIF's explanation in `note` when it gives one (such as several equal matches for a name shared across kingdoms, with a pointer to resubmit the entry with `kingdom` while it has none); a failed lookup is `ERROR` with `error` and, when classified, `reason`, and neither fails the batch
|
|
81
82
|
|
|
82
83
|
---
|
|
83
84
|
|
|
84
85
|
### `gbif_get_species` <sub>tool</sub>
|
|
85
86
|
|
|
86
|
-
- One
|
|
87
|
-
- Returns the classification with rank keys, `authorship`, `vernacularName`, `numDescendants`, `publishedIn`, and `parentKey`; a `taxonomicStatus` of `SYNONYM` comes with `acceptedKey` and `accepted`. GBIF's taxon record carries no occurrence count: use `gbif_count_occurrences`
|
|
87
|
+
- One `taxonKey`, a non-negative integer (`0` is the backbone kingdom *incertae sedis*): a backbone key, or the taxon usage key of any checklist, such as a `gbif_search_species` row's `key`. A key no checklist has fails as `not_found`, one past the 32-bit range as `invalid_filter`, and a fraction or negative key fails at the schema
|
|
88
|
+
- Returns the classification with rank keys, `datasetKey` (the source checklist), `nubKey` (the mapped backbone key, the one the occurrence tools take as `taxonKey`; absent where the backbone has no mapping), `authorship`, `vernacularName`, `numDescendants`, `publishedIn`, and `parentKey`; `key`, the rank keys, `parentKey`, and `acceptedKey` are taxon usage keys of that checklist, equal to `nubKey` only on a backbone usage. A `taxonomicStatus` of `SYNONYM` comes with `acceptedKey` and `accepted`. GBIF's taxon record carries no occurrence count: use `gbif_count_occurrences` with `nubKey`
|
|
88
89
|
|
|
89
90
|
---
|
|
90
91
|
|
|
91
92
|
### `gbif_search_species` <sub>tool</sub>
|
|
92
93
|
|
|
93
|
-
- `q` name fragment (scientific and vernacular), `rank`, `isExtinct`, and a checklist `datasetKey` (omit for the backbone); up to 1,000 per page with integer `limit` and `offset`
|
|
94
|
-
- Taxa carry the checklist usage `key`, optional source `datasetKey` and mapped backbone `nubKey`, `rank`, `taxonomicStatus`, classification names, `vernacularName` (GBIF's own, else the first English vernacular name containing `q` when `q` is not part of the row's own scientific name, else the first English one), and `numDescendants`. `numOccurrences` appears only when GBIF supplies a positive value; its species search sends a `0` placeholder on every row, so count with `gbif_count_occurrences` on `nubKey` or a `SPECIES_KEY` facet. Enrichment reports `totalCount`, `endOfRecords`, and the `
|
|
95
|
-
- `
|
|
94
|
+
- `q` name fragment (scientific and vernacular), `rank`, `status`, `isExtinct`, and a checklist `datasetKey` (omit for the backbone); up to 1,000 per page with integer `limit` and `offset`, where `offset + limit` may not exceed 100,000
|
|
95
|
+
- Taxa carry the checklist usage `key`, optional source `datasetKey` and mapped backbone `nubKey`, `rank`, `taxonomicStatus`, classification names, `vernacularName` (GBIF's own, else the first English vernacular name containing `q` when `q` is not part of the row's own scientific name, else the first English one), and `numDescendants`. `numOccurrences` appears only when GBIF supplies a positive value; its species search sends a `0` placeholder on every row, so count with `gbif_count_occurrences` on `nubKey` or a `SPECIES_KEY` facet. Enrichment reports `totalCount`, `endOfRecords`, the `taxonScope` applied, and the `status` values applied. Occurrence queries use `nubKey` when supplied; otherwise resolve the name with `gbif_match_species`. Omitted `datasetKey` selects GBIF Backbone Taxonomy `d7dddbf4-2cf0-4f39-9b2a-bb099caae36c`
|
|
96
|
+
- `status` takes one or more of `ACCEPTED`, `DOUBTFUL`, `SYNONYM`, `HETEROTYPIC_SYNONYM`, `HOMOTYPIC_SYNONYM`, `PROPARTE_SYNONYM`, and `MISAPPLIED`, and a name matches when it carries any of them; `SYNONYM` matches only names whose status is exactly `SYNONYM`, not the heterotypic, homotypic, or pro parte forms. An empty list fails at the schema. `status: ["ACCEPTED"]` with `rank: "SPECIES"` and a `genus` lists that genus's accepted species
|
|
97
|
+
- `kingdom`, `family`, and `genus` take names, matched by their exact spelling in any letter case, never fuzzily; the narrowest one scopes, and `kingdom` beside a narrower one disambiguates it. An unknown name fails as `unresolved_taxon_scope`, a genus outside the named family as `conflicting_taxon_scope`, and a scope paired with a non-backbone `datasetKey` matches nothing. A blank filter or a malformed `datasetKey` fails as `invalid_filter`
|
|
98
|
+
- GBIF's species search serves nothing past an `offset + limit` of 100,000, whatever the query. The sum is checked on the applied `limit` before any request, and a larger one fails as `pagination_cap_exceeded`. When `totalCount` exceeds 100,000, every page carries a notice naming the ceiling and the way past it: narrow with `kingdom`, `family`, `genus`, `rank`, `status`, `isExtinct`, or `q`, or walk a subtree with `gbif_get_species_children`, which has no ceiling
|
|
96
99
|
|
|
97
100
|
---
|
|
98
101
|
|
|
99
102
|
### `gbif_get_species_classification` <sub>tool</sub>
|
|
100
103
|
|
|
101
|
-
- One `taxonKey
|
|
104
|
+
- One `taxonKey` (a backbone key or the taxon usage key of any checklist); returns `classification` root-first from kingdom to the immediate parent, each entry with `key`, `rank`, `name`, `scientificName`, `datasetKey`, and `nubKey`. The chain is read in the queried taxon's own checklist: 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
|
|
102
105
|
- The queried taxon is not included (use `gbif_get_species`); a root taxon returns an empty chain with a notice, an unknown key fails as `not_found`, one past the 32-bit range as `invalid_filter`, and a fraction or negative key fails at the schema
|
|
103
106
|
|
|
104
107
|
---
|
|
105
108
|
|
|
106
109
|
### `gbif_get_species_children` <sub>tool</sub>
|
|
107
110
|
|
|
108
|
-
- One `taxonKey` (a non-negative integer; `0` is the backbone's *incertae sedis* kingdom), up to 1,000 children per page with integer `limit` and `offset`; no filters. A fraction or negative value fails at the schema; an unknown key fails as `not_found`, one past GBIF's 32-bit range as `invalid_filter`
|
|
109
|
-
- Each child carries `key`, `canonicalName`, `rank`, `taxonomicStatus`, `vernacularName` when GBIF has one, and `numDescendants`; GBIF sends no occurrence count, so use `gbif_count_occurrences` with the child's `
|
|
111
|
+
- One `taxonKey` (a non-negative integer, a backbone key or the taxon usage key of any checklist; `0` is the backbone's *incertae sedis* kingdom), whose children are listed within its own checklist, up to 1,000 children per page with integer `limit` and `offset`; no filters. A fraction or negative value fails at the schema; an unknown key fails as `not_found`, one past GBIF's 32-bit range as `invalid_filter`
|
|
112
|
+
- Each child carries `key` (its taxon usage key in the parent's checklist), `datasetKey`, `nubKey` (the mapped backbone key, absent where the backbone has no mapping), `canonicalName`, `rank`, `taxonomicStatus`, `vernacularName` when GBIF has one, and `numDescendants`; GBIF sends no occurrence count, so use `gbif_count_occurrences` with the child's `nubKey`. GBIF reports no total, so `endOfRecords` (with `truncated` while more remain) is the continuation signal
|
|
110
113
|
- An empty later page gives offset-reset guidance; only an empty first page for an existing taxon means no direct children
|
|
111
114
|
|
|
112
115
|
---
|
|
113
116
|
|
|
114
117
|
### `gbif_search_occurrences` <sub>tool</sub>
|
|
115
118
|
|
|
116
|
-
- Filters: `taxonKey` (preferred; `scientificName` does
|
|
117
|
-
- `
|
|
118
|
-
-
|
|
119
|
-
-
|
|
120
|
-
-
|
|
119
|
+
- Filters: `taxonKey` (preferred: a key names exactly one taxon, where a `scientificName` shared across kingdoms, such as *Oenanthe*, matches nothing; `scientificName` does resolve synonyms), `checklistKey` with `checklistTaxonKey`, `country`, `publishingCountry`, `stateProvince`, `gadmGid`, a `decimalLatitude`/`decimalLongitude` box, WKT `geometry`, or `geoDistance` (a radius around a point), `elevation`, `depth`, `year`, `month` (one month or a range), `eventDate`, `basisOfRecord`, `hasCoordinate`, `hasGeospatialIssue`, `isInCluster`, `coordinateUncertaintyInMeters`, `datasetKey`, `publishingOrg`, `catalogNumber`, `institutionCode`, `recordedBy`, `mediaType`, `typeStatus`, `establishmentMeans`, `license`, `occurrenceStatus`, `iucnRedListCategory`; `includeMedia` adds each row's media; up to 300 per page
|
|
120
|
+
- `checklistKey` selects the taxonomy a taxon key is read in. Omitted, or `d7dddbf4-2cf0-4f39-9b2a-bb099caae36c`, is the GBIF Backbone and `taxonKey` takes its integer keys. Either value also leaves out the records GBIF has not matched to a taxon in that checklist, which a call with no `checklistKey` keeps. `7ddf754f-d193-4cc9-b351-99906754a03b` is the Catalogue of Life eXtended Release: scope by one of its keys with `checklistTaxonKey` (such as `3WSJV`, the key `gbif_match_species` returns under the same `checklistKey`), which matches the taxon and every descendant, as `taxonKey` does. A key holds uppercase letters and digits only and is matched case-sensitively; a digit-only one such as `8288` (the genus *Tringa*) is not the Backbone `taxonKey` of the same spelling. `checklistTaxonKey` without the Catalogue of Life `checklistKey`, and `taxonKey` with it, fail as `invalid_filter` before any request, since GBIF answers a key from the other taxonomy with zero records or an unrelated taxon. Rows keep their Backbone `taxonKey` either way
|
|
121
|
+
- `country`, `basisOfRecord`, `taxonKey`, and `checklistTaxonKey` each take one value or a non-empty array, and a record matching any one member matches (`country: ["ES", "PT"]` covers both countries, and a facet call ranks them as one scope). `taxonKey` and `checklistTaxonKey` take at most 100 members; an empty array fails at the schema, and each member passes the check a single value does. Different filters still intersect (a taxon key with `scientificName` excepted, below), and an array is echoed in `scope` as the array
|
|
122
|
+
- `gadmGid` is an uppercase GADM GID (`ESP.1_1`) GBIF derives from each record's coordinates, so records without coordinates match none; take one from a `GADM_LEVEL_0_GID`–`GADM_LEVEL_3_GID` facet or `gbif_get_occurrence`'s `gadm` field. `catalogNumber` and `institutionCode` match the whole value case-insensitively, `recordedBy` one collector exactly and case-sensitively (take a spelling from a `RECORDED_BY` facet), and `mediaType` is `StillImage`, `MovingImage`, `Sound`, or `InteractiveResource`. `limit` and `offset` are integers, `taxonKey` is an integer or an array of them, and `month` is an integer 1–12 or a string
|
|
123
|
+
- `publishingOrg` is the UUID of the organization that published the records, across all its datasets; take one from `gbif_search_publishers`, a dataset's or an occurrence record's `publishingOrganizationKey`, or a `PUBLISHING_ORG` facet. It is not the organization hosting the installation, and not `publishingCountry`
|
|
124
|
+
- `typeStatus` and `establishmentMeans` are matched case-insensitively against GBIF's TypeStatus (51 concepts) and EstablishmentMeans (7) vocabularies, then sent and echoed in the concept's own spelling. A value matches its concept and every narrower one: `Type` covers every kind of type, `Lectotype` covers `Isolectotype`, `native` covers `nativeEndemic` and `nativeReintroduced`, `introduced` covers `introducedAssistedColonisation`. A value naming no concept fails as `invalid_filter` listing them
|
|
125
|
+
- `license` is `CC0_1_0`, `CC_BY_4_0`, or `CC_BY_NC_4_0`; a blank or other value fails at the schema as `-32602`, not `invalid_filter`
|
|
126
|
+
- `hasGeospatialIssue: true` keeps records GBIF flagged with a spatial issue (zero coordinates, coordinates out of range, outside the stated country); `false` keeps unflagged ones. GBIF often drops the coordinates of a flagged record, so pair `false` with `hasCoordinate: true` for records to map
|
|
127
|
+
- All supplied spatial filters intersect: combining `geometry` or `geoDistance` with latitude or longitude ranges restricts results to their overlap
|
|
128
|
+
- `geoDistance` is `"latitude,longitude,distance"`, latitude first, with the distance ending in a lowercase `km` or `m` (`"38.17,-3.95,25km"` and `"38.17,-3.95,25000m"` are the same circle). The unit is required, because GBIF reads a distance with no unit as meters, so any other form fails as `invalid_filter`
|
|
129
|
+
- `decimalLatitude`, `decimalLongitude`, `coordinateUncertaintyInMeters`, `elevation`, and `depth` are ranges written `"min,max"`, both ends inclusive. A value without a comma is an exact match, not a range around it, and every result carries a notice saying so, with an example range per field (`decimalLatitude "38,39"`, `decimalLongitude "-4,-3"`, `coordinateUncertaintyInMeters "0,1000"` for within 1 km, `elevation "2000,*"` for 2,000 m and above, `depth "200,*"` for 200 m and deeper), listing only the fields the notice names. `coordinateUncertaintyInMeters`, `elevation`, and `depth` also take `*` for one open end (`"*,1000"`, `"2000,*"`); a bare `*`, padded or not, fails as `invalid_filter` on these and on `year`, `month`, and `eventDate`. A `*` end with whitespace between it and the comma (`"* ,1990"`, `"2020, *"`) also fails as `invalid_filter` on `coordinateUncertaintyInMeters`, `year`, `month`, `elevation`, and `depth`, and the message gives the corrected form (`"*,1990"`), because GBIF answers that spacing with HTTP 404 and an empty body, as it does a bare `*`; whitespace on the outer side of a `*` end (`" *,1990"`) or beside a number end (`"*, 1990"`, `"1990 ,*"`) is read by GBIF and forwarded, and `eventDate` with that spacing goes to GBIF, whose 400 names the value
|
|
130
|
+
- `year` is one year or a `"min,max"` range, `month` an integer 1–12 or a string holding one month or an ascending range (`"3,5"` for March through May, with no wrap past December), and `eventDate` is `YYYY`, `YYYY-MM`, or `YYYY-MM-DD`, each covering its whole period, or a range of any mix of them (`"2026-01-01,2026-06-30"`). `*` opens one end of each range (`"*,1990"`, `"2020,*"`), and any value, `"*,*"` included, drops records that carry no value for that field. GBIF rejects a time of day, a descending range, or an impossible date by name
|
|
131
|
+
- Records carry `key`, `taxonKey`, `taxonomicStatus`, coordinates, `eventDate` and `eventTime`, `basisOfRecord`, `occurrenceStatus`, `iucnRedListCategory`, `datasetKey`, `institutionCode`, `catalogNumber`, and `issues`, plus each of these where GBIF has it: `acceptedTaxonKey` and `acceptedScientificName` (the accepted taxon behind a synonym record, the name with authorship), `publishingOrganizationKey`, `license` (the record's Creative Commons URL; the `license` filter takes the code form), `rightsHolder`, `recordNumber` (the collector's number, not `catalogNumber`), `elevation` and `depth` in meters, and `typeStatus` and `establishmentMeans` (both go back unchanged to their filters). `occurrenceStatus` reads `DETECTED` or `NOT_DETECTED`, as GBIF serves it. With `includeMedia`, each row also carries every media item of its record as `{ type, identifier, license, rightsHolder }` in source order, whatever `mediaType` selected; it is off by default because it adds to both response surfaces. Enrichment reports `totalCount`, `endOfRecords`, and the `occurrenceStatus` applied
|
|
132
|
+
- Search, count and facets echo the same `scope`: effective supplied biological filters, with `occurrenceStatus` always included and pagination controls excluded. `ANY` is echoed but omitted upstream. `taxonKey` and `scientificName` combine with OR, so a name GBIF cannot resolve (one shared across kingdoms, or one it does not know) empties the combined query, the `taxonKey` records included; a zero then carries a notice saying so and naming two ways out: drop the name, or resolve it with `gbif_match_species` and add the returned key to the call's `taxonKey` (or `checklistTaxonKey`) array in place of the name. All 11 GBIF basis-of-record values are accepted, including `FOSSIL_SPECIMEN`, `OBSERVATION`, and `UNKNOWN`
|
|
121
133
|
- Latitude, longitude and coordinate uncertainty are independent optional facts; text renders each supplied value, including zero, in decimal degrees or meters
|
|
122
134
|
- `offset + limit` caps at 100,001 and GBIF has no cursor; a deeper request fails as `pagination_cap_exceeded`, and a larger match is reached by partitioning on a `DATASET_KEY` facet from `gbif_occurrence_facets`. A rejected filter value fails as `invalid_filter`
|
|
123
135
|
|
|
@@ -133,32 +145,33 @@ Both resources are also reachable via `gbif_get_species` and `gbif_get_dataset`;
|
|
|
133
145
|
### `gbif_get_occurrence` <sub>tool</sub>
|
|
134
146
|
|
|
135
147
|
- One `occurrenceKey` from a search result, a positive integer (a non-positive or fractional key is rejected at the schema); an unknown key fails as `not_found`
|
|
136
|
-
- The
|
|
148
|
+
- The Darwin Core record: `occurrenceStatus` (`NOT_DETECTED` is a survey that found nothing, not a sighting; the `occurrenceStatus` filter takes `ABSENT` or `NOT_DETECTED` for it), coordinates with `elevation` and `depth` in meters and, where the publisher gave them, `informationWithheld` and `dataGeneralizations` (the coordinates are coarser than observed on purpose), GADM levels 0–3 under `gadm`, dates with `eventTime` and `dateIdentified`, `taxonomicStatus`, the backbone key at every rank (`kingdomKey` through `speciesKey`), `acceptedTaxonKey` and `acceptedScientificName` (the accepted taxon behind a synonym record), `iucnRedListCategory`, institution, collection, and catalog codes, `datasetName`, `recordedBy`, `identifiedBy`, and `recordNumber`, `occurrenceRemarks`, `habitat`, `samplingProtocol`, `organismQuantity` with `organismQuantityType`, `typeStatus` and `establishmentMeans`, `license` (the Creative Commons URL), `rightsHolder`, and `publishingOrganizationKey` (goes into `publishingOrg`), `references` (the link to the source record), `isInCluster`, `media` with each item's `rightsHolder`, `identifiers`, and `issues`. Each field is omitted when GBIF sends none
|
|
137
149
|
|
|
138
150
|
---
|
|
139
151
|
|
|
140
152
|
### `gbif_occurrence_facets` <sub>tool</sub>
|
|
141
153
|
|
|
142
|
-
- `facet` is one of `COUNTRY`, `STATE_PROVINCE`, `YEAR`, `MONTH`, `BASIS_OF_RECORD`, `DATASET_KEY`, `PUBLISHING_COUNTRY`, `KINGDOM_KEY`, `PHYLUM_KEY`, `CLASS_KEY`, `ORDER_KEY`, `FAMILY_KEY`, `GENUS_KEY`, `SPECIES_KEY`, `OCCURRENCE_STATUS`, `IUCN_RED_LIST_CATEGORY`, `GADM_LEVEL_0_GID`–`GADM_LEVEL_3_GID`, `INSTITUTION_CODE`, `MEDIA_TYPE`, `RECORDED_BY`; up to 100 values per page (`facetLimit`, default 10), paged with `facetOffset`
|
|
154
|
+
- `facet` is one of `COUNTRY`, `STATE_PROVINCE`, `YEAR`, `MONTH`, `BASIS_OF_RECORD`, `DATASET_KEY`, `PUBLISHING_COUNTRY`, `KINGDOM_KEY`, `PHYLUM_KEY`, `CLASS_KEY`, `ORDER_KEY`, `FAMILY_KEY`, `GENUS_KEY`, `SPECIES_KEY`, `OCCURRENCE_STATUS`, `IUCN_RED_LIST_CATEGORY`, `GADM_LEVEL_0_GID`–`GADM_LEVEL_3_GID`, `INSTITUTION_CODE`, `MEDIA_TYPE`, `RECORDED_BY`, `PUBLISHING_ORG`, `TYPE_STATUS`, `ESTABLISHMENT_MEANS`, `LICENSE`; up to 100 values per page (`facetLimit`, default 10), paged with `facetOffset`
|
|
143
155
|
- Accepts every biological filter listed for `gbif_search_occurrences`, with the same constraints and spatial intersection. Repeat them on the facet call and each partition search to preserve the population. Returns `totalOccurrences` and `counts` ranked by count; a rejected scope value fails as `invalid_filter`
|
|
144
|
-
- Each facet request fetches one extra bucket to prove continuation. `truncated`, `shown`, and `cap` appear only when that bucket exists; advance `facetOffset` by the exposed page size. An exactly full final page carries no truncation flag. Empty later pages give offset-reset guidance; an empty first page distinguishes zero matching occurrences from a dimension with no data
|
|
145
|
-
- `DATASET_KEY` buckets sum to the scope's full total, so it is the facet for partitioning a search too large to page; `YEAR`, `MONTH`, `STATE_PROVINCE`, `SPECIES_KEY`, `INSTITUTION_CODE`, `MEDIA_TYPE`, and `
|
|
146
|
-
- `includeLabels: true` names each bucket on a `KINGDOM_KEY`–`SPECIES_KEY` or `
|
|
156
|
+
- Each facet request fetches one extra bucket to prove continuation. `truncated`, `shown`, and `cap` appear only when that bucket exists; advance `facetOffset` by the exposed page size. GBIF pages a ranking only so far: `facetOffset + facetLimit` may reach 1,199,999 on any scope, past which the call fails as `pagination_cap_exceeded` before any request, and 500,000 on a scope ranking more than 500,001 buckets, where GBIF refuses a deeper page and the call fails the same way; when the next page at the same `facetLimit` would reach past position 500,001 (the lookahead bucket counts), the continuation notice names the `facetLimit` that lands the next page exactly on it, and that page carries a notice in place of a continuation, with `truncated` still set, so a walk at any `facetLimit` ends at position 500,001. To rank buckets past either, narrow the scope with filters (`taxonKey` of a class or order, `country`, `year`, `basisOfRecord`, or a `datasetKey` from a `DATASET_KEY` facet) and page each narrower scope from 0. An exactly full final page carries no truncation flag. Empty later pages give offset-reset guidance; an empty first page distinguishes zero matching occurrences from a dimension with no data
|
|
157
|
+
- `DATASET_KEY` buckets sum to the scope's full total, so it is the facet for partitioning a search too large to page; `YEAR`, `MONTH`, `STATE_PROVINCE`, `SPECIES_KEY`, `INSTITUTION_CODE`, `MEDIA_TYPE`, `RECORDED_BY`, `TYPE_STATUS`, and `ESTABLISHMENT_MEANS` drop records that lack the field, and the GADM levels drop records without coordinates or outside every GADM unit at that level. `MEDIA_TYPE` and `RECORDED_BY` buckets overlap (a record with two media types or two collectors counts in each), and so do `TYPE_STATUS` and `ESTABLISHMENT_MEANS` (a record counts under its concept and every broader one: an `Isolectotype` also under `Lectotype` and `Type`), so their sums can exceed `totalOccurrences`. `INSTITUTION_CODE` buckets come back lowercased and `institutionCode` takes them unchanged; `PUBLISHING_ORG`, `TYPE_STATUS`, `ESTABLISHMENT_MEANS`, and `LICENSE` buckets go back unchanged as `publishingOrg`, `typeStatus`, `establishmentMeans`, and `license`, and `GADM_LEVEL_*_GID` buckets as `gadmGid`. `OCCURRENCE_STATUS` buckets read `DETECTED` and `NOT_DETECTED`, which the `occurrenceStatus` filter takes unchanged. `KINGDOM_KEY`–`SPECIES_KEY` buckets are Backbone keys for `taxonKey`, or, under the Catalogue of Life `checklistKey`, Catalogue of Life keys for `checklistTaxonKey`. Pass `facet: OCCURRENCE_STATUS` with `occurrenceStatus: ANY` for the presence/absence split
|
|
158
|
+
- `includeLabels: true` names each bucket on a `KINGDOM_KEY`–`SPECIES_KEY`, `DATASET_KEY`, `PUBLISHING_ORG`, or `GADM_LEVEL_0_GID`–`GADM_LEVEL_3_GID` page: `counts[].label` is the taxon's `canonicalName`, the dataset `title`, the organization `title`, or the administrative area's `name`. Taxon buckets are looked up in the taxonomy `checklistKey` selects, never by the shape of the key, since `8288` is a Catalogue of Life genus and a Backbone family. It costs one GBIF request per exposed bucket (never the lookahead), at most 8 in flight server-wide, no retries, and one 10 s deadline per page; a bucket whose lookup fails, finds no name, or misses it has no `label` and is counted in `notice`, which points an unlabeled GADM bucket at `gbif_get_occurrence`'s `gadm` field. Other dimensions ignore it, and without it a facet call is one request. Labeling Catalogue of Life buckets reads the `/v2` route, so a `GBIF_BASE_URL` not ending in `/v1` fails that call as a configuration error
|
|
147
159
|
|
|
148
160
|
---
|
|
149
161
|
|
|
150
162
|
### `gbif_search_datasets` <sub>tool</sub>
|
|
151
163
|
|
|
152
|
-
- Filters: `q`, `type` (`OCCURRENCE`, `CHECKLIST`, `METADATA`, `SAMPLING_EVENT`), `publishingCountry`, `publishingOrg`, `hostingOrg`; up to 1,000 per page
|
|
164
|
+
- Filters: `q`, `type` (`OCCURRENCE`, `CHECKLIST`, `METADATA`, `SAMPLING_EVENT`), `publishingCountry`, `publishingOrg`, `hostingOrg`; up to 1,000 per page, where `offset + limit` may not exceed 125,000
|
|
153
165
|
- Returns `key`, `title`, `type`, `license`, `doi`, `recordCount`, `publishingOrganizationKey` and `publishingOrganizationTitle`, and a 300-character `description` preview, with `descriptionTruncated` flagging a cut (`gbif_get_dataset` has the full text). `publishingOrganizationKey` goes back in as `publishingOrg`. `limit` and `offset` are integers
|
|
154
166
|
- `publishingOrg` matches the organization whose data it is and is the usual chain from `gbif_search_publishers`; `hostingOrg` matches the organization whose installation serves it, and the two together intersect. Both take the lowercase UUID form; anything else, like any rejected filter value, fails as `invalid_filter`
|
|
167
|
+
- GBIF's dataset search serves nothing past an `offset + limit` of 125,000. The sum is checked on the applied `limit` before any request, and a larger one fails as `pagination_cap_exceeded`. When `totalCount` exceeds 125,000, every page carries a notice naming the ceiling and the way past it: `type` splits the index with no gap or overlap, since every dataset has exactly one of the four types, and `q`, `publishingCountry`, `publishingOrg`, and `hostingOrg` narrow it further
|
|
155
168
|
|
|
156
169
|
---
|
|
157
170
|
|
|
158
171
|
### `gbif_get_dataset` <sub>tool</sub>
|
|
159
172
|
|
|
160
173
|
- One `datasetKey` UUID and `contactLimit` (default 10, max 100; `0` drops contact detail but keeps `contactsTotal`); a malformed key fails as `invalid_filter`, an unknown one as `not_found`
|
|
161
|
-
- Returns `description`, `citationText`, `license`, `doi`, `publishingOrganizationKey` (goes into `gbif_search_datasets` as `publishingOrg`; the detail record carries no organization name), `recordCount`, `numConstituents`, `contacts` with `contactsTotal` and `contactsReturned`, `temporalCoverages`, and `
|
|
174
|
+
- Returns `description`, `citationText`, `license`, `doi`, `publishingOrganizationKey` (goes into `gbif_search_datasets` as `publishingOrg`; the detail record carries no organization name), `recordCount`, `numConstituents`, `contacts` with `contactsTotal` and `contactsReturned`, `temporalCoverages`, `geographicCoverages` (each a description, a `boundingBox` as GBIF sends it, or both; a `minLongitude` above `maxLongitude` is a box crossing the antimeridian), and `deleted`, GBIF's timestamp for a dataset it no longer publishes (it is then not searchable and GBIF indexes none of its occurrences; absent on a published dataset)
|
|
162
175
|
|
|
163
176
|
---
|
|
164
177
|
|
|
@@ -166,14 +179,14 @@ Both resources are also reachable via `gbif_get_species` and `gbif_get_dataset`;
|
|
|
166
179
|
|
|
167
180
|
- `q` name fragment and `country` (alpha-2 or alpha-3, any case); up to 1,000 per page with integer `limit` and `offset`
|
|
168
181
|
- Returns organization `key`, `title`, `country`, and `city`; the key chains into `gbif_search_datasets` as `publishingOrg`
|
|
169
|
-
- A blank `q`, an empty `country`, or a country GBIF cannot parse fails as `invalid_filter`
|
|
182
|
+
- A blank `q`, an empty `country`, or a country GBIF cannot parse fails as `invalid_filter`. Besides the codes, GBIF parses its own enum name for a country (`UNITED_KINGDOM`, or `United Kingdom`), but no other name: `Britain`, `UK`, and numeric codes fail
|
|
170
183
|
|
|
171
184
|
---
|
|
172
185
|
|
|
173
186
|
### `gbif://species/{taxonKey}` <sub>resource</sub>
|
|
174
187
|
|
|
175
|
-
- Taxon record as `application/json`: classification names, `authorship`, `vernacularName`, `taxonomicStatus` with `acceptedKey` and `accepted`, `numDescendants`
|
|
176
|
-
- `taxonKey` is a whole signed decimal integer within the signed 32-bit range; `0` is the backbone kingdom *incertae sedis*. The segment is URI-decoded once and surrounding whitespace is trimmed; leading `+`, zero padding and their percent-encoded equivalents are accepted. An unknown key fails as `not_found`; malformed escapes, suffixes, fractions, exponents, hexadecimal forms, embedded whitespace and out-of-range values fail as `invalid_filter` before a request. Use a backbone key from `gbif_match_species` or a
|
|
188
|
+
- Taxon usage record as `application/json`: classification names, `authorship`, `vernacularName`, `taxonomicStatus` with `acceptedKey` and `accepted`, `numDescendants`, `datasetKey` (the source checklist), and `nubKey` (the mapped backbone key the occurrence tools take); `key` and `acceptedKey` are taxon usage keys of that checklist
|
|
189
|
+
- `taxonKey` is a whole signed decimal integer within the signed 32-bit range; `0` is the backbone kingdom *incertae sedis*. The segment is URI-decoded once and surrounding whitespace is trimmed; leading `+`, zero padding and their percent-encoded equivalents are accepted. An unknown key fails as `not_found`; malformed escapes, suffixes, fractions, exponents, hexadecimal forms, embedded whitespace and out-of-range values fail as `invalid_filter` before a request. Use a backbone key from `gbif_match_species` or a taxon usage key of any checklist, such as a search result's `key`
|
|
177
190
|
|
|
178
191
|
---
|
|
179
192
|
|
|
@@ -188,20 +201,21 @@ Built on [`@cyanheads/mcp-ts-core`](https://github.com/cyanheads/mcp-ts-core): s
|
|
|
188
201
|
|
|
189
202
|
GBIF-specific:
|
|
190
203
|
|
|
191
|
-
- GBIF API v1 species, occurrence, dataset, and
|
|
204
|
+
- GBIF API v1 species, occurrence, dataset, organization, and GADM endpoints, plus v2 species matching for the Catalogue of Life, keyless, with an identifying `User-Agent` on every request
|
|
192
205
|
- Synonym-safe keys: `gbif_match_species` resolves a synonym to its accepted taxon, and the occurrence tools filter on that `taxonKey`
|
|
193
|
-
-
|
|
194
|
-
-
|
|
195
|
-
-
|
|
206
|
+
- Opt-in Catalogue of Life matching: `checklistKey` on both match tools matches against the Catalogue of Life eXtended Release and returns string keys in separate fields, and the occurrence tools take them as `checklistTaxonKey`, so a Catalogue of Life key never lands in a backbone integer field
|
|
207
|
+
- Sightings by default: the search, count, and facet tools default `occurrenceStatus` to `PRESENT`, excluding absence records. Records and facet buckets read `DETECTED` and `NOT_DETECTED`, which the filter takes as well as `PRESENT` and `ABSENT`. Dataset `recordCount` spans every status, so it can exceed a `gbif_count_occurrences` total for the same key
|
|
208
|
+
- Strict country codes: `country` (where a record was observed) and `publishingCountry` (the publisher's country) on the occurrence tools, and `publishingCountry` on `gbif_search_datasets`, accept only uppercase ISO 3166-1 alpha-2, because lowercase and alpha-3 forms silently match nothing there and a country name such as `Britain` draws a 400 upstream. `stateProvince` matches verbatim and case-sensitively, so take values from a `STATE_PROVINCE` facet
|
|
209
|
+
- Blank filters rejected: GBIF reads an empty parameter as no filter, so an optional filter sent blank or whitespace-only fails as `invalid_filter` instead of widening the query. The exception is a blank `country` or `publishingCountry` on the occurrence tools, or a blank `publishingCountry` on `gbif_search_datasets`, which fails earlier at the uppercase pattern as `-32602 invalid_arguments`, as does a blank or unknown `license` at its enum. Omit a field to leave it off
|
|
196
210
|
|
|
197
211
|
Agent-friendly output:
|
|
198
212
|
|
|
199
|
-
- Scope echo: enrichment reports `totalCount`, `endOfRecords`, the `occurrenceStatus` applied, and the resolved `taxonScope`, with notices on empty results, over-cap totals, and a `stateProvince`, `gadmGid`, or `recordedBy` that matched nothing
|
|
213
|
+
- Scope echo: enrichment reports `totalCount`, `endOfRecords`, the `occurrenceStatus` applied, and the resolved `taxonScope`, with notices on empty results, over-cap totals, and a `scientificName`, `stateProvince`, `gadmGid`, or `recordedBy` that matched nothing
|
|
200
214
|
- Graceful partial failure: `gbif_bulk_match_species` returns a `NONE` or `ERROR` row per name instead of failing the batch
|
|
201
|
-
- Typed errors: `invalid_filter`, `not_found`, `no_match`, `unresolved_taxon_scope`, `conflicting_taxon_scope`, and `pagination_cap_exceeded`, each with a recovery hint
|
|
215
|
+
- Typed errors: `invalid_filter`, `not_found`, `no_match`, `unresolved_taxon_scope`, `conflicting_taxon_scope`, and `pagination_cap_exceeded` (on `gbif_search_occurrences`, `gbif_occurrence_facets`, `gbif_search_species`, and `gbif_search_datasets`), each with a recovery hint
|
|
202
216
|
- Sparse fields omitted rather than null-filled: `extinct` appears only on taxa GBIF explicitly flags
|
|
203
|
-
- Dataset metadata preserves temporal ranges, single dates, and verbatim periods such as `1975-current
|
|
204
|
-
- Publisher descriptions retain paragraph breaks and decode numeric character references once; Markdown output renders publisher text literally
|
|
217
|
+
- Dataset metadata preserves temporal ranges, single dates, and verbatim periods such as `1975-current`, and geographic coverage bounding boxes as GBIF sends them; unsupported coverage entries are disclosed. A deleted dataset carries its `deleted` timestamp. An unavailable supplementary record count carries `recordCountNotice` while retaining metadata
|
|
218
|
+
- Publisher descriptions retain paragraph breaks and decode numeric character references once; Markdown output renders publisher text literally, in dataset and occurrence output alike. A value containing Markdown or character-reference syntax appears in `content[]` as numeric character references (`&#NN;`) standing for one character each, never part of the value; `structuredContent` carries every string as GBIF sent it. An http(s) URL in an occurrence record (`occurrenceID`, `references`, a media or `identifiers` entry) renders as a link whose text is the URL, and any other value as escaped text
|
|
205
219
|
|
|
206
220
|
## Getting started
|
|
207
221
|
|
|
@@ -281,7 +295,7 @@ MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http
|
|
|
281
295
|
|
|
282
296
|
### Prerequisites
|
|
283
297
|
|
|
284
|
-
- [Bun v1.4.
|
|
298
|
+
- [Bun v1.4.4](https://bun.sh/) or higher (or Node.js v24+).
|
|
285
299
|
- No credentials: the GBIF endpoints this server calls are public.
|
|
286
300
|
|
|
287
301
|
### Installation
|
|
@@ -315,7 +329,7 @@ cp .env.example .env
|
|
|
315
329
|
|
|
316
330
|
| Variable | Description | Default |
|
|
317
331
|
|:---|:---|:---|
|
|
318
|
-
| `GBIF_BASE_URL` | GBIF API base URL. | `https://api.gbif.org/v1` |
|
|
332
|
+
| `GBIF_BASE_URL` | GBIF API base URL. Keep the trailing `/v1`: `checklistKey` on the match tools, and `includeLabels` on `gbif_occurrence_facets` under the Catalogue of Life `checklistKey`, call the `/v2` route derived by replacing it, and fail as a configuration error without it. | `https://api.gbif.org/v1` |
|
|
319
333
|
| `GBIF_CLAMP_READ_LIMITS` | Clamp oversized whole-number read limits to the documented caps and disclose requested/applied values. Bulk matching processes the first 50 names and returns the remainder in `unprocessedNames`. Set `false` to advertise and enforce rejecting maxima instead. Strict boolean parsing rejects malformed values. | `true` |
|
|
320
334
|
| `GBIF_REQUEST_TIMEOUT_MS` | Per-request HTTP timeout, in ms. | `10000` |
|
|
321
335
|
| `GBIF_USER_AGENT` | `User-Agent` sent on every GBIF request. GBIF asks integrators to identify themselves with a contact URL or email. | server name, version, and repository URL |
|
package/changelog/0.8.x/0.8.0.md
CHANGED
|
@@ -18,7 +18,7 @@ security: false
|
|
|
18
18
|
## Changed
|
|
19
19
|
|
|
20
20
|
- **22 numeric inputs are now integer-typed** — `taxonKey` (6 tools), `occurrenceKey`, `limit` and `offset` (5 paged tools), `facetLimit`, `facetOffset`, `month` (3 occurrence tools). Fractions, negative `taxonKey`, non-positive `occurrenceKey`, and integers past 2^53−1 now fail as `invalid_arguments` before any request; previously fractions were sent upstream or clamped, and values past 2^53−1 clamped. Over-cap integers still clamp. ([#75](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/75))
|
|
21
|
-
- **`gbif_match_species` and `gbif_bulk_match_species` disclose `HIGHERRANK` matches** — a `notice` (single) or per-row `note` (bulk) names the matched rank and taxon and says `taxonKey` covers
|
|
21
|
+
- **`gbif_match_species` and `gbif_bulk_match_species` disclose `HIGHERRANK` matches** — a `notice` (single) or per-row `note` (bulk) names the matched rank and taxon and says what `taxonKey` covers — that whole taxon, or its accepted taxon when the fallback taxon is a synonym; GBIF's ambiguity note on a `NONE` surfaces in the `no_match` message and bulk row. `taxonKey` values are unchanged. ([#73](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/73))
|
|
22
22
|
- **`gbif_search_species` omits `numOccurrences`** unless GBIF supplies a positive value, and `vernacularName` now comes from the row's English `vernacularNames[]` entries. ([#74](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/74))
|
|
23
23
|
- **`.mcpb` bundle cleaner** also strips node-gyp build output and build-only package files, and `.mcpbignore` lists every root dev path.
|
|
24
24
|
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
---
|
|
2
|
+
summary: "Catalogue of Life eXtended Release keys on the match and occurrence tools, new occurrence filters and facets, richer occurrence records, per-name kingdoms in bulk matching, and offset ceilings on species and dataset search."
|
|
3
|
+
breaking: false
|
|
4
|
+
security: false
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# 0.8.1 — 2026-11-12
|
|
8
|
+
|
|
9
|
+
## Added
|
|
10
|
+
|
|
11
|
+
- **`checklistKey` on `gbif_match_species` and `gbif_bulk_match_species`** (opt-in) selects the Catalogue of Life eXtended Release, `7ddf754f-d193-4cc9-b351-99906754a03b`, the taxonomy GBIF now maintains in place of the frozen Backbone. Matches return string keys as `checklistTaxonKey` / `checklistMatchedTaxonKey`; `taxonKey` is absent. The `/v2` route is derived from a `GBIF_BASE_URL` ending in `/v1`, and any other base fails as a ConfigurationError. ([#89](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/89))
|
|
12
|
+
- **`checklistKey` + `checklistTaxonKey` on the occurrence tools** scope by a Catalogue of Life key (sent upstream as `taxonKey`). `taxonKey` is rejected alongside them, and `KINGDOM_KEY` … `SPECIES_KEY` bucket labels follow `checklistKey`, never key shape. ([#90](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/90))
|
|
13
|
+
- **`publishingOrg`, `hasGeospatialIssue`, `typeStatus`, `establishmentMeans`, and `license` filters** on the occurrence tools, and `PUBLISHING_ORG`, `TYPE_STATUS`, `ESTABLISHMENT_MEANS`, and `LICENSE` facets, with `PUBLISHING_ORG` bucket labels. `typeStatus` and `establishmentMeans` are canonicalized against GBIF's vocabularies and match narrower concepts too. ([#86](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/86))
|
|
14
|
+
- **`gbif_get_occurrence` and every `gbif_search_occurrences` row** carry `license`, `rightsHolder`, `publishingOrganizationKey`, `acceptedTaxonKey`, `acceptedScientificName`, `recordNumber`, `elevation`, `depth`, `typeStatus`, and `establishmentMeans`; media items carry `rightsHolder`. `gbif_search_occurrences` returns media only with the new `includeMedia`. ([#87](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/87))
|
|
15
|
+
- **`gbif_bulk_match_species` entries** are a name string or `{ name, kingdom }`, and `unprocessedNames` returns entries as submitted. A blank entry `kingdom` fails as `invalid_filter`. ([#81](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/81))
|
|
16
|
+
- **`acceptedName` on synonym matches** from `gbif_match_species` and `gbif_bulk_match_species`, read from the match response with no extra request. ([#85](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/85))
|
|
17
|
+
- **`gbif_occurrence_facets` `includeLabels`** names `GADM_LEVEL_0_GID` … `GADM_LEVEL_3_GID` buckets; a bucket whose lookup returns an empty 200 stays unlabeled. ([#88](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/88))
|
|
18
|
+
- **`occurrenceStatus`** on the occurrence tools also takes `DETECTED` and `NOT_DETECTED`, the names GBIF serves on records and `OCCURRENCE_STATUS` buckets, sent and echoed as given. The default stays `PRESENT`.
|
|
19
|
+
- **A `scientificName` filter that matches nothing** returns a notice naming the cross-kingdom-homonym reading and the `gbif_match_species` + `kingdom` route.
|
|
20
|
+
|
|
21
|
+
## Changed
|
|
22
|
+
|
|
23
|
+
- **`.mcpb` bundle cleaner** also strips `AGENTS.md` and `CLAUDE.md` at any dependency's root and `SKILL.md` files anywhere under `node_modules/`.
|
|
24
|
+
|
|
25
|
+
## Fixed
|
|
26
|
+
|
|
27
|
+
- **`gbif_search_species` and `gbif_search_datasets` check `offset + limit` against GBIF's ceilings** (100,000 and 125,000) on the applied limit before any request, failing as `pagination_cap_exceeded` instead of a retried 500 or a blank-filter error. A total past the ceiling draws a notice naming the narrowing routes. ([#84](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/84))
|
|
28
|
+
- **A comma-less `decimalLatitude`, `decimalLongitude`, or `coordinateUncertaintyInMeters`** matches only that exact value and now draws a notice on every result, across search, count, and facets. A bare `*` (padded too) fails as `invalid_filter` instead of GBIF's bare 404. ([#83](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/83))
|
|
29
|
+
- **`scientificName` descriptions** no longer claim the filter misses synonyms; it resolves them.
|
|
30
|
+
- **`gbif_bulk_match_species`** escapes the markdown heading of each name, and its per-name catch rethrows caller cancellation and ConfigurationError instead of recording them as per-name errors.
|
|
31
|
+
- **`gbif_occurrence_facets` `includeLabels` under the Catalogue of Life** refuses a non-`/v1` `GBIF_BASE_URL` before the aggregation request.
|
|
32
|
+
|
|
33
|
+
## Dependencies
|
|
34
|
+
|
|
35
|
+
- `@cyanheads/mcp-ts-core` ^0.13.18 → ^0.13.22 (GBIF's error body no longer rides on `error.data`; its explanation is still folded into the error message).
|
|
36
|
+
- `@biomejs/biome` ^2.6.4 → ^2.6.6.
|
|
37
|
+
- `tsc-alias` ^1.9.9 → ^1.9.10.
|
|
38
|
+
- `vitest` ^5.0.5 → ^5.1.0.
|
|
39
|
+
- `engines.bun` >=1.4.0 → >=1.4.4.
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
---
|
|
2
|
+
summary: "New occurrence filters (eventDate, geoDistance, elevation, depth, month ranges, array values), a species status filter, and richer occurrence and dataset records; facet paging ceilings, a bare * year, and checklist usage keys now report correctly."
|
|
3
|
+
breaking: false
|
|
4
|
+
security: false
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# 0.8.2 — 2026-11-19
|
|
8
|
+
|
|
9
|
+
## Added
|
|
10
|
+
|
|
11
|
+
- **`status` on `gbif_search_species`** filters by one or more taxonomic statuses (`ACCEPTED`, `DOUBTFUL`, `SYNONYM`, and four more), OR-ed, and echoes the applied values as a `status` enrichment key. ([#96](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/96))
|
|
12
|
+
- **`eventDate`, `geoDistance`, `elevation`, and `depth` filters** on the occurrence tools, and `month` also takes a `"min,max"` range. A bare `*` is refused as `year`'s is, and `geoDistance` must end in a lowercase `km` or `m`. ([#97](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/97))
|
|
13
|
+
- **`country`, `basisOfRecord`, `taxonKey`, and `checklistTaxonKey`** on the occurrence tools take an array, OR-ed by GBIF (`taxonKey` and `checklistTaxonKey` up to 100 members); `scope` echoes the array. ([#98](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/98))
|
|
14
|
+
- **`gbif_get_occurrence`** returns `informationWithheld`, `dataGeneralizations`, `references`, `occurrenceRemarks`, `habitat`, `samplingProtocol`, `datasetName`, `organismQuantity`, `organismQuantityType`, `dateIdentified`, `isInCluster`, and the `kingdomKey` … `speciesKey` rank keys. Its text fields are escaped in `content[]` and `references` renders as a link. ([#99](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/99))
|
|
15
|
+
|
|
16
|
+
## Changed
|
|
17
|
+
|
|
18
|
+
- **`checklistKey` description** states that either value leaves out the records GBIF has not matched to a taxon in that checklist.
|
|
19
|
+
- **`scientificName` descriptions** on the occurrence tools state that the name combines with a taxon key as a union, and what an unresolvable name does.
|
|
20
|
+
|
|
21
|
+
## Fixed
|
|
22
|
+
|
|
23
|
+
- **`gbif_occurrence_facets` fails as `pagination_cap_exceeded`** past position 1,200,000, before any request (was `invalid_filter`), and past 500,001 on a scope ranking more buckets (was a reasonless `-32001` HTTP 404). The page landing on 500,001 carries a notice, not a continuation, and a continuation that would cross it names the `facetLimit` that lands on it. ([#91](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/91))
|
|
24
|
+
- **A bare `*` as `year`** fails as `invalid_filter` naming the open-ended forms; 0.8.1 sent it to GBIF, which answered a `-32001` HTTP 404. ([#93](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/93))
|
|
25
|
+
- **`gbif_get_species`, `gbif_get_species_children`, `gbif_get_species_classification`, and `gbif://species/{taxonKey}`** now return `nubKey` and `datasetKey` beside a checklist usage `key`, and no longer describe usage keys as backbone keys; `nubKey` is the key the occurrence tools take, absent where the backbone has no mapping. ([#94](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/94))
|
|
26
|
+
- **`gbif_get_dataset` and `gbif://dataset/{datasetKey}`** return `deleted` for a dataset GBIF has deleted, and each coverage's `boundingBox`; a coverage with a box and no description is kept. ([#95](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/95))
|
|
27
|
+
- **`gbif_search_species` descriptions** no longer require capitalized `kingdom`, `family`, and `genus` names, and the `gbif_search_publishers` `country` recovery names the forms GBIF parses: alpha-3 codes and its own country names. ([#100](https://github.com/cyanheads/gbif-biodiversity-mcp-server/issues/100))
|
|
28
|
+
- **`iucnRedListCategory`** accepts `NE` (Not Evaluated), which 0.8.1 rejected.
|
|
29
|
+
- **A `scientificName` GBIF cannot resolve, sent beside a taxon key,** empties the query; the zero's notice now names the name as the cause, where 0.8.1 printed the notice for a name sent alone.
|
|
30
|
+
- **`gbif_get_occurrence` and `gbif_search_occurrences`** escape publisher-written text in `content[]`, `eventTime` included, and render an http(s) media URL as a link, as `gbif_get_occurrence` also does for `occurrenceID` and identifier URLs.
|
|
31
|
+
- **The country-code rejection** on the occurrence tools and on `gbif_search_datasets` `publishingCountry` states what GBIF does with each form, where 0.8.1 said a country name matches nothing.
|
|
32
|
+
- **A `*` range end with whitespace between it and the comma** (`"* ,1990"`) on `year` or `coordinateUncertaintyInMeters` fails as `invalid_filter` naming the corrected form; 0.8.1 sent it to GBIF, which answered a bare 404.
|
|
33
|
+
|
|
34
|
+
## Dependencies
|
|
35
|
+
|
|
36
|
+
- `@biomejs/biome` ^2.6.6 → ^2.6.8.
|
|
37
|
+
- `ignore` ^7.0.14 → ^7.0.16.
|
|
38
|
+
- `vitest` ^5.1.0 → 5.1.0 (pinned: the forks pool in 5.1.1 calls `child.channel.unref()`, which Bun 1.4.4 does not implement).
|
package/changelog/template.md
CHANGED
|
@@ -116,14 +116,21 @@ security: false
|
|
|
116
116
|
resolves to whatever real item already owns 42, and timeline previews pull
|
|
117
117
|
in that unrelated item's metadata.
|
|
118
118
|
|
|
119
|
+
Outside reporters: when the issue or PR came from outside the project
|
|
120
|
+
(`git-wrapup` step 5 says how to tell), thank its author in the same
|
|
121
|
+
parenthetical, profile linked by full URL for the same reason:
|
|
122
|
+
|
|
123
|
+
([#38](https://github.com/cyanheads/mcp-ts-core/issues/38), thanks [@octocat](https://github.com/octocat)!)
|
|
124
|
+
|
|
119
125
|
TAG ANNOTATIONS — the annotated tag body renders as the GitHub Release body
|
|
120
126
|
via `gh release create --notes-from-tag`. It is a condensed digest of this
|
|
121
127
|
entry, never a copy, and its format is owned by the `release-and-publish`
|
|
122
128
|
skill (step 4, "Create the annotated tag"): a short subject line without the
|
|
123
129
|
version, flat headline bullets — no Keep-a-Changelog section headers, no
|
|
124
|
-
gates line — at most one deps line, issue backlinks
|
|
125
|
-
last. In release-PR mode the `git-wrapup`
|
|
126
|
-
PR body's `## Changes` and the tag copies
|
|
130
|
+
gates line — at most one deps line, issue backlinks with any outside-reporter
|
|
131
|
+
thanks, and the changelog link last. In release-PR mode the `git-wrapup`
|
|
132
|
+
skill authors those bullets as the PR body's `## Changes` and the tag copies
|
|
133
|
+
them.
|
|
127
134
|
-->
|
|
128
135
|
|
|
129
136
|
## Added
|
package/dist/index.js
CHANGED
|
@@ -28,7 +28,7 @@ import { initGbifService } from './services/gbif/gbif-service.js';
|
|
|
28
28
|
await createApp({
|
|
29
29
|
name: 'gbif-biodiversity-mcp-server',
|
|
30
30
|
title: 'gbif-biodiversity-mcp-server',
|
|
31
|
-
instructions: 'Use the gbif_* tools to query species taxonomy, occurrences, datasets, and publishers via the GBIF API. Keyless — these endpoints need no credentials. Resolve any name with gbif_match_species first — it returns the backbone taxonKey the occurrence tools expect, resolving a synonym to its accepted taxon and reporting the matched synonym key alongside as matchedTaxonKey, unlike the raw scientificName filter. A matchType of HIGHERRANK means GBIF matched at a higher rank — a misspelled species can come back as its genus or kingdom — so that taxonKey covers the whole higher taxon; the notice on the result names it. gbif_search_species defaults to the GBIF Backbone Taxonomy checklist d7dddbf4-2cf0-4f39-9b2a-bb099caae36c and honors an explicit datasetKey. Its key is the source checklist usage key; use the optional nubKey for occurrence queries, otherwise resolve the name with gbif_match_species. The optional datasetKey identifies the source checklist. The kingdom, family, and genus filters on gbif_search_species take names and are resolved to backbone keys the same way before the search runs, since /species/search scopes by taxon key alone: the narrowest of the three supplied is what scopes, a name is matched exactly and capitalized as GBIF writes it, one that reaches no backbone taxon at that rank fails rather than widening the search, and pairing any of them with datasetKey matches nothing unless that checklist is the GBIF backbone. Countries use ISO 3166-1 alpha-2; datasets and publishers are keyed by UUID, occurrences by integer key. Omit a filter you do not want rather than sending it blank: GBIF ignores a parameter it is given with no value and answers with the whole unfiltered scope, so every optional filter on these tools rejects a blank or whitespace-only value instead of quietly widening the query. That rejection is a typed invalid_filter carrying the recovery hint the tool declares, except on country and publishingCountry of the occurrence tools and publishingCountry of gbif_search_datasets, where the uppercase-only pattern rejects it at the schema, so the failure is the generic -32602 invalid_arguments rejection, carrying the message of that pattern instead. On the occurrence tools country and publishingCountry, and on gbif_search_datasets publishingCountry, the uppercase two-letter form is the only one accepted — lowercase and alpha-3 forms ("gb", "USA") match nothing on those routes, so those fields reject anything else rather than answering zero, while gbif_search_publishers resolves either form case-insensitively against the registry and needs no such constraint. An organization key from gbif_search_publishers chains into gbif_search_datasets two ways: publishingOrg for the datasets that organization published, hostingOrg for the ones its own installation serves. publishingOrg is almost always the one meant — most organizations publish through an installation someone else runs, so hostingOrg matches nothing for them — and supplying both intersects the two rather than combining them. gbif_get_dataset, the gbif://dataset/{datasetKey} resource, and each gbif_search_datasets row also return the publishingOrganizationKey of the dataset, which goes into publishingOrg the same way. On the occurrence tools country is where the record was observed and publishingCountry is the country of the organization that published it — different questions that disagree on most records, so pick deliberately; stateProvince is matched verbatim, exactly and case-sensitively, and an unrecognized value returns zero records rather than an error, so take one from a STATE_PROVINCE facet instead of guessing a spelling. gadmGid is the normalized alternative: a GADM GID (ESP.1_1) GBIF derives from the coordinates of each record, matched exactly and taken from a GADM_LEVEL_0_GID … GADM_LEVEL_3_GID facet or the gadm field of gbif_get_occurrence; records without coordinates carry none. catalogNumber and institutionCode match whole values case-insensitively, recordedBy matches one collector exactly and case-sensitively (take a spelling from a RECORDED_BY facet), and mediaType is one of StillImage, MovingImage, Sound, InteractiveResource. GBIF indexes absence records — a documented survey that looked for a taxon and did not find it — alongside sightings, so gbif_search_occurrences, gbif_count_occurrences, and gbif_occurrence_facets all default occurrenceStatus to PRESENT and report the applied filter in their enrichment; pass ANY to include absences, or ABSENT for absences alone. For some taxa absences dominate: an unfiltered count can run five orders of magnitude above the sightings it appears to report. The dataset recordCount on gbif_search_datasets, gbif_get_dataset, and the gbif://dataset/{datasetKey} resource is not filtered that way — it spans every occurrenceStatus, so it can exceed a gbif_count_occurrences total for the same datasetKey. Occurrence paging caps at offset+limit=100,001 and GBIF exposes no cursor or scroll, so a larger result set is reached only by partitioning it: gbif_occurrence_facets with facet DATASET_KEY splits a scope into buckets that sum to its full total, since every occurrence carries exactly one datasetKey, and each bucket is then searchable on its own; a facet on a dimension a record can lack — YEAR, MONTH, STATE_PROVINCE, SPECIES_KEY, INSTITUTION_CODE, MEDIA_TYPE, RECORDED_BY, and the GADM_LEVEL_0_GID … GADM_LEVEL_3_GID GIDs (records without coordinates or outside every GADM unit at that level) — leaves those records in no bucket, and MEDIA_TYPE and RECORDED_BY buckets overlap. Search, count and facets accept the same biological filters and echo only effective supplied filters in scope, always including occurrenceStatus; isGeoreferenced is a count alias for hasCoordinate and conflicting values fail as invalid_filter. Repeat every biological filter on the facet call and each partition search so bucket counts reconcile. All supplied spatial filters intersect, while taxonKey and scientificName combine with OR. Key-dimension buckets (KINGDOM_KEY through SPECIES_KEY, DATASET_KEY) are bare keys; includeLabels adds the name of each as label at one extra request per bucket, under a 10 s deadline, and notice counts any left unlabeled. This server cannot retrieve a result set in bulk — the GBIF Download API needs a GBIF.org account and returns an archive asynchronously, and the monthly GBIF Parquet snapshot on AWS Open Data is a bulk dataset; both are routes to take outside this server. The gbif-biodiversity-guide skill (skill://gbif-biodiversity-guide/SKILL.md) carries the gates for choosing a region filter, reading counts and trends, reconciling a name list, tracing records to collections and publishers, and concluding a taxon is absent.',
|
|
31
|
+
instructions: 'Use the gbif_* tools to query species taxonomy, occurrences, datasets, and publishers via the GBIF API. Keyless — these endpoints need no credentials. Resolve any name with gbif_match_species first — it returns the backbone taxonKey the occurrence tools expect, resolving a synonym to its accepted taxon and reporting the matched synonym key alongside as matchedTaxonKey; the raw scientificName filter also resolves a synonym, but a name shared across kingdoms, such as Oenanthe, matches nothing there, where a key names exactly one taxon. A matchType of HIGHERRANK means GBIF matched at a higher rank — a misspelled species can come back as its genus or kingdom — so that taxonKey covers the whole higher taxon; the notice on the result names it. gbif_bulk_match_species resolves such a name when its entry is { name, kingdom }. checklistKey 7ddf754f-d193-4cc9-b351-99906754a03b (opt-in) selects the Catalogue of Life eXtended Release, the taxonomy GBIF now maintains: the match tools then return its case-sensitive string key as checklistTaxonKey, and the occurrence tools take one as checklistTaxonKey under the same checklistKey, where taxonKey is rejected and KINGDOM_KEY through SPECIES_KEY buckets are Catalogue of Life keys; either checklistKey value also leaves out the records GBIF has not matched to a taxon in that checklist. gbif_search_species defaults to the GBIF Backbone Taxonomy checklist d7dddbf4-2cf0-4f39-9b2a-bb099caae36c and honors an explicit datasetKey. Its key is the source checklist usage key; use the optional nubKey for occurrence queries, otherwise resolve the name with gbif_match_species; gbif_get_species, gbif_get_species_children, and gbif_get_species_classification return the same datasetKey and nubKey beside each usage key. The optional datasetKey identifies the source checklist. The kingdom, family, and genus filters on gbif_search_species take names and are resolved to backbone keys the same way before the search runs, since /species/search scopes by taxon key alone: the narrowest of the three supplied is what scopes, a name is matched by its exact spelling in any letter case, one that reaches no backbone taxon at that rank fails rather than widening the search, and pairing any of them with datasetKey matches nothing unless that checklist is the GBIF backbone. gbif_search_species also takes status, one or more taxonomic statuses OR-ed, where SYNONYM matches only that exact status. gbif_search_species pages to offset+limit 100,000, gbif_search_datasets to 125,000, and gbif_occurrence_facets to facetOffset+facetLimit 1,199,999, or 500,000 on a scope ranking more than 500,001 buckets; past those a request fails as pagination_cap_exceeded, and the notice on a larger match names the filters that narrow it. Countries use ISO 3166-1 alpha-2; datasets and publishers are keyed by UUID, occurrences by integer key. Omit a filter you do not want rather than sending it blank: GBIF ignores a parameter it is given with no value and answers with the whole unfiltered scope, so every optional filter on these tools rejects a blank or whitespace-only value instead of quietly widening the query. That rejection is a typed invalid_filter carrying the recovery hint the tool declares, except on country and publishingCountry of the occurrence tools, publishingCountry of gbif_search_datasets, and license of the occurrence tools, where the uppercase-only pattern (an enum, for license) rejects a blank or unknown value at the schema, so the failure is the generic -32602 invalid_arguments rejection, carrying the message of that pattern or enum instead. On the occurrence tools country and publishingCountry, and on gbif_search_datasets publishingCountry, the uppercase two-letter form is the only one accepted — lowercase and alpha-3 forms ("gb", "USA") match nothing on those routes, so those fields reject anything else rather than answering zero, while gbif_search_publishers resolves either form case-insensitively against the registry and needs no such constraint. An organization key from gbif_search_publishers chains into gbif_search_datasets two ways: publishingOrg for the datasets that organization published, hostingOrg for the ones its own installation serves. publishingOrg is almost always the one meant — most organizations publish through an installation someone else runs, so hostingOrg matches nothing for them — and supplying both intersects the two rather than combining them. gbif_get_dataset, the gbif://dataset/{datasetKey} resource, and each gbif_search_datasets row also return the publishingOrganizationKey of the dataset, and gbif_get_occurrence and every gbif_search_occurrences row return it for the record, which goes into publishingOrg the same way. The occurrence tools take publishingOrg too, scoping to everything that organization published across its datasets; a PUBLISHING_ORG facet lists the organizations in a scope. On the occurrence tools country is where the record was observed and publishingCountry is the country of the organization that published it — different questions that disagree on most records, so pick deliberately; stateProvince is matched verbatim, exactly and case-sensitively, and an unrecognized value returns zero records rather than an error, so take one from a STATE_PROVINCE facet instead of guessing a spelling. gadmGid is the normalized alternative: a GADM GID (ESP.1_1) GBIF derives from the coordinates of each record, matched exactly and taken from a GADM_LEVEL_0_GID … GADM_LEVEL_3_GID facet or the gadm field of gbif_get_occurrence; records without coordinates carry none. catalogNumber and institutionCode match whole values case-insensitively, recordedBy matches one collector exactly and case-sensitively (take a spelling from a RECORDED_BY facet), and mediaType is one of StillImage, MovingImage, Sound, InteractiveResource. typeStatus and establishmentMeans name a GBIF vocabulary concept and match it and every narrower one (Type covers every kind of type). For records to map, pair hasGeospatialIssue false with hasCoordinate true: GBIF often strips the coordinates of a flagged record. GBIF indexes absence records — a documented survey that looked for a taxon and did not find it — alongside sightings, so gbif_search_occurrences, gbif_count_occurrences, and gbif_occurrence_facets all default occurrenceStatus to PRESENT and report the applied filter in their enrichment; pass ANY to include absences, or ABSENT for absences alone. Records, rows, and OCCURRENCE_STATUS buckets read DETECTED and NOT_DETECTED, the GBIF names for the same two states, and pass back unchanged as occurrenceStatus. For some taxa absences dominate: an unfiltered count can run five orders of magnitude above the sightings it appears to report. The dataset recordCount on gbif_search_datasets, gbif_get_dataset, and the gbif://dataset/{datasetKey} resource is not filtered that way — it spans every occurrenceStatus, so it can exceed a gbif_count_occurrences total for the same datasetKey. A deleted dataset keeps resolving through gbif_get_dataset with a deleted timestamp, and GBIF indexes none of its occurrences. Occurrence paging caps at offset+limit=100,001 and GBIF exposes no cursor or scroll, so a larger result set is reached only by partitioning it: gbif_occurrence_facets with facet DATASET_KEY splits a scope into buckets that sum to its full total, since every occurrence carries exactly one datasetKey, and each bucket is then searchable on its own; a facet on a dimension a record can lack — YEAR, MONTH, STATE_PROVINCE, SPECIES_KEY, INSTITUTION_CODE, MEDIA_TYPE, RECORDED_BY, TYPE_STATUS, ESTABLISHMENT_MEANS, and the GADM_LEVEL_0_GID … GADM_LEVEL_3_GID GIDs (records without coordinates or outside every GADM unit at that level) — leaves those records in no bucket, and MEDIA_TYPE, RECORDED_BY, TYPE_STATUS, and ESTABLISHMENT_MEANS buckets overlap (a TYPE_STATUS or ESTABLISHMENT_MEANS record counts under its concept and every broader one), so their sums can pass the total. Search, count and facets accept the same biological filters and echo only effective supplied filters in scope, always including occurrenceStatus; isGeoreferenced is a count alias for hasCoordinate and conflicting values fail as invalid_filter. Repeat every biological filter on the facet call and each partition search so bucket counts reconcile. All supplied spatial filters intersect, geoDistance included (a radius around a point, written "38.17,-3.95,25km" with a km or m unit), while taxonKey and scientificName combine with OR, so a scientificName GBIF cannot resolve empties the whole query. country, basisOfRecord, taxonKey, and checklistTaxonKey take one value or an array, OR-ed within the filter, so a multi-country region is one call. decimalLatitude, decimalLongitude, coordinateUncertaintyInMeters, elevation, and depth take "min,max", both ends inclusive; a value without a comma matches only that exact value, not values near it. year, month, and eventDate take one value or "min,max", and on those and on elevation, depth, and coordinateUncertaintyInMeters "*" opens one end of a range but a bare "*" is rejected, as is whitespace between a "*" end and the comma ("* ,1990") on all of those but eventDate. Key and GID buckets (KINGDOM_KEY through SPECIES_KEY, DATASET_KEY, PUBLISHING_ORG, GADM_LEVEL_0_GID through GADM_LEVEL_3_GID) are bare keys; includeLabels adds the name of each (the organization title for PUBLISHING_ORG, the area name for a GADM level) as label at one extra request per bucket, under a 10 s deadline, and notice counts any left unlabeled. Where content[] shows &#NN; in publisher-supplied text, that is a character reference standing for one character so the text stays literal in Markdown, never part of the value; structuredContent carries every string as GBIF sent it, so take a value to pass back as a filter from there. This server cannot retrieve a result set in bulk — the GBIF Download API needs a GBIF.org account and returns an archive asynchronously, and the monthly GBIF Parquet snapshot on AWS Open Data is a bulk dataset; both are routes to take outside this server. The gbif-biodiversity-guide skill (skill://gbif-biodiversity-guide/SKILL.md) carries the gates for choosing a region filter, reading counts and trends, reconciling a name list, tracing records to collections and publishers, and concluding a taxon is absent.',
|
|
32
32
|
// Declared here rather than left to MCP_SESSION_MODE, so a source run and the
|
|
33
33
|
// container resolve the same posture. No handler calls ctx.requestInput, so
|
|
34
34
|
// nothing needs the stateful-only elicitation path a 2025-era client relies on.
|
package/dist/index.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;GAGG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,wBAAwB,CAAC;AACnD,OAAO,EAAE,eAAe,EAAE,MAAM,2BAA2B,CAAC;AAC5D,YAAY;AACZ,OAAO,EAAE,mBAAmB,EAAE,MAAM,6DAA6D,CAAC;AAClG,OAAO,EAAE,mBAAmB,EAAE,MAAM,6DAA6D,CAAC;AAClG,OAAO,EAAE,oBAAoB,EAAE,MAAM,gEAAgE,CAAC;AACtG,OAAO,EAAE,oBAAoB,EAAE,MAAM,+DAA+D,CAAC;AACrG,OAAO,EAAE,cAAc,EAAE,MAAM,yDAAyD,CAAC;AACzF,OAAO,EAAE,iBAAiB,EAAE,MAAM,4DAA4D,CAAC;AAC/F,OAAO,EAAE,cAAc,EAAE,MAAM,yDAAyD,CAAC;AACzF,OAAO,EAAE,sBAAsB,EAAE,MAAM,kEAAkE,CAAC;AAC1G,OAAO,EAAE,4BAA4B,EAAE,MAAM,wEAAwE,CAAC;AACtH,iBAAiB;AACjB,OAAO,EAAE,gBAAgB,EAAE,MAAM,2DAA2D,CAAC;AAC7F,OAAO,EAAE,oBAAoB,EAAE,MAAM,+DAA+D,CAAC;AACrG,8BAA8B;AAC9B,OAAO,EAAE,kBAAkB,EAAE,MAAM,6DAA6D,CAAC;AACjG,mBAAmB;AACnB,OAAO,EAAE,qBAAqB,EAAE,MAAM,gEAAgE,CAAC;AACvG,OAAO,EAAE,oBAAoB,EAAE,MAAM,+DAA+D,CAAC;AACrG,OAAO,EAAE,iBAAiB,EAAE,MAAM,4DAA4D,CAAC;AAC/F,OAAO,EAAE,eAAe,EAAE,MAAM,iCAAiC,CAAC;AAElE,MAAM,SAAS,CAAC;IACd,IAAI,EAAE,8BAA8B;IACpC,KAAK,EAAE,8BAA8B;IACrC,YAAY,EACV,
|
|
1
|
+
{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;GAGG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,wBAAwB,CAAC;AACnD,OAAO,EAAE,eAAe,EAAE,MAAM,2BAA2B,CAAC;AAC5D,YAAY;AACZ,OAAO,EAAE,mBAAmB,EAAE,MAAM,6DAA6D,CAAC;AAClG,OAAO,EAAE,mBAAmB,EAAE,MAAM,6DAA6D,CAAC;AAClG,OAAO,EAAE,oBAAoB,EAAE,MAAM,gEAAgE,CAAC;AACtG,OAAO,EAAE,oBAAoB,EAAE,MAAM,+DAA+D,CAAC;AACrG,OAAO,EAAE,cAAc,EAAE,MAAM,yDAAyD,CAAC;AACzF,OAAO,EAAE,iBAAiB,EAAE,MAAM,4DAA4D,CAAC;AAC/F,OAAO,EAAE,cAAc,EAAE,MAAM,yDAAyD,CAAC;AACzF,OAAO,EAAE,sBAAsB,EAAE,MAAM,kEAAkE,CAAC;AAC1G,OAAO,EAAE,4BAA4B,EAAE,MAAM,wEAAwE,CAAC;AACtH,iBAAiB;AACjB,OAAO,EAAE,gBAAgB,EAAE,MAAM,2DAA2D,CAAC;AAC7F,OAAO,EAAE,oBAAoB,EAAE,MAAM,+DAA+D,CAAC;AACrG,8BAA8B;AAC9B,OAAO,EAAE,kBAAkB,EAAE,MAAM,6DAA6D,CAAC;AACjG,mBAAmB;AACnB,OAAO,EAAE,qBAAqB,EAAE,MAAM,gEAAgE,CAAC;AACvG,OAAO,EAAE,oBAAoB,EAAE,MAAM,+DAA+D,CAAC;AACrG,OAAO,EAAE,iBAAiB,EAAE,MAAM,4DAA4D,CAAC;AAC/F,OAAO,EAAE,eAAe,EAAE,MAAM,iCAAiC,CAAC;AAElE,MAAM,SAAS,CAAC;IACd,IAAI,EAAE,8BAA8B;IACpC,KAAK,EAAE,8BAA8B;IACrC,YAAY,EACV,4oUAA4oU;IAC9oU,8EAA8E;IAC9E,4EAA4E;IAC5E,gFAAgF;IAChF,WAAW,EAAE,WAAW;IACxB,KAAK,EAAE;QACL,gBAAgB;QAChB,oBAAoB;QACpB,cAAc;QACd,iBAAiB;QACjB,4BAA4B;QAC5B,sBAAsB;QACtB,qBAAqB;QACrB,oBAAoB;QACpB,iBAAiB;QACjB,oBAAoB;QACpB,kBAAkB;QAClB,cAAc;QACd,oBAAoB;KACrB;IACD,SAAS,EAAE,CAAC,mBAAmB,EAAE,mBAAmB,CAAC;IACrD,OAAO,EAAE,EAAE;IACX,oFAAoF;IACpF,MAAM,EAAE,QAAQ;IAChB,6EAA6E;IAC7E,OAAO,EAAE,EAAE,WAAW,EAAE,KAAK,EAAE;IAC/B,KAAK,CAAC,IAAI;QACR,MAAM,GAAG,GAAG,eAAe,EAAE,CAAC;QAC9B,eAAe,CAAC,IAAI,CAAC,MAAM,EAAE,IAAI,CAAC,OAAO,EAAE;YACzC,OAAO,EAAE,GAAG,CAAC,OAAO;YACpB,SAAS,EAAE,GAAG,CAAC,gBAAgB;YAC/B,SAAS,EAAE,GAAG,CAAC,SAAS;SACzB,CAAC,CAAC;IACL,CAAC;CACF,CAAC,CAAC"}
|