---
summary: "@cyanheads/mcp-ts-core ^0.11.1 → ^0.12.3 (tool inputs now strict; MCP SDK moves to @modelcontextprotocol/server); gbif_get_dataset and gbif_occurrence_facets adopt the framework's standard truncated/shown/cap trailer for their contact-list and facet-page caps."
breaking: false
security: false
---

# 0.7.3 — 2026-08-25

## Added

- **`.github/CONTRIBUTING.md` and `.github/CODE_OF_CONDUCT.md`** — issue-first contribution guidance and a project code of conduct.
- **`format:unsafe`** script — `format` now runs Biome's safe fixes only; `format:unsafe` applies its unsafe autofixes for manual review.

## Changed

- **Tool arguments are strict.** An argument key a tool's schema does not declare is rejected by name before the handler runs, instead of being silently dropped — inherited from `@cyanheads/mcp-ts-core` ^0.12.3; no tool on this server changed its own declared inputs.
- **`gbif_occurrence_facets` replaces `moreValuesLikely` with the framework's standard `truncated`/`shown`/`cap` enrichment trailer.** The notice now also names the `facetOffset` to page with. A client keyed on `moreValuesLikely` needs to read `truncated` instead.
- **`gbif_get_dataset` discloses contact-list truncation in the same standard trailer.** `contactsTotal`/`contactsReturned` on `output` are unchanged.
- **HTTP session mode is documented explicitly.** `.env.example` and the README env table note `MCP_SESSION_MODE`'s `auto` default (resolves to `stateful`) and that the Docker image runs `stateless`.
- **`.github/SECURITY.md`** routes reports to `security@caseyjhand.com` and asks reproductions to redact credentials.
- **Bun pinned to 1.4.0** — `Dockerfile` build/production stages and `packageManager`. The build stage now targets `$BUILDPLATFORM` rather than the image's target platform: under QEMU emulation Bun's JavaScriptCore aborts on a spurious `MemoryExhaustion` assertion, failing a cross-arch build outright on an arm64 host.

## Fixed

- **`bun run devcheck`'s `bun audit` parser handles Bun 1.4's changed output format.** Bun 1.4 rewrote both the vulnerability header (`name  <range>` → `name@<version>`) and the dependency-path separator (`›` → `>`); the parser in `scripts/devcheck.ts` now accepts either, where a lone old-format matcher against 1.4 output parsed nothing.

## Dependencies

- `@cyanheads/mcp-ts-core` ^0.11.1 → ^0.12.3 (MCP SDK moves `@modelcontextprotocol/sdk` ^1.30.0 → `@modelcontextprotocol/server` ^2.0.0)
- `@biomejs/biome` ^2.5.6 → ^2.5.10
- `@types/node` ^26.1.2 → ^26.2.0
- `tsc-alias` ^1.9.1 → ^1.9.2
- `vitest` ^4.1.10 → ^4.1.11
